BSOD any game and randomly

writhziden · 23 Nov 2011

Here is a forum that may help. https://www.sevenforums.com/crashes-d...ould-i-do.html

It's old, so don't post there, but try the instructions given by Wallonn7 and report back in this thread.

Edit: And you should run the memtest for five passes before doing the procedure outlined in that thread.

Behemia · 07 Jan 2012

So I tried everything stated in the posts and links to other threads, nothing has worked

I am also now getting PFN_list_corrupt bsod and a USB based one aswell.
On a brighter note, it has finally decided to spit a few DMP files into my minidump folder which is good I guess.
Files are attached if any kind genius would like to help me out :)
Thanks.

writhziden · 07 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Behemia\113011-22620-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329ce90
Debug session time: Wed Nov 30 07:24:08.149 2011 (UTC - 7:00)
System Uptime: 0 days 4:08:48.694
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80014d9f60
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003144fd0 to fffff800030d7640

STACK_TEXT:  
fffff880`04b69588 fffff800`03144fd0 : 00000000`0000001a 00000000`00041790 fffffa80`014d9f60 00000000`0000ffff : nt!KeBugCheckEx
fffff880`04b69590 fffff800`0310afd9 : 00000000`00000000 000007fe`fec68fff 00000000`00000000 fffff800`0325e6c8 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`04b69750 fffff800`030a90a8 : ffffffff`ffffffff fffff880`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`04b69870 fffff800`033ad09a : fffff8a0`0208b920 fffff880`04b69c20 00000000`00000000 fffffa80`044eb390 : nt!MmCleanProcessAddressSpace+0x228
fffff880`04b698c0 fffff800`0339237d : 00000000`40010004 00000000`00000001 000007ff`fffdc000 fffffa80`04463060 : nt!PspExitThread+0x56a
fffff880`04b699c0 fffff800`030cadfa : 00000000`00000001 fffff800`00b96080 fffffa80`043e2180 fffffa80`050bc060 : nt!PsExitSpecialApc+0x1d
fffff880`04b699f0 fffff800`030cb140 : 00000000`00000000 fffff880`04b69a70 fffff800`033922f0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`04b69a70 fffff800`030d6977 : fffffa80`044eb390 00000000`002ff758 fffff880`04b69bc8 fffff880`04b69c00 : nt!KiInitiateUserApc+0x70
fffff880`04b69bb0 00000000`76d618ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`002ff738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d618ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36024
fffff800`03144fd0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Behemia\010612-23197-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03055000 PsLoadedModuleList = 0xfffff800`0329ae90
Debug session time: Fri Jan  6 15:14:43.010 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:23.556
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff88004032710, fffff98004660990, fffffa8004043540}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
	This IRP should either have been completed earlier or should have been passed
	down.
Arg2: fffff88004032710, The address in the driver's code where the error was detected.
Arg3: fffff98004660990, IRP address.
Arg4: fffffa8004043540, ProviderId.

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


BUGCHECK_STR:  0xc9_220

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`04032710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`04032710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff98004660990

DEVICE_OBJECT: fffffa80045d0050

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff800032d1440 -- (!locks fffff800032d1440)

Resource @ nt!PiEngineLock (0xfffff800032d1440)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff800032d1440
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000355c3dc to fffff800030d5640

