BSOD General Useage 0x000000d1

[wnight77]

Hey guys, My GF's PC has been Bluescreening i will add as much information as i can as requested.

we have been getting numerous bluescreens 0x000000d1, 0x0000000a, and a few others, i recently cleaned the history so i will wait for more crashes to list as we get them agian.

i have tried EVERYThing i can think of. im left thinking its either CPU or motherboard.

i have ran memtest86+ for 4 hours, 100% pass
i have run Asus PC diag - 100% pass
i got a new HDD and did a fresh install of Windows.
Both HDD's passed all the tests i ran on them with no errors.
RAn Video Card test for 20+ minutes <farks or something like that>

Ive attached the SF Diagnostics Tool file, i think i may be missing the memory dmp file but i will get that if its missing.

Windows 7 Home Premium 64bit
Motherboard -Asus p8z77-V LK
Video Card - 1 x XFX Double D FX-787A-CDFC Radeon HD 7870 GHz Edition
Ram - 1 x G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)

100113-18174-01.dmp 10/1/2013 8:55:50 PM DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 00000000`0020079f 00000000`00000002 00000000`00000000 fffff880`0188a95d tcpip.sys tcpip.sys+8a95d TCP/IP Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100113-18174-01.dmp 4 15 7601 277,136 10/1/2013 8:56:39 PM

 

[x BlueRobot]

[COLOR=Red]BugCheck D1[/COLOR], {20079f, 2, 0, fffff8800188a95d}

Probably caused by : tcpip.sys ( tcpip!OlmPeriodicOcbPriorityUpdateHandler+d )

0: kd> [COLOR=SeaGreen]!stack[/COLOR]
Call Stack : [COLOR=Red]11 frames[/COLOR]
## Stack-Pointer    Return-Address   Call-Site       
00 fffff800044093f8 fffff800030c6129 nt!KeBugCheckEx+0 
01 fffff80004409400 fffff800030c4da0 nt!KiBugCheckDispatch+69 
02 fffff80004409540 fffff8800188a95d nt!KiPageFault+260 
03 fffff800044096d0 fffff88001885948 tcpip!OlmPeriodicOcbPriorityUpdateHandler+d 
04 fffff80004409720 fffff800030d185c tcpip!TcpPeriodicTimeoutHandler+348 (perf)
05 fffff800044097a0 fffff800030d16f6 nt!KiProcessTimerDpcTable+6c 
06 fffff80004409810 fffff800030d15de nt!KiProcessExpiredTimerList+c6 
07 fffff80004409e60 fffff800030d13c7 nt!KiTimerExpiration+1be 
08 fffff80004409f00 fffff800030c9d15 nt!KiRetireDpcList+277 
09 fffff80004409fb0 fffff800030c9b2c nt!KxRetireDpcList+5 
0a fffff880071682a0 0000000000000000 nt!KiDispatchInterruptContinue+0

Remove:

Start Menu\Programs\ASUS
Start Menu\Programs\ASUS\AI Suite II
Start Menu\Programs\ASUS\PC Diagnostics

Please remove the above programs, since they are simply factory bloatware, which can slow down and corrupt your system. The AI Suite II is especially problematic.

Start Menu\Programs\Java

Do you even require Java? What programs or webpages require Java?

No AV or on demand scanners installed?

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

How many passes of MemTest86+ did you run?

What hard drive diagnostic tools did you run? How long? What tests?

What do mean by farks, when running the graphics card test?

 

[wnight77]

Start Menu\Programs\ASUS
Start Menu\Programs\ASUS\AI Suite II
Start Menu\Programs\ASUS\PC Diagnostics

Removed,


i do not wish to install an antivirus this is a 100% fresh install on a 100% new HDD i did this to see if it would eliminate the BSD and it did not. also as i stated scanned new and old HDD with chkdsk and hdtune

we have had like 8 more BSD let me upload the new info

ntoskrnl.exe+75b80

also i noticed it always seems to be this address.

 

[wnight77]

