BSOD System_Service_Exception / DRIVER_IRQL_NOT_LESS_OR_EQUAL

Windows 7 Ultimate x64
Retail

Hello,

I keep getting BSODs, usually while having a flash video running, but the very last one occured without any flash video being opened.

I ran chkdsk /R on my system drive this morning with 0 errors.
I've also run memtest86 for ~10 hours with 0 errors.

Thanks in advance!

Tervel said:

Windows 7 Ultimate x64
Retail

Hello,

I keep getting BSODs, usually while having a flash video running, but the very last one occured without any flash video being opened.

I ran chkdsk /R on my system drive this morning with 0 errors.
I've also run memtest86 for ~10 hours with 0 errors.

Thanks in advance!

Nothing definative but Related to DlinkUDSMBus.sys KCodes Master Bus of USB Software Bus By TCP. Yours is 3 years old.

Hello,

I uninstalled D-Link shareport utility which from what I gather seems to be what is using DlinkUDSMBus.sys.

However I did have another BSOD, this time while having a flash video open (In Firefox this time instead of Google Chrome) while gaming.

The dump is attached below.

Thanks in advance!

More BSODs. Starting to think this is Hardware related, especially as they always seem to happen during (or shortly after) the first boot of the day.

This afternoon for example:
Computer boots, I log in -> Computer completely freezes
I press the reset button -> Angry BIOS beeps (the long ones you'd get if for example you haven't inserted your graphics card properly), after a few seconds it restarts again and boots up normally, I log in, Bluescreen.
Computer reboots, starts up normally and been running fine for hours.

The problem is that I don't know what hardware would cause this. My PSU is ~3 months old, memory showing 0 errors after 8+ hours of memtest86. I would imagine HDDs are irrelevant as they wouldn't cause issues already at the POST.

In my mind this leaves Motherboard, CPU, GFX.

Does this sound right to people?
Can I assume it's the motherboard if the CPU does fine after hours of Prime95 and the Graphics card does fine with Furmark?

Thanks again!

They went away for a while but have now started appearing again for some reason.

Attaching 4 minidumps.

Thanks in advance!

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tervel\121811-22354-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03449670
Debug session time: Sun Dec 18 08:26:39.077 2011 (UTC - 7:00)
System Uptime: 0 days 0:50:08.509
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, e87a001, 862c, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000000e87a001
Arg3: 000000000000862c
Arg4: fffff70001080000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032d85a7 to fffff80003280c40