STACK_TEXT:  
fffff880`02fba0b8 fffff800`0355c3dc : 00000000`000000c9 00000000`00000220 fffff880`04032710 fffff980`04660990 : nt!KeBugCheckEx
fffff880`02fba0c0 fffff800`0356647a : fffff800`0355a9f0 fffff880`04032710 fffff980`04660990 fffffa80`04043540 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02fba100 fffff800`035670ff : 00000000`00000220 fffffa80`04043540 fffff980`04660990 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02fba150 fffff800`0356c6a7 : fffff980`04660f28 fffff880`04032710 00000000`00000000 00000000`00000000 : nt!VfErrorReport10+0x6f
fffff880`02fba230 fffff800`0355c04e : fffffa80`04512e90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
fffff880`02fba260 fffff800`03568b2d : fffffa80`046113c0 fffffa80`045125d0 fffff980`04660990 fffff980`04660990 : nt!VfMajorVerifyIrpStackUpward+0x6e
fffff880`02fba2a0 fffff800`0357a50d : fffff980`04660f28 fffff880`02fba480 00000000`c0000010 fffff980`04660f28 : nt!IovpCompleteRequest2+0xad
fffff880`02fba310 fffff800`030d8a91 : fffff980`04660f2b fffff800`00000000 00000000`000000ff fffff880`00000005 : nt!IovpLocalCompletionRoutine+0x9d
fffff880`02fba370 fffff800`0357219f : fffff980`04660990 fffff880`0403c400 fffffa80`045d0100 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff880`02fba450 fffff800`030bb1ea : fffff880`00000013 fffff880`02fba578 fffff980`04660f28 fffffa80`045d01a0 : nt!IovCompleteRequest+0x19f
fffff880`02fba520 fffff880`04032a0f : 00000000`00000000 fffffa80`045d01a0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`02fba550 fffff880`040327fb : 00000000`00000000 fffffa80`045d01a0 fffff980`04660990 fffff880`02fba600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`02fba590 fffff800`03578c16 : fffff980`00000002 fffff980`04660990 00000000`00000002 fffff800`0357437e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`02fba600 fffff800`03577c42 : fffff980`04660f70 00000000`00000002 fffffa80`045dff50 fffffa80`04553bd0 : nt!IovCallDriver+0x566
fffff880`02fba660 fffff800`03578c16 : fffff980`04660990 00000000`00000002 fffffa80`045dfe00 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
fffff880`02fba690 fffff800`03577d58 : fffff980`04660990 fffffa80`045dfe00 00000000`00000000 fffffa80`043e50c0 : nt!IovCallDriver+0x566
fffff880`02fba6f0 fffff800`03577e42 : fffffa80`04043540 fffffa80`043acd90 fffffa80`04043540 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`02fba760 fffff800`03564faf : fffffa80`042ae270 00000000`000007ff fffff800`0320b5b8 fffff800`03468ca9 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`02fba800 fffff800`0317ec92 : fffffa80`042ae270 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`02fba830 fffff800`034bd26c : fffffa80`042ae270 fffffa80`043acd90 00000000`00000001 00000000`00000002 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`02fba860 fffff800`034bee64 : fffffa80`042ae270 fffffa80`042ae270 fffffa80`043acd90 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`02fba950 fffff800`034bf428 : fffff800`032cedc0 00000000`00000000 00000000`00000010 fffff800`034bf390 : nt!PipProcessDevNodeTree+0x264
fffff880`02fbabc0 fffff800`031ceb97 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`02fbac10 fffff800`030dfa21 : fffff800`031ce870 fffff800`033cbf01 fffffa80`018fe600 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`02fbacb0 fffff800`03372cce : 00000000`00000000 fffffa80`018fe680 00000000`00000080 fffffa80`01866450 : nt!ExpWorkerThread+0x111
fffff880`02fbad40 fffff800`030c6fe6 : fffff880`009e9180 fffffa80`018fe680 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fbad80 00000000`00000000 : fffff880`02fbb000 fffff880`02fb5000 fffff880`02fb96e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Behemia\010612-28080-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03264e90
Debug session time: Fri Jan  6 15:17:39.798 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:29.343
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff88003e87710, fffff9801312c990, fffffa800493e540}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
	This IRP should either have been completed earlier or should have been passed
	down.
Arg2: fffff88003e87710, The address in the driver's code where the error was detected.
Arg3: fffff9801312c990, IRP address.
Arg4: fffffa800493e540, ProviderId.

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


BUGCHECK_STR:  0xc9_220

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`03e87710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`03e87710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff9801312c990

DEVICE_OBJECT: fffffa80046fb050

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff8000329b440 -- (!locks fffff8000329b440)

Resource @ nt!PiEngineLock (0xfffff8000329b440)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff8000329b440
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800035263dc to fffff8000309f640