100313-14554-01.dmp 10/3/2013 2:36:47 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`030d8ec9 afd.sys afd.sys+53882 Ancillary Function Driver for WinSock Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75b80

C:\Windows\Minidump\100313-14554-01.dmp 4 15 7601 277,136 10/3/2013 2:37:22 AM

100313-14180-01.dmp 10/3/2013 2:32:53 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`030e4470 fffff880`08234f60 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75b80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18229 (win7sp1_gdr.130801-1533) x64 ntoskrnl.exe+75b80

C:\Windows\Minidump\100313-14180-01.dmp 4 15 7601 277,136 10/3/2013 2:34:19 AM

100313-15475-01.dmp 10/3/2013 2:27:06 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`030e2ec9 ntoskrnl.exe ntoskrnl.exe+75b80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18229 (win7sp1_gdr.130801-1533) x64 ntoskrnl.exe+75b80

C:\Windows\Minidump\100313-15475-01.dmp 4 15 7601 277,136 10/3/2013 2:27:41 AM

100313-15444-01.dmp 10/3/2013 2:26:06 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`0337bfb4 fffff880`03c34d00 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75b80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18229 (win7sp1_gdr.130801-1533) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100313-15444-01.dmp 4 15 7601 277,136 10/3/2013 2:26:41 AM

100313-15147-01.dmp 10/3/2013 2:19:44 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`03082ec9 ntoskrnl.exe ntoskrnl.exe+75b80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18229 (win7sp1_gdr.130801-1533) x64 ntoskrnl.exe+75b80

C:\Windows\Minidump\100313-15147-01.dmp 4 15 7601 277,136 10/3/2013 2:20:28 AM

100213-15022-01.dmp 10/2/2013 7:27:46 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`030e2ec9 dxgmms1.sys dxgmms1.sys+c759 DirectX Graphics MMS Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18126 (win7sp1_gdr.130409-1534) x64 ntoskrnl.exe+75b80

C:\Windows\Minidump\100213-15022-01.dmp 4 15 7601 277,136 10/2/2013 7:28:30 PM