STACK_TEXT:  
fffff880`08b0d7e8 fffff800`032d85a7 : 00000000`0000001a 00000000`00041284 00000000`0e87a001 00000000`0000862c : nt!KeBugCheckEx
fffff880`08b0d7f0 fffff800`032efe6c : fffffa80`015c0180 e2c00000`74008825 00000000`0e879000 c5300000`8f57f825 : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`08b0d830 fffff800`032b4569 : fffff900`00000000 00000000`0ec5ffff fffff880`00000000 00000000`00001001 : nt! ?? ::FNODOBFM::`string'+0x35d20
fffff880`08b0d9f0 fffff800`03598221 : fffffa80`038e6010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`08b0db10 fffff800`03598623 : 00000000`00000000 00000000`0e7c0000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`08b0dbd0 fffff800`0327fed3 : fffffa80`05b96b60 fffff880`08b0dbd8 fffffa80`05971a60 00000000`7efdb000 : nt!NtUnmapViewOfSection+0x5f
fffff880`08b0dc20 00000000`775315ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000bdea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775315ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4ac3
fffff800`032d85a7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tervel\010912-33977-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_53706341`0203008c, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_53706341`0203008c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_53706341`0203008c
Debugger can not determine kernel base address
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03202000 PsLoadedModuleList = 0xfffff800`03447670
Debug session time: Mon Jan  9 11:15:01.960 2012 (UTC - 7:00)
System Uptime: 0 days 2:58:02.724
Unable to load image Unknown_Module_53706341`0203008c, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_53706341`0203008c
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_53706341`0203008c
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003544833, fffff88009cc30d0, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003544833, Address of the instruction which caused the bugcheck
Arg3: fffff88009cc30d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+6166363732346330
fffff800`03544833 f0838108020000ff lock add dword ptr [rcx+208h],0FFFFFFFFh

CONTEXT:  fffff88009cc30d0 -- (.cxr 0xfffff88009cc30d0)
Unable to read context, Win32 error 0n30

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032884a9 to fffff880041b97f2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`032884a9 : 00000000`0026be7a fffffa80`03d710a8 fffff800`03402cc0 00000000`00000001 : 0xfffff880`041b97f2
fffff800`00b9cca0 00000000`0026be7a : fffffa80`03d710a8 fffff800`03402cc0 00000000`00000001 fffff800`033f4e80 : 0xfffff800`032884a9
fffff800`00b9cca8 fffffa80`03d710a8 : fffff800`03402cc0 00000000`00000001 fffff800`033f4e80 fffff800`0328a167 : 0x26be7a
fffff800`00b9ccb0 fffff800`03402cc0 : 00000000`00000001 fffff800`033f4e80 fffff800`0328a167 00000006`50c47fe1 : 0xfffffa80`03d710a8
fffff800`00b9ccb8 00000000`00000001 : fffff800`033f4e80 fffff800`0328a167 00000006`50c47fe1 00000006`000a72f1 : 0xfffff800`03402cc0
fffff800`00b9ccc0 fffff800`033f4e80 : fffff800`0328a167 00000006`50c47fe1 00000006`000a72f1 00000006`50c47fe1 : 0x1
fffff800`00b9ccc8 fffff800`0328a167 : 00000006`50c47fe1 00000006`000a72f1 00000006`50c47fe1 00000000`000000f1 : 0xfffff800`033f4e80
fffff800`00b9ccd0 00000006`50c47fe1 : 00000006`000a72f1 00000006`50c47fe1 00000000`000000f1 fffffa80`03d71010 : 0xfffff800`0328a167
fffff800`00b9ccd8 00000006`000a72f1 : 00000006`50c47fe1 00000000`000000f1 fffffa80`03d71010 400000c2`400000c1 : 0x6`50c47fe1
fffff800`00b9cce0 00000006`50c47fe1 : 00000000`000000f1 fffffa80`03d71010 400000c2`400000c1 0000000f`400000c3 : 0x6`000a72f1
fffff800`00b9cce8 00000000`000000f1 : fffffa80`03d71010 400000c2`400000c1 0000000f`400000c3 00000005`8495f9ac : 0x6`50c47fe1
fffff800`00b9ccf0 fffffa80`03d71010 : 400000c2`400000c1 0000000f`400000c3 00000005`8495f9ac fffff800`00b96080 : 0xf1
fffff800`00b9ccf8 400000c2`400000c1 : 0000000f`400000c3 00000005`8495f9ac fffff800`00b96080 fffffa80`024b8890 : 0xfffffa80`03d71010
fffff800`00b9cd00 0000000f`400000c3 : 00000005`8495f9ac fffff800`00b96080 fffffa80`024b8890 00000000`00000000 : 0x400000c2`400000c1
fffff800`00b9cd08 00000005`8495f9ac : fffff800`00b96080 fffffa80`024b8890 00000000`00000000 00001942`8c4ae6fa : 0xf`400000c3
fffff800`00b9cd10 fffff800`00b96080 : fffffa80`024b8890 00000000`00000000 00001942`8c4ae6fa 00001942`8c4aeeb8 : 0x5`8495f9ac
fffff800`00b9cd18 fffffa80`024b8890 : 00000000`00000000 00001942`8c4ae6fa 00001942`8c4aeeb8 fffff800`032818a4 : 0xfffff800`00b96080
fffff800`00b9cd20 00000000`00000000 : 00001942`8c4ae6fa 00001942`8c4aeeb8 fffff800`032818a4 fffff800`00b96080 : 0xfffffa80`024b8890


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tervel\011112-22401-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0325c000 PsLoadedModuleList = 0xfffff800`034a1670
Debug session time: Wed Jan 11 07:14:13.788 2012 (UTC - 7:00)
System Uptime: 0 days 1:39:09.567
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 8547e, 1, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3824b )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000008547e, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000334a140 to fffff800032d8c40