STACK_TEXT:  
fffff880`02fb30b8 fffff800`035263dc : 00000000`000000c9 00000000`00000220 fffff880`03e87710 fffff980`1312c990 : nt!KeBugCheckEx
fffff880`02fb30c0 fffff800`0353047a : fffff800`035249f0 fffff880`03e87710 fffff980`1312c990 fffffa80`0493e540 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02fb3100 fffff800`035310ff : 00000000`00000220 fffffa80`0493e540 fffff980`1312c990 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02fb3150 fffff800`035366a7 : fffff980`1312cf28 fffff880`03e87710 00000000`00000000 00000000`000001f1 : nt!VfErrorReport10+0x6f
fffff880`02fb3230 fffff800`0352604e : fffffa80`0446ae90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
fffff880`02fb3260 fffff800`03532b2d : fffffa80`046a11e0 fffffa80`0446a5d0 fffff980`1312c990 fffff980`1312c990 : nt!VfMajorVerifyIrpStackUpward+0x6e
fffff880`02fb32a0 fffff800`0354450d : fffff980`1312cf28 fffff880`02fb3480 00000000`c0000010 fffff980`1312cf28 : nt!IovpCompleteRequest2+0xad
fffff880`02fb3310 fffff800`030a2a91 : fffff980`1312cf2b fffff800`00000000 00000000`000000ff fffff880`00000005 : nt!IovpLocalCompletionRoutine+0x9d
fffff880`02fb3370 fffff800`0353c19f : fffff980`1312c990 fffff880`03e91400 fffffa80`046fb100 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff880`02fb3450 fffff800`030851ea : fffff880`00000013 fffff880`02fb3578 fffff980`1312cf28 fffffa80`046fb1a0 : nt!IovCompleteRequest+0x19f
fffff880`02fb3520 fffff880`03e87a0f : 00000000`00000000 fffffa80`046fb1a0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`02fb3550 fffff880`03e877fb : 00000000`00000000 fffffa80`046fb1a0 fffff980`1312c990 fffff880`02fb3600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`02fb3590 fffff800`03542c16 : fffff980`00000002 fffff980`1312c990 00000000`00000002 fffff800`0353e37e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`02fb3600 fffff800`03541c42 : fffff980`1312cf70 00000000`00000002 fffffa80`04517250 fffffa80`03e03230 : nt!IovCallDriver+0x566
fffff880`02fb3660 fffff800`03542c16 : fffff980`1312c990 00000000`00000002 fffffa80`04517100 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
fffff880`02fb3690 fffff800`03541d58 : fffff980`1312c990 fffffa80`04517100 00000000`00000000 fffffa80`0493e1b0 : nt!IovCallDriver+0x566
fffff880`02fb36f0 fffff800`03541e42 : fffffa80`0493e540 fffffa80`01917010 fffffa80`0493e540 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`02fb3760 fffff800`0352efaf : fffffa80`048e4270 00000000`000007ff fffff800`031d55b8 fffff800`03432ca9 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`02fb3800 fffff800`03148c92 : fffffa80`048e4270 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`02fb3830 fffff800`0348726c : fffffa80`048e4270 fffffa80`01917010 00000000`00000001 00000000`00000001 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`02fb3860 fffff800`03488e64 : fffffa80`048e4270 fffffa80`048e4270 fffffa80`01917010 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`02fb3950 fffff800`03489428 : fffffa80`03e52100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x264
fffff880`02fb3bc0 fffff800`03198b97 : 00000001`00000003 00000000`00000000 00000000`00000001 fffffa80`00000084 : nt!PiProcessReenumeration+0x98
fffff880`02fb3c10 fffff800`030a9a21 : fffff800`03198870 fffff800`0323c601 fffffa80`018fcb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`02fb3cb0 fffff800`0333ccce : 00000000`00000000 fffffa80`018fcb60 00000000`00000080 fffffa80`01866450 : nt!ExpWorkerThread+0x111
fffff880`02fb3d40 fffff800`03090fe6 : fffff880`009e9180 fffffa80`018fcb60 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fb3d80 00000000`00000000 : fffff880`02fb4000 fffff880`02fae000 fffff880`02fb32e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0

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

Update the following drivers by using Driver Reference and Drivers and Downloads to find the manufacturers and manufacturer sites.

Code:

wacommousefilter	fffff880`03c67000	fffff880`03c6f000	Fri Feb 16 11:12:17 2007 (45d5f401)	00005ace		wacommousefilter.sys
btwavdt	fffff880`02600000	fffff880`0266b000	Sun Feb 25 22:06:58 2007 (45e26af2)	0001aad1		btwavdt.sys
btwaudio	fffff880`0288b000	fffff880`0290a000	Sun Feb 25 22:08:26 2007 (45e26b4a)	00017fa7		btwaudio.sys
btwrchid	fffff880`0290a000	fffff880`0290d300	Sun Feb 25 22:08:50 2007 (45e26b62)	00010164		btwrchid.sys

Also, since your blue screens are system related, the following possibilities exist.

System file corruption. Run SFC /SCANNOW Command - System File Checker to check for system file corruption.You may have to run it up to three times to fix all errors.
Faulty hardware. 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.
Hard disk errors. Run Disk Check with both boxes checked.
An underlying driver that is incompatible with your system. Run Driver Verifier to find any issues. 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 above 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 non-Microsoft drivers until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Behemia · 08 Jan 2012

Established that it's not likely to be the harddrives, as I ran the pre driver loaded disk checker for all my 3 drives and returned no errors after about 6 hours of testing :/
Ran Verifier.exe and found HIDclass.sys BSOD right away so I'm looking into this now.
Thanks again.

writhziden · 08 Jan 2012

Behemia said:

Established that it's not likely to be the harddrives, as I ran the pre driver loaded disk checker for all my 3 drives and returned no errors after about 6 hours of testing :/
Ran Verifier.exe and found HIDclass.sys BSOD right away so I'm looking into this now.
Thanks again.

See USB Driver - General Fix for Problems for troubleshooting your HIDCLASS.SYS BSODs.

If the problems persist after following the steps in the above, do the following steps.
Updating bluetooth drivers has been known to fix such blue screen errors, as well. Update bluetooth, any memory card reader drivers, and all USB device drivers (external hard drives, mouse, keyboard, gamepads, etc.) as well as the USB hub drivers. Also check all Human Interface Devices and update their drivers.

If you are unable to find updates, uninstall the drivers and then re-install the latest drivers available after restarting your machine.

Behemia · 08 Jan 2012

Tried this, not sure if it didnt work or if I did it wrong

As a bonus my bluetooth headset now works on the pc

I still get HIDclass bsod on verifier, and i get win32k.sys bsod randomly, along with driver_irql not less or equal. but no DMP files are ever produced from these.
I'll try the driver wipe again tomorrow, or maybe next day.
Thanks again, B.

writhziden · 08 Jan 2012

Behemia said:

Tried this, not sure if it didnt work or if I did it wrong

As a bonus my bluetooth headset now works on the pc

I still get HIDclass bsod on verifier, and i get win32k.sys bsod randomly, along with driver_irql not less or equal. but no DMP files are ever produced from these.
I'll try the driver wipe again tomorrow, or maybe next day.
Thanks again, B.

You may have to verify 5-10 drivers at a time to get .dmp files for some failures. Just something to keep in mind. :)

writhziden · 29 Jan 2012

Any luck running Verifier and finding conflicting drivers?

Behemia · 01 Feb 2012

No luck at all, I really did try every piece of advice you guys gave me and nothing worked

Thanks for all the help but I opted to get a new PC instead (i5 ftw ;D )
I'm fairly sure the motherboard was damaged as no matter what windows OS I ran, it continually gave me bsods even on clean installs, nothing running etc

Thanks again for the help though

writhziden · 01 Feb 2012

Yeah, that sounds like a hardware failure. May have been the motherboard or any number of other pieces of hardware, but at least you found a solution you seem happy with. :) You can probably mark this thread as solved. Enjoy the new system.

BSOD any game and randomly

More BSOD :(

Getting there...