100213-14476-01.dmp 10/2/2013 6:16:14 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000008 00000000`00000002 00000000`00000001 fffff800`030ceec9 ntoskrnl.exe ntoskrnl.exe+75b80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18229 (win7sp1_gdr.130801-1533) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100213-14476-01.dmp 4 15 7601 277,136 10/2/2013 6:16:54 PM

 

[wnight77]

How many passes of MemTest86+ did you run?
about 4 hours - 4 passes or so

What hard drive diagnostic tools did you run? How long? What tests?
HDtune and ChkDsk

What do mean by farks, when running the graphics card test?
meant Furmark
FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

 

[wnight77]

im currently running with all audio drivers/devices turned off to see if the bluescreen stops.

 

[x BlueRobot]

0: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`0f0ab000 fffff880`0fcf2000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Sat Aug 31 01:02:50 2013[/COLOR] (522132AA)
    CheckSum:         00BF596C
    ImageSize:        00C47000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your AMD graphics card driver seems to be problematic, please update to the latest WHQL version from here: Support & Drivers

WHQL
Release Date: September 18th 2013
Version: 13.9
In Device Manager: 13.152

0: kd> [COLOR="SeaGreen"]lmvm AtihdW76[/COLOR]

start             end                 module name
fffff880`040f1000 fffff880`0410d000   AtihdW76 T (no symbols)           
    Loaded symbol image file: AtihdW76.sys
    Image path: \SystemRoot\system32\drivers\AtihdW76.sys
    Image name: AtihdW76.sys
    Timestamp:        [COLOR="Red"]Fri Jul 05 19:10:37 2013[/COLOR] (51D70C1D)
    CheckSum:         0001AA85
    ImageSize:        0001C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your ATI Function Driver for HD Audio Service seems to be problematic too, please update from the AMD Support Page.

You haven't completed any adequate testing in my opinion, but this seems to be more of a driver problem. Have you enabled Driver Verifier?

 

[wnight77]

yes i have had it running since your first response, however when it crashes now/bluescreens the pc freezes and i do not get a minidump.

P.S. i have updated my graphics drivers again to the newest version again, the reason it was an older version is i was testing to see if the newest version was maybe causing the bluescreen.

i have disabled alot of hardware on the pc now to see if the blue screen will stop.

currently only the Video card is active, onboard network is disabled, onboard sound is disabled.

im using a usb wireless adapter for connectivity. im having trouble understanding the value of driver verifier, since i dont ever really get any useful information from it. i can check and see drivers are loaded with it but no longer getting the minidumps when the pc bluescreens seems bad :/

update, even with everything disabled on the board, and all 3rd party devices removed, <except Vcard> pc was still freezing.

is it possible CPU/Motherboard/Powersupply issue? the power supply is very old the rest of the pc is fairly new. under 6 months. powersupply is about 3 years old or more.

i have redisabled the driver verifier for now so that i can collect some more minidumps.<i left it on for 24 hours and was not able to hit bluescreen even once it always just froze when it was going to crash.

 

[x BlueRobot]

Driver Verifier will cause a 'laggy' effect and freezing, since it's monitoring numerous things with the currently selected drivers e.g Special Pool

Boot into the BIOS, and then post the voltages for the 3.3V, 5V and 12V rails.

 

[wnight77]

Most recent Crash

0x0000003b

100613-13868-01.dmp 10/6/2013 4:42:17 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`032705a8 fffff880`08e73a60 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75b80 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18229 (win7sp1_gdr.130801-1533) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100613-13868-01.dmp 4 15 7601 277,136 10/6/2013 4:43:34 PM

 

[wnight77]

Also Power supply Reports - from bios

3.3V= it was moving between 3.408 <most of the time> and sometimes 3.392
5v=5.120
12v=12.192

i also have some power going to my Vcard <2 of them> not sure if i need to check those as well.

the cpu voltage at the time <in bios> was bouncing between 1.088 and 1.096

 

[x BlueRobot]

Your voltages look fine to me.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="Lime"][COLOR="SeaGreen"]c0000005[/COLOR][/COLOR], fffff800032705a8, fffff88008e73a60, 0}

Probably caused by : ntkrnlmp.exe ( nt!KeInitializeApc+0 )

0: kd> [COLOR="SeaGreen"]lmvm atikmpag[/COLOR]

start             end                 module name
fffff880`04214000 fffff880`042b2000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        [COLOR="Red"]Fri Aug 30 23:32:32 2013[/COLOR] (52211D80)
    CheckSum:         0009C9D2
    ImageSize:        0009E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Are you sure you have updated the graphics card driver?

 fffff88008e73a60 -- ([COLOR="SeaGreen"].cxr 0xfffff88008e73a60[/COLOR])
rax=fffffa8008d0a980 rbx=fffff88008e744c8 [COLOR="Red"]rcx=0000000000000000[/COLOR]
rdx=fffffa8008d0a930 rsi=fffff900c226da20 rdi=0000000000000020
rip=fffff800032705a8 rsp=fffff88008e74448 rbp=0000000000000005
 r8=0000000000000000  r9=0000000000000000 r10=fffff900c0200000
r11=fffffa8008d0a930 r12=0000000000000000 r13=000000000025fd20
r14=000000000025cdb0 r15=0000000075122450
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
[COLOR="Blue"]nt!KeInitializeApc[/COLOR]:
fffff800`032705a8 c60112          mov     byte ptr [COLOR="Red"][rcx][/COLOR],12h ds:002b:00000000`00000000=??

0: kd> [COLOR="SeaGreen"]dt nt!_KAPC[/COLOR]
   +0x000 Type             : UChar
   +0x001 SpareByte0       : UChar
   +0x002 Size             : UChar
   +0x003 SpareByte1       : UChar
   +0x004 SpareLong0       : Uint4B
   +0x008 Thread           : Ptr64 _KTHREAD
   +0x010 ApcListEntry     : _LIST_ENTRY
   +0x020 KernelRoutine    : Ptr64     void 
   +0x028 RundownRoutine   : Ptr64     void 
   +0x030 NormalRoutine    : Ptr64     void 
   +0x038 NormalContext    : Ptr64 Void
   +0x040 SystemArgument1  : Ptr64 Void
   +0x048 SystemArgument2  : Ptr64 Void
   +0x050 ApcStateIndex    : Char
   +0x051 ApcMode          : Char
   +0x052 Inserted         : UChar

The last instruction which seems to be caused a context switch to save the thread's context and then produce a bugcheck is nt!KeInitializeApc (undocumented), which is used to create and fill the fields of the above data structure.

The function prototype for nt!KeInitializeApc is here:

NTKERNELAPI VOID KeInitializeApc (

IN PRKAPC Apc,

IN PKTHREAD Thread,

IN KAPC_ENVIRONMENT Environment,

IN PKKERNEL_ROUTINE KernelRoutine, <-- Called at IRQL Level 2

IN PKRUNDOWN_ROUTINE RundownRoutine OPTIONAL,

IN PKNORMAL_ROUTINE NormalRoutine OPTIONAL,

IN KPROCESSOR_MODE ApcMode,

IN PVOID NormalContext

);

The KernelRoutine parameter contains a pointer to the function which will be called when the APC is dispatched, and is executed at the IRQL Level of 2, although, the current thread only has a IRQL Level of 0, so my best guess is that routine was called at the wrong IRQL Level?

Please run http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html for a few hours, and do not let the temperature exceed 90*C.

GPU-Z Video card GPU Information Utility is a good program for monitoring GPU temperature.

 

[wnight77]

Are you sure you have updated the graphics card driver?

If it is not showing the correct driver i can again try updating it thats strange though,

I uninstalled the old driver, used DriverSweeper
Guru3D - Driver Sweeper

<kind of an older version but i like it>

and Reinstalled with the new driver,

AMD Catalyst? Display Driver for Windows 7/Windows 8 64-bit
http://www2.ati.com/drivers/13-9_win7_win8_64_dd_ccc_whql.exe


i ran furmark for about 1 hour before coming to this forum, however i can try it again for about 2 hours if you think it will help i dont mind

Please run http://www.sevenforums.com/bsod-hel.../bsod-help-support/tutorials...t-furmark.html for a few hours, and do not let the temperature exceed 90*C.



the Gfx Card i have is a...

XFX Double D FX-787A-CDFC Radeon HD 7870 GHz Edition 2GB 256-bit GDDR5 PCI Express 3.0 x16 HDCP Ready CrossFireX Support Video Card - Newegg.com


P.S.

We have not had a crash in 1 day, what "seems" to have at least temporary stop the crashing was i removed all usb devices from usb 3.0 ports and am currently only using 2 usb 2.0 ports that are a totally different bus<chipset>/wtv that the other ports.

 

[wnight77]

we had 2 more crashes today.

here are the minidumps and the loaded drivers.

100713-15724-01.dmp 10/7/2013 3:00:58 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`000d3aa0 fffff880`059e8b50 00000000`00000000 Ntfs.sys Ntfs.sys+93c6f NT File System Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100713-15724-01.dmp 4 15 7601 277,192 10/7/2013 3:02:09 PM