STACK_TEXT:  
fffff880`03364988 fffff800`0334a140 : 00000000`0000004e 00000000`00000007 00000000`0008547e 00000000`00000001 : nt!KeBugCheckEx
fffff880`03364990 fffff800`03273b64 : fffffa80`02db0010 00000000`00000000 00000000`00000000 fffffa80`024cd040 : nt! ?? ::FNODOBFM::`string'+0x3824b
fffff880`03364a70 fffff800`03273ba6 : 00000000`00000001 00000000`00000000 fffff800`03479260 00000000`00000000 : nt!MiPfCompletePrefetchIos+0x54
fffff880`03364aa0 fffff800`03284d85 : fffffa80`024cd040 00000000`0b6c4000 00000000`0b6c4000 fffff800`03479260 : nt!MmWaitForCacheManagerPrefetch+0x1e
fffff880`03364ad0 fffff800`0331e98e : fffffa80`035ab3a0 fffffa80`00000000 fffffa80`00000005 00000000`00000001 : nt!CcPerformReadAhead+0x341
fffff880`03364c00 fffff800`032e3001 : fffffa80`024ffd60 fffff800`035cf901 fffff800`034da8d0 fffff800`00000002 : nt!CcWorkerThread+0x21e
fffff880`03364cb0 fffff800`03573fee : 00000000`00000000 fffffa80`024cd040 00000000`00000080 fffffa80`024b8890 : nt!ExpWorkerThread+0x111
fffff880`03364d40 fffff800`032ca5e6 : fffff880`03163180 fffffa80`024cd040 fffff880`0316dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03364d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3824b
fffff800`0334a140 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3824b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+3824b

BUCKET_ID:  X64_0x4E_7_nt!_??_::FNODOBFM::_string_+3824b

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tervel\011212-21715-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03491670
Debug session time: Thu Jan 12 06:32:40.355 2012 (UTC - 7:00)
System Uptime: 0 days 0:19:03.744
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800032c7ee0, fffff8800862e240, 0}

Probably caused by : hardware ( nt!KiSystemServiceExit+5 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032c7ee0, Address of the instruction which caused the bugcheck
Arg3: fffff8800862e240, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiSystemServiceExit+5
fffff800`032c7ee0 0000            add     byte ptr [rax],al

CONTEXT:  fffff8800862e240 -- (.cxr 0xfffff8800862e240)
rax=0000000000000000 rbx=fffffa80035e4300 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000006c0f900 rdi=0000000000000000
rip=fffff800032c7ee0 rsp=fffff8800862ec00 rbp=fffff8800862ec00
 r8=fffffa800326f000  r9=0000000000000000 r10=fffffffffffffffe
r11=fffffa8004e76a20 r12=00000000fff2c000 r13=0000000003e5fd20
r14=0000000003e5ef10 r15=0000000073212450
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=0000             efl=00010286
nt!KiSystemServiceExit+0x5:
fffff800`032c7ee0 0000            add     byte ptr [rax],al ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!KiSystemServiceExit+5
fffff800`032c7ee0 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800032c7ee0

STACK_TEXT:  
fffff880`0862ec00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x5


FOLLOWUP_IP: 
nt!KiSystemServiceExit+5
fffff800`032c7ee0 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSystemServiceExit+5

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800862e240 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Your bluescreen crash files are inconclusive, but point to a hardware problem.

Run the following steps and post back after doing each one.

1. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs.
2. Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.
3. Run Driver Verifier to find any driver incompatibilities/conflicts. To run Driver Verifier, do the following:
   
   a. Backup your system and user files
   b. Create a system restore point
   c. If you do not have a Windows 7 DVD, Create a system repair disc
   d. Run Driver Verifier
   
   If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
   
   Thanks to zigzag3143 for contributing to the Verifier steps.
   If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

