BSOD On My New Desktop Pc

ggt · Oct 16, 2013

I bought a new PC 4 days ago. I installed fresh Windows 7 64bit from the dvd. When I open a video or play a game i see a bsod about in 10 seconds and the computer restarts. Tried installing latest nvidia drivers (plus beta driver, original driver from the dvd given with graphics card, one version older driver) and nothing changed. The BSOD keeps popping.

· OS - Windows 7 (x64)
· CPU - Intel Core i3-3210 3.20 ghz
· Video Card - Nvidia Geforce Gt630 2 gb (Gigabyte - GV-N630-2GI)
· MotherBoard - Gigabyte GA-H61M-DS2 Rev 3.0
· Power Supply - 400w

Note: Windows7_Vista_jcgriff2 tool didn't work perfectly. It has been saying "Waiting for SystemInfo" for hours so I stopped it.

Patrick · Oct 16, 2013

Hi,

Various bugchecks attached:

KMODE_EXCEPTION_NOT_HANDLED (1e)

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

If we take a look at the call stack:

Code:

1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`02f1a9a8 fffff800`030c05be : fffffa80`042d7d30 fffff880`05691425 fffff880`02f1b120 fffff800`030f3a90 : nt+0x75b90
fffff880`02f1a9b0 fffffa80`042d7d30 : fffff880`05691425 fffff880`02f1b120 fffff800`030f3a90 00000000`00000000 : nt+0x6d5be
fffff880`02f1a9b8 fffff880`05691425 : fffff880`02f1b120 fffff800`030f3a90 00000000`00000000 fffff800`030f375d : 0xfffffa80`042d7d30
fffff880`02f1a9c0 fffff880`02f1b120 : fffff800`030f3a90 00000000`00000000 fffff800`030f375d fffff800`032d7380 : [COLOR=#ff0000][I][B]Rt64win7+0x3425[/B][/I][/COLOR]
fffff880`02f1a9c8 fffff800`030f3a90 : 00000000`00000000 fffff800`030f375d fffff800`032d7380 fffff800`03214260 : 0xfffff880`02f1b120
fffff880`02f1a9d0 00000000`00000000 : fffff800`030f375d fffff800`032d7380 fffff800`03214260 fffff800`03053000 : nt+0xa0a90

We can see a Rt64win7 call before the bugcheck. Rt64win7.sys is the Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC. With this said, there's something likely causing network related conflicts, likely a 3rd party antivirus or firewall software.

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

If we look at the call stack in this dump, we can see:

Code:

2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`062e9678 fffff800`0308c169 : 00000000`0000003b 00000000`c0000005 fffff880`03f1a83a fffff880`062e9f40 : nt+0x75bc0
fffff880`062e9680 00000000`0000003b : 00000000`c0000005 fffff880`03f1a83a fffff880`062e9f40 00000000`00000000 : nt+0x75169
fffff880`062e9688 00000000`c0000005 : fffff880`03f1a83a fffff880`062e9f40 00000000`00000000 fffffa80`0607c470 : 0x3b
fffff880`062e9690 fffff880`03f1a83a : fffff880`062e9f40 00000000`00000000 fffffa80`0607c470 696c6275`703a7361 : 0xc0000005
fffff880`062e9698 fffff880`062e9f40 : 00000000`00000000 fffffa80`0607c470 696c6275`703a7361 72746552`7a732063 : [COLOR=#ff0000][I][B]aswSnx+0x6b83a[/B][/I][/COLOR]
fffff880`062e96a0 00000000`00000000 : fffffa80`0607c470 696c6275`703a7361 72746552`7a732063 73736572`64644179 : 0xfffff880`062e9f40

an aswSnx.sys call which is the avast! Virtualization Driver. As I said earlier, likely something causing network conflicts. This is most likely it.

---------------------------------------------

Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal tool - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

Regards,

Patrick

jcgriff2 · Oct 16, 2013

Hi -

There were 10 dump files; 1 was corrupted (-0- bytes); the other 9 - bugchecks -
(4) 0x1e = kernel threw an exception
(1) 0x3b = system service threw an exception
(1) 0x50 = invalid memory referenced
(2) 0xd1 = driver attempted to improperly access memory or memory itself is bad
(1) 0x7e = thread threw an exception

Most exception errors are 0xc0000005 = memory access violation

2 dumps had exception codes = 0x0, which points to unknown hardware failure -- as does the listed probable causes, which included NVIDIA video, Avast and Realtek Ethernet drivers.

System up-times prior to BSOD range from just 14 secs to just under 20 minutes:

Code:

System Uptime: 0 days 0:12:22.491
System Uptime: 0 days 0:07:30.292
System Uptime: 0 days 0:19:24.484
System Uptime: 0 days 0:12:57.711
System Uptime: 0 days 0:00:28.688
System Uptime: 0 days 0:00:53.603
System Uptime: 0 days 0:00:26.254
System Uptime: 0 days 0:00:14.008
System Uptime: 0 days 0:00:15.444

Windows 7 SP1 Ultimate x64 OEM version was installed on the night of 14.10.2013. You said the system was new. Did you purchase it pre-assembled or did you assemble it/ add hardware devices to it?

I suspect the 400w PSU may be underpowered. I'll ask a Hardware Expert to take a look.

Please provide specific PSU specs - manufacturer, model, etc. . . - Thanks.

Regards. . .

jcgriff2

`

EDIT: @ Patrick -- didn't see you there!

BSOD SUMMARY

Code:

[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-15350-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 15:28:17.102 2013 (UTC - 4:00)
System Uptime: 0 days 0:12:22.491
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+3425 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-37143-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 08:44:23.262 2013 (UTC - 4:00)
System Uptime: 0 days 0:07:30.292
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+75b90 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-46285-01.dmp]
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 08:24:49.095 2013 (UTC - 4:00)
System Uptime: 0 days 0:19:24.484
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : aswSnx.SYS ( aswSnx+6b83a )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`03f1a83a fffff880`062e9f40 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-20685-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 08:04:29.666 2013 (UTC - 4:00)
System Uptime: 0 days 0:12:57.711
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+75bc0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x1E
Bugcheck code 0000001E
Arguments ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 02/25/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-23540-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 05:31:19.299 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:28.688
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+39d7d9 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
Bugcheck code 00000050
Arguments fffff880`0319463e 00000000`00000001 fffff880`04c6e7d9 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 02/25/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-22354-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 05:27:51.588 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:53.603
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7f7c4 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`048f37c4 fffff880`02183c88 fffff880`021834e0
BiosVersion = F3
BiosReleaseDate = 02/25/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-22495-01.dmp]
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Oct 15 04:42:24.865 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:26.254
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+2b90c7 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`030c00c7 00000000`00000000 ffffffff`ffffffff
BiosVersion = F3
BiosReleaseDate = 02/25/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-16114-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Oct 15 03:50:01.619 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:14.008
BugCheck D1, {21280050, 2, 0, fffff880053adf39}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
Bugcheck code 000000D1
Arguments 00000000`21280050 00000000`00000002 00000000`00000000 fffff880`053adf39
BiosVersion = F3
BiosReleaseDate = 02/25/2013
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = To be filled by O.E.M.
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\101513-24975-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon Oct 14 21:22:10.054 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:15.444
BugCheck D1, {fffffa804644d0a0, 2, 1, fffff880056b47ca}
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
Bugcheck code 000000D1
Arguments fffffa80`4644d0a0 00000000`00000002 00000000`00000001 fffff880`056b47ca
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

	    
             
       [color=#555555]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562][color=#555555][u]http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562[/u][/color][/url]   

           [url=https://www.sysnative.com][color=#555555][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#555555][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/font]

ggt · Oct 16, 2013

I now uninstalled avast completely.

PSU Specs: Everest Atx Switching Power Supply (ATX 400-GM) 400W

I took it preassembled but just installed Windows 7 64 bit.

I've also done memtest86+ and scanned hdd via HDTune, both yielded perfect results.

It says in its box the graphics card needs 350W or higher PSU. I have 400.

ggt · Oct 16, 2013

It crashed again saying "MEMORY_MANAGEMENT" in blue screen.

Memory dump is in attachment.

Patrick · Oct 16, 2013

Latest DMP file is of the MEMORY_MANAGEMENT (1a) bugcheck.

BugCheck 1A, {41790, fffffa8001e3ada0, ffff, 0}

The 1st parameter of the bugcheck is 41790 which indicates that a page table has been corrupted. The page table is used to store mappings between physical and virtual memory addresses.

The Microsoft symbol server is still having issues, so we cannot run a dt nt!_MMPFN to check the PFN database structure integrity -

Symbol nt!_MMPFN not found.

--------------------------------------------------------

I've also done memtest86+

How long? If it was any less than ~8 passes (SEVERAL hours), run again.

If Memtest passes again after at least ~8 passes and no less, run chkdsk and then Seatools if chkdsk results are clean:

Chkdsk:
There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:

Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

Regards,

Patrick

ggt · Oct 16, 2013

Memtest86+ was more than 8 passes. It reported no errors.

Seatools reported no errors.

Chkdsk report and 1 more crash dump added.

Patrick · Oct 16, 2013

Thanks for the info, and the chkdsk log is clean.

Latest attached DMP file is of the DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) bugcheck.

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.

Code:

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Lots of memory_corruption. Given this is a *D1, I am curious if we are dealing with a device driver causing corruption. Let's enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick

ggt · Oct 16, 2013

After enabling driver verifier do I need to force a BSOD by opening a game?

ggt · Oct 16, 2013

After enabling driver verifier I got another BSOD. Added the dump.

Edit: Crashed 1 more time. now says BUGCODE_USB_DRIVER.

If I didn't get it wrong, everytime a different driver is the cause. I started to think every single part of my computer is faulty.

Patrick · Oct 16, 2013

Hi,

The latest attached DMP file is of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bugcheck.

BugCheck 1000007E, {ffffffffc0000005, fffff8800fd807d8, fffff880057bdae8, fffff880057bd340}

The 1st parameter is 0xc0000005 which indicates an access violation occurs. Let's see what caused it:

Code:

2: kd> .exr 0xfffff880057bdae8
ExceptionAddress: fffff8800fd807d8 ([COLOR=#ff0000][I][B]dxgmms1!VidSchiProfilePerformanceTick[/B][/I][/COLOR]+0x0000000000000040)
   ExceptionCode: [COLOR=#ff0000][I][B]c0000005 (Access violation)[/B][/I][/COLOR]

A dxgmms1.sys routine did, which is the DirectX MMS. Usually in DirectX crashes it's faulty RAM, video card, or board itself.

Ultimately, given the wide variety of bugchecks that are at this point clearly hardware, the PC is only 4 days old and brand new. Return it ASAP.

Regards,

Patrick

ggt · Oct 20, 2013

They changed Graphics Card and RAM for free. Now there is no problem.

Thanks for the help.

Patrick · Oct 20, 2013

Hi,

Very glad to hear, thanks for the update.

Regards,

Patrick

BSOD On My New Desktop Pc

ggt

Member

Attachments

Patrick

Sysnative Staff

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

ggt

Member

ggt

Member

Attachments

Patrick

Sysnative Staff

ggt

Member

Attachments

Patrick

Sysnative Staff

ggt

Member

ggt

Member

Attachments

Patrick

Sysnative Staff

ggt

Member

Patrick

Sysnative Staff

BSOD On My New Desktop Pc

Member

Attachments

Sysnative Staff

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Member

Attachments

Sysnative Staff

Member

Attachments

Sysnative Staff

Member

Member

Attachments

Sysnative Staff

Member

Sysnative Staff

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)