100713-13338-01.dmp 10/7/2013 2:58:07 PM ATTEMPTED_WRITE_TO_READONLY_MEMORY 0x000000be fffff880`03bce444 00000002`0f126121 fffff880`08a6e020 00000000`0000000a USBPORT.SYS USBPORT.SYS+2d444 USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75b80 C:\Windows\Minidump\100713-13338-01.dmp 4 15 7601 277,192 10/7/2013 2:59:17 PM

 

[x BlueRobot]

Remember to look for any screen distortions or artifacts during Furmark.

[COLOR=Red]BugCheck BE[/COLOR], {[COLOR=SeaGreen]fffff88003bce444[/COLOR], 20f126121, fffff88008a6e020, a}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetCurrentFrame+26 )

0: kd> [COLOR=SeaGreen]!dpx[/COLOR]
Start memory scan  : 0xfffff88008a6deb8 ($csp)
End memory scan    : 0xfffff88008a6f000 (Stack Base)

0xfffff88008a6dec8 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e018 : 0xfffff800032d5cae : nt!KiPageFault+0x16e
0xfffff88008a6e020 : 0x0000000000002710 :  Trap @ fffff88008a6e020
0xfffff88008a6e038 : 0xfffff88003bce42c : USBPORT!USBPORT_IsrDpc
0xfffff88008a6e058 : 0xfffff800034dc8a0 : nt!IopTimerQueueHead
0xfffff88008a6e060 : 0xfffff88003bce434 : USBPORT!USBPORT_IsrDpc+0x8
0xfffff88008a6e068 : 0xfffff80003512240 : nt!IopTimerLock
0xfffff88008a6e088 : 0xfffff800032da0ea : nt!KeWaitForMultipleObjects+0x272
0xfffff88008a6e0f0 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e188 : 0xfffff800036d5777 : nt!IoInitializeTimer+0x77
0xfffff88008a6e1d8 : 0xfffff88003ba2628 : USBPORT!MPf_Get32BitFrameNumber+0xa0
0xfffff88008a6e208 : 0xfffff88003bae34d : USBPORT!USBPORTBUSIF_UsbdBusQueryBusTime+0x6d
0xfffff88008a6e238 : 0xfffff88006000f7a : usbaudio!USBHwGetCurrentFrame+0x26
0xfffff88008a6e268 : 0xfffff88006001081 : usbaudio!UsbHwFrameCountTimestamp+0x89
0xfffff88008a6e298 : 0xfffff8000340b30d : nt!ExFreePoolWithTag+0x22d
0xfffff88008a6e2e8 : 0xfffff880060012ca : usbaudio!USBHwGetClockRatio+0x186
0xfffff88008a6e358 : 0xfffff880060016f0 : usbaudio!USBType1RenderBytePosition+0x70
0xfffff88008a6e3d8 : 0xfffff88006010247 : usbaudio!PropertyGetAudioPositionEx+0x4b
0xfffff88008a6e3f8 : 0xfffff880044a7500 : ks!PinAutomationTable+0x110
0xfffff88008a6e418 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f
0xfffff88008a6e458 : 0xfffff80003467588 : nt!NonPagedPoolDescriptor+0x8
0xfffff88008a6e460 : 0xfffff8800449f590 : ks!WPP_ThisDir_CTLGUID_AvStream+0xe0
0xfffff88008a6e468 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e488 : 0xfffff880044a9b47 : ks!KspHandleAutomationIoControl+0x2c7
0xfffff88008a6e4c8 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
0xfffff88008a6e4f0 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
0xfffff88008a6e4f8 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e508 : 0xfffff880044aa183 : ks!CKsPin::DispatchDeviceIoControl+0x11f
0xfffff88008a6e568 : 0xfffff880044a97bb : ks!KsDispatchIrp+0xdb
0xfffff88008a6e598 : 0xfffff88004490560 : ks!CKsDevice::PassThroughIrp+0xc0
0xfffff88008a6e638 : 0xfffff8000340bd0e : nt!ExAllocatePoolWithTag+0xfe
0xfffff88008a6e658 : 0xfffff80003489b80 : nt!ObTypeIndexTable
0xfffff88008a6e748 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f