You may want to run the disk check again since errors were fixed. I usually recommend running them repeatedly until Windows reports no problems with the disk.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Tervel\dumps\012112-24601-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03200000 PsLoadedModuleList = 0xfffff800`03445670
Debug session time: Sat Jan 21 11:14:23.383 2012 (UTC - 7:00)
System Uptime: 0 days 3:52:29.147
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000047, fffff800032aa590, fffff88006fc15a0, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkGetPresentHistory+750 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000047, Exception code that caused the bugcheck
Arg2: fffff800032aa590, Address of the instruction which caused the bugcheck
Arg3: fffff88006fc15a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP: 
nt!RtlRaiseStatus+18
fffff800`032aa590 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h]

CONTEXT:  fffff88006fc15a0 -- (.cxr 0xfffff88006fc15a0)
rax=0000000000000000 rbx=00000000c0000047 rcx=fffff88006fc15a0
rdx=0000000000000000 rsi=000000000428f8b0 rdi=0000000000000013
rip=fffff800032aa590 rsp=fffff88006fc14e0 rbp=fffff88006fc1ca0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=00000000000007fc r13=fffff88003163180
r14=0000000000000000 r15=fffffa800511c000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000282
nt!RtlRaiseStatus+0x18:
fffff800`032aa590 488b8424b8010000 mov     rax,qword ptr [rsp+1B8h] ss:0018:fffff880`06fc1698=fffff800032aa590
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000323770a to fffff800032aa590

STACK_TEXT:  
fffff880`06fc14e0 fffff800`0323770a : 00000000`00000000 fffff880`0408b2b0 00000000`00000013 fffffa80`0511c000 : nt!RtlRaiseStatus+0x18
fffff880`06fc1a80 fffff880`040ee560 : 00000000`0000080c 00000000`00000000 00000000`0428f8b0 00000000`000cab00 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff880`06fc1b00 fffff960`001bfbb7 : fffffa80`05b50b60 00000000`00000001 00000000`00000428 00000000`000003d8 : dxgkrnl!DxgkGetPresentHistory+0x750
fffff880`06fc1bf0 fffff800`0327bed3 : fffffa80`00000800 00000000`0428f820 000007fe`f72fc610 00000000`00000000 : win32k!NtGdiDdDDIGetPresentHistory+0x17
fffff880`06fc1c20 000007fe`fe11120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0428f778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe11120a


FOLLOWUP_IP: 
dxgkrnl!DxgkGetPresentHistory+750
fffff880`040ee560 488d8c2488000000 lea     rcx,[rsp+88h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgkrnl!DxgkGetPresentHistory+750

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

STACK_COMMAND:  .cxr 0xfffff88006fc15a0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DxgkGetPresentHistory+750

BUCKET_ID:  X64_0x3B_dxgkrnl!DxgkGetPresentHistory+750

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

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the latest drivers for your display card(s)
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Display adapters
7. Do the following for each adapter (in case you have multiple display cards)
   
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
8. Restart your computer after uninstalling drivers for all display cards
9. Install the latest driver for the display cards once Windows starts

Alternatively:

1. Login as an adminstrative user
2. Download the latest drivers for your display card(s)
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Display adapters
8. Do the following for each adapter (in case you have multiple display cards)
   
   • Right click the adapter
   • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
   • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer after uninstalling drivers for all display cards
10. Install the latest driver for the display cards once Windows starts

The other .dmp files were similar to the previous ones, and no .dmp files generated by Verifier yet. Have you run the Windows Memory Diagnostic tool?

Greetings!

Windows Memory Diagnostic ended with 0 errors.

Just now I had my first BSOD since activating Driver Verifier - This BSOD occured as I was saving the machine state of a VirtualBox machine to shut it down.

I didn't have Virtualbox started during any of my other BSODs, is it still likely that Virtualbox is causing all of them?