BSOD, help please

Please enable driver verifier, updating BIOS would be last thing we do, so let's put it aside for now

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

great! If you haven't experienced any more BSODs, don't turn on Drivrer Verifier. I thought you were still having problem, that's why I gave you instruction for turning on DV.

Great, keep us up to date

Thanks

Tuan

Driver Verifier stresses the drivers. If a driver is not functioning properly, it will trigger a BSOD which will generally identify the offending driver. It does not stop drivers from working. It attempts to find and identify bad drivers.

You are very welcome. That is what we are here for. :)

This time it blamed the system file. As you had not experienced any BSODs in 36 hours, I would suggest to turn off Driver Verifier for now. typing verifier.exe into the start menu, and open Verifier and Select "Delete existing settings".

Run system file check:

Open an elevated command prompt and enter sfc /scannow.

BUGCHECK SUMMARY:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.161\080610-24125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c3d000 PsLoadedModuleList = 0x82d7c570
Debug session time: Fri Aug  6 17:56:04.045 2010 (UTC + 7:00)
System Uptime: 0 days 2:45:37.124
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {12, 86366306, 1, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltpDispatch+0 )

Followup: MachineOwner
---------

Regard,

Tuan