[...]

0: kd> [COLOR=SeaGreen]lmvm ladfGSRamd64[/COLOR]
Browse full module list
start             end                 module name
fffff880`060db000 fffff880`060f2880   ladfGSRamd64 T (no symbols)           
    Loaded symbol image file: ladfGSRamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
    Image name: ladfGSRamd64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=DarkRed][COLOR=Red]Mon Apr 15 19:39:15 2013[/COLOR][/COLOR] (516C4953)
    CheckSum:         0001C16A
    ImageSize:        00017880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your driver for the Logitech GSeries Headset seems to be causing problems, please check for any updates/patches from here - http://www.logitech.com/en-us/support

The driver most likely has attempted to execute a virtual address which has the Executable protection bit clear, the !pte would have been useful but this is Minidump and this information wasn't retained.

 

[wnight77]

Remember to look for any screen distortions or artifacts during Furmark.

[COLOR=Red]BugCheck BE[/COLOR], {[COLOR=SeaGreen]fffff88003bce444[/COLOR], 20f126121, fffff88008a6e020, a}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetCurrentFrame+26 )

0: kd> [COLOR=SeaGreen]!dpx[/COLOR]
Start memory scan  : 0xfffff88008a6deb8 ($csp)
End memory scan    : 0xfffff88008a6f000 (Stack Base)

0xfffff88008a6dec8 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e018 : 0xfffff800032d5cae : nt!KiPageFault+0x16e
0xfffff88008a6e020 : 0x0000000000002710 :  Trap @ fffff88008a6e020
0xfffff88008a6e038 : 0xfffff88003bce42c : USBPORT!USBPORT_IsrDpc
0xfffff88008a6e058 : 0xfffff800034dc8a0 : nt!IopTimerQueueHead
0xfffff88008a6e060 : 0xfffff88003bce434 : USBPORT!USBPORT_IsrDpc+0x8
0xfffff88008a6e068 : 0xfffff80003512240 : nt!IopTimerLock
0xfffff88008a6e088 : 0xfffff800032da0ea : nt!KeWaitForMultipleObjects+0x272
0xfffff88008a6e0f0 : 0xfffff88003bce444 : USBPORT!USBPORT_IsrDpc+0x18
0xfffff88008a6e188 : 0xfffff800036d5777 : nt!IoInitializeTimer+0x77
0xfffff88008a6e1d8 : 0xfffff88003ba2628 : USBPORT!MPf_Get32BitFrameNumber+0xa0
0xfffff88008a6e208 : 0xfffff88003bae34d : USBPORT!USBPORTBUSIF_UsbdBusQueryBusTime+0x6d
0xfffff88008a6e238 : 0xfffff88006000f7a : usbaudio!USBHwGetCurrentFrame+0x26
0xfffff88008a6e268 : 0xfffff88006001081 : usbaudio!UsbHwFrameCountTimestamp+0x89
0xfffff88008a6e298 : 0xfffff8000340b30d : nt!ExFreePoolWithTag+0x22d
0xfffff88008a6e2e8 : 0xfffff880060012ca : usbaudio!USBHwGetClockRatio+0x186
0xfffff88008a6e358 : 0xfffff880060016f0 : usbaudio!USBType1RenderBytePosition+0x70
0xfffff88008a6e3d8 : 0xfffff88006010247 : usbaudio!PropertyGetAudioPositionEx+0x4b
0xfffff88008a6e3f8 : 0xfffff880044a7500 : ks!PinAutomationTable+0x110
0xfffff88008a6e418 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f
0xfffff88008a6e458 : 0xfffff80003467588 : nt!NonPagedPoolDescriptor+0x8
0xfffff88008a6e460 : 0xfffff8800449f590 : ks!WPP_ThisDir_CTLGUID_AvStream+0xe0
0xfffff88008a6e468 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e488 : 0xfffff880044a9b47 : ks!KspHandleAutomationIoControl+0x2c7
0xfffff88008a6e4c8 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
0xfffff88008a6e4f0 : 0xfffff8800449f510 : ks!WPP_ThisDir_CTLGUID_AvStream+0x60
0xfffff88008a6e4f8 : 0xfffff880044a2110 : ks!WPP_GLOBAL_Control
0xfffff88008a6e508 : 0xfffff880044aa183 : ks!CKsPin::DispatchDeviceIoControl+0x11f
0xfffff88008a6e568 : 0xfffff880044a97bb : ks!KsDispatchIrp+0xdb
0xfffff88008a6e598 : 0xfffff88004490560 : ks!CKsDevice::PassThroughIrp+0xc0
0xfffff88008a6e638 : 0xfffff8000340bd0e : nt!ExAllocatePoolWithTag+0xfe
0xfffff88008a6e658 : 0xfffff80003489b80 : nt!ObTypeIndexTable
0xfffff88008a6e748 : 0xfffff880044a958f : ks!KspPropertyHandler+0x71f

[...]

0: kd> [COLOR=SeaGreen]lmvm ladfGSRamd64[/COLOR]
Browse full module list
start             end                 module name
fffff880`060db000 fffff880`060f2880   ladfGSRamd64 T (no symbols)           
    Loaded symbol image file: ladfGSRamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
    Image name: ladfGSRamd64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=DarkRed][COLOR=Red]Mon Apr 15 19:39:15 2013[/COLOR][/COLOR] (516C4953)
    CheckSum:         0001C16A
    ImageSize:        00017880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your driver for the Logitech GSeries Headset seems to be causing problems, please check for any updates/patches from here - Logitech Support - Downloads, Manuals, FAQs & More

The driver most likely has attempted to execute a virtual address which has the Executable protection bit clear, the !pte would have been useful but this is Minidump and this information wasn't retained.

i installed the new version of the driver, lets hope the pc finally settles down and stops bluescreening, its like every day it develops a new reason to bluescreen :/ its been good since the last crash so far tho. <after updating the driver>

 

[x BlueRobot]

That's good news, please keep me posted

 

[wnight77]

welp the blue screens have reappeared again for some reason, nothing was changed either...

110113-10358-01.dmp 11/1/2013 10:25:25 PM APC_INDEX_MISMATCH 0x00000001 00000000`75332e09 00000000`00000000 00000000`0000ffff fffff880`0840fb60 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-10358-01.dmp 4 15 7601 277,192 11/1/2013 10:26:24 PM
110113-11388-01.dmp 11/1/2013 7:48:48 PM BUGCODE_USB_DRIVER 0x000000fe 00000000`00000006 fffffa80`08280a18 00000000`63706458 00000000`00000000 USBPORT.SYS USBPORT.SYS+2d27d USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-11388-01.dmp 4 15 7601 277,192 11/1/2013 7:49:55 PM
110113-10717-01.dmp 11/1/2013 4:18:44 PM ATTEMPTED_WRITE_TO_READONLY_MEMORY 0x000000be fffff880`0442d444 00000002`0f159121 fffff880`09512020 00000000`0000000a USBPORT.SYS USBPORT.SYS+2d444 USB 1.1 & 2.0 Port Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-10717-01.dmp 4 15 7601 277,192 11/1/2013 4:19:44 PM
110113-11840-01.dmp 11/1/2013 12:29:37 AM 0x00000116 fffffa80`07e85010 fffff880`040f0e5c 00000000`00000000 00000000`00000002 dxgkrnl.sys dxgkrnl.sys+5d140 DirectX Graphics Kernel Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18228 (win7sp1_gdr.130731-2222) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\110113-11840-01.dmp 4 15 7601 615,640 11/1/2013 12:30:45 AM

 

[x BlueRobot]

[COLOR="Red"]BugCheck BE[/COLOR], {[COLOR="SeaGreen"]fffff8800442d444[/COLOR], 20f159121, fffff88009512020, a}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetCurrentFrame+26 )

0: kd> [COLOR="SeaGreen"]lmvm ladfGSRamd64[/COLOR]
start             end                 module name
fffff880`03fb8000 fffff880`03fcf880   ladfGSRamd64 T (no symbols)           
    Loaded symbol image file: ladfGSRamd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfGSRamd64.sys
    Image name: ladfGSRamd64.sys
    Timestamp:        [COLOR="Red"]Mon Apr 15 19:39:15 2013[/COLOR] (516C4953)
    CheckSum:         0001C16A
    ImageSize:        00017880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Logitech Headset driver seems to be causing problems again, did you manage to update the driver? If so, it may be a good idea to remove the driver completely and then see if any problems arise.

[COLOR="Red"]BugCheck 1[/COLOR], {75332e09, 0, [COLOR="SeaGreen"]ffff[/COLOR], fffff8800840fb60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

We can see from the above bugcheck, that a thread has disabled Special APC's and Kernel APC's without re-enabling again, leading to the bugcheck. This is caused by drivers.

The thread must have entered a Guarded Region, which is synchronization mechanism used to allow only one thread to use a certain resource, the resource acquisition is protected from other threads.

0: kd> [COLOR="SeaGreen"]!irql[/COLOR]
Debugger saved IRQL for processor 0x0 -- 0 (LOW_LEVEL)

We can see that the IRQL Level has dropped back to 0, and is no longer at IRQL Level 2, therefore APC's should have been enabled again when leaving the Guarded Region.

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html