Windows 7: Random BSOD's Please help!

azah · 12 Mar 2011

Hello!
I'm running a dualboot system (one for pro audio, one for gaming).
Both are Windows 7 x64 Ultimate OEM.
One of the systems (gaming) recently started acting very weird BSOD's at random - in the middle of the night (it's on 24/7) - while gaming - while browsing.
The temperatures are completely normal (40-50C)
First thinking memory trouble as i added 6GB more to a total of 12GB;
However the pro audio system isn't BSOD'ing ever!?

I've tried WinDbg and just about everything to find the culprit.

Please please somebody help, what is the matter?!

Attached a complete Windows_NT6_BSOD_jcgriff2 folder.

Many many thanks in advance.

**yowanvista** · 12 Mar 2011

Information

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

Code:

sptd.sys        fffff880`01029000    fffff880`0114f000    0x00126000    0x4ad24632    12/10/2009 00:55:14

Since no probable cause is being indicated enable driver verifier to locate the possible drivers causing the BSODs
Driver Verifier - Enable and Disable
Then upload the dumps which are created

Update your Lan/Networking drivers

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffae009537550, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030ac970, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b70e8
 fffffae009537550 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`030ac970 f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  fffff8800ee2bee0 -- (.trap 0xfffff8800ee2bee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c3062000 rbx=0000000000000000 rcx=fffff900c306b000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000133fe0 rsp=fffff8800ee2c078 rbp=0000000000000001
 r8=0000000000000028  r9=000000000000215a r10=0000000000000034
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
win32k!memset+0xb0:
fffff960`00133fe0 480fc311        movnti  qword ptr [rcx],rdx ds:0001:fffff900`c306b000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003085be9 to fffff80003086640

STACK_TEXT:  
fffff880`0ee2b718 fffff800`03085be9 : 00000000`0000000a fffffae0`09537550 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0ee2b720 fffff800`03084860 : fffff900`00000000 fffff880`0ee2c0e0 fffff900`c00c0020 fffffae0`09537540 : nt!KiBugCheckDispatch+0x69
fffff880`0ee2b860 fffff800`030ac970 : 00000011`00000020 fffff960`001c87f1 00000000`00000000 fffff960`0013b556 : nt!KiPageFault+0x260
fffff880`0ee2b9f0 fffff800`030ab12f : fffffa80`09c00460 00000000`0000001c fffffa80`09543540 00000000`0000001c : nt!MiReplenishPageSlist+0xc0
fffff880`0ee2ba60 fffff800`030972af : 00000000`00000002 fffff880`00000002 fffff880`07551c00 00000000`00000000 : nt!MiRemoveAnyPage+0x24f
fffff880`0ee2bb80 fffff800`030a41ce : 00000000`00000001 fffff900`c306b000 fffff880`0ee2bee0 fffff6fc`80618358 : nt!MiResolveDemandZeroFault+0x54f
fffff880`0ee2bc70 fffff800`0309443b : 00000000`0024fd20 00000000`00000000 00000000`00240000 fffff800`030858d3 : nt!MiDispatchFault+0x8ce
fffff880`0ee2bd80 fffff800`0308476e : 00000000`00000001 fffff900`c306b000 00000000`00240000 fffff900`c3062000 : nt!MmAccessFault+0xe1b
fffff880`0ee2bee0 fffff960`00133fe0 : fffff960`00122e06 fffff900`c3780a70 00000000`00000000 fffff960`00144264 : nt!KiPageFault+0x16e
fffff880`0ee2c078 fffff960`00122e06 : fffff900`c3780a70 00000000`00000000 fffff960`00144264 fffff960`001345ed : win32k!memset+0xb0
fffff880`0ee2c080 fffff960`00124320 : 00000000`00000000 fffff880`0ee2c220 00000000`00000001 fffff960`0012191a : win32k!AllocateObject+0xf2
fffff880`0ee2c0c0 fffff960`000fb610 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1f8
fffff880`0ee2c1b0 fffff960`000fb18a : 00000072`000004fe 00000000`00000072 00000000`01080030 00000000`000004fe : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`0ee2c280 fffff800`030858d3 : fffffa80`0d3bfb60 fffff880`0ee2c3e0 00000000`00000000 fffff900`c0136010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`0ee2c360 00000000`73542e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0024d3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73542e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!memset+b0
fffff960`00133fe0 480fc311        movnti  qword ptr [rcx],rdx

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  win32k!memset+b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2415ea

FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0

BUCKET_ID:  X64_0xA_win32k!memset+b0

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

azah · 13 Mar 2011

I've uninstalled Daemon Tools, and i know it's dodgy software - but i use it on my other installation and never had it BSOD on me.
The uninstallation didn't come without trouble though, it BSOD'ed on me atleast 3-4 times. Heh.

I also enabled driver verfier, and just today got a BSOD while gaming.

Attached the minidump, does the driver verifier generate any other dump?

azah · 13 Mar 2011

Wow. Now the machine blew up!

Can't install any Virtual Drive program now it seems!
During installation of MagicDisc i get a BSOD refering to pxhlpa64.sys.
First boot it hangs at Windows logo.
Second boot it successfully boots to Desktop,
but BSOD's as soon as the Desktop is fully loaded with the same reference.

After a safe mode boot and uninstall it reverted.

Tried Virtual Clonedrive from Slysoft.
Exactly the same procedure!

Attaching the dumps.

**yowanvista** · 13 Mar 2011

pxhlpa64.sys is a driver used by PxHelp by Sonic solutions, please remove that software in safe mode

Remove any itunes software and update any DVD burning software, they use a driver GEARAspiWDM.sys which is mentioned in your dumps

Code:

BugCheck C9, {224, fffff880010bd938, fffff9802d718ca0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
Unable to load image \SystemRoot\System32\Drivers\PxHlpa64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
Probably caused by : PxHlpa64.sys ( PxHlpa64+8938 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
    IRP's IoStatus.Status field.
Arg2: fffff880010bd938, The address in the driver's code where the error was detected.
Arg3: fffff9802d718ca0, IRP address.
Arg4: 0000000000000002, Expected status code.

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


BUGCHECK_STR:  0xc9_224

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  224

FAULTING_IP: 
PxHlpa64+8938
fffff880`010bd938 53              push    rbx

FOLLOWUP_IP: 
PxHlpa64+8938
fffff880`010bd938 53              push    rbx

IRP_ADDRESS:  fffff9802d718ca0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000351c3dc to fffff80003095640

STACK_TEXT:  
fffff880`035771a8 fffff800`0351c3dc : 00000000`000000c9 00000000`00000224 fffff880`010bd938 fffff980`2d718ca0 : nt!KeBugCheckEx
fffff880`035771b0 fffff800`0352647a : fffff800`0351a9f0 fffff880`010bd938 fffff980`2d718ca0 00000000`00000002 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035771f0 fffff800`035273f3 : fffff880`010bd938 fffffa80`0d4c2d28 00000000`00000002 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03577240 fffff800`03532759 : fffffa80`0d4c2c70 fffffa80`0d4c2c70 fffffa80`0d4c2d28 fffff880`010bf778 : nt!VfErrorReport4+0x83
fffff880`03577330 fffff800`03532b63 : fffffa80`0d4c2c70 00000000`00000002 fffffa80`0bd69030 00000000`00000001 : nt!IovpCallDriver2+0x179
fffff880`03577390 fffff800`03538c2e : fffff980`2d718ca0 fffff980`2d718ca0 00000000`00000002 fffffa80`0bd69030 : nt!VfAfterCallDriver+0x353
fffff880`035773e0 fffff800`0353b4da : fffff980`2d718e48 fffffa80`0bd69030 fffffa80`0d32b430 fffffa80`0d4c2c70 : nt!IovCallDriver+0x57e
fffff880`03577440 fffff800`03538c16 : fffff980`2d718ca0 00000000`00000002 fffffa80`0d32b430 fffffa80`0adbd6e0 : nt!ViFilterDispatchPnp+0xea
fffff880`03577470 fffff880`00ec093c : fffff980`2d718e90 00000000`00000000 fffffa80`0c903170 fffffa80`0adbd6e0 : nt!IovCallDriver+0x566
fffff880`035774d0 fffff880`00eb92ce : 00000000`00000001 fffff880`035775e0 fffff880`03577500 fffffa80`0c903100 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`03577500 fffff880`00eb7dd6 : fffffa80`0c128602 00000000`00000002 00000000`00000000 fffffa80`0c903170 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`03577570 fffff880`00e87245 : fffff980`2d718ca0 fffff980`2d718ca0 fffffa80`0db5e4b0 fffffa80`0db5e4b0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`035775e0 fffff880`00e8714b : fffff880`035776c8 fffff980`2d718ca0 00000000`00000002 fffffa80`0db5e4b0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`03577610 fffff800`03538c16 : fffff980`2d718ca0 00000000`00000002 fffffa80`0db5e4b0 fffff800`0353437e : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`03577650 fffff800`0353b4da : fffff980`2d718ed8 fffffa80`0db5e4b0 fffffa80`0b475930 fffffa80`0d3f7290 : nt!IovCallDriver+0x566
fffff880`035776b0 fffff800`03538c16 : fffff980`2d718ca0 00000000`00000002 fffffa80`0b475930 fffffa80`0df1dbb0 : nt!ViFilterDispatchPnp+0xea
fffff880`035776e0 fffff880`0f28f35b : fffff980`2d718f20 00000000`00000000 fffff980`2d718ca0 fffffa80`0df1dbb0 : nt!IovCallDriver+0x566
fffff880`03577740 fffff980`2d718f20 : 00000000`00000000 fffff980`2d718ca0 fffffa80`0df1dbb0 00000000`00000010 : GEARAspiWDM+0x735b
fffff880`03577748 00000000`00000000 : fffff980`2d718ca0 fffffa80`0df1dbb0 00000000`00000010 00000000`00010246 : 0xfffff980`2d718f20


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  PxHlpa64+8938

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PxHlpa64

IMAGE_NAME:  PxHlpa64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  475dd06d

FAILURE_BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+8938

BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+8938

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
    IRP's IoStatus.Status field.
Arg2: fffff880010bd938, The address in the driver's code where the error was detected.
Arg3: fffff9802d718ca0, IRP address.
Arg4: 0000000000000002, Expected status code.

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


BUGCHECK_STR:  0xc9_224

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  224

FAULTING_IP: 
PxHlpa64+8938
fffff880`010bd938 53              push    rbx

FOLLOWUP_IP: 
PxHlpa64+8938
fffff880`010bd938 53              push    rbx

IRP_ADDRESS:  fffff9802d718ca0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000351c3dc to fffff80003095640

STACK_TEXT:  
fffff880`035771a8 fffff800`0351c3dc : 00000000`000000c9 00000000`00000224 fffff880`010bd938 fffff980`2d718ca0 : nt!KeBugCheckEx
fffff880`035771b0 fffff800`0352647a : fffff800`0351a9f0 fffff880`010bd938 fffff980`2d718ca0 00000000`00000002 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035771f0 fffff800`035273f3 : fffff880`010bd938 fffffa80`0d4c2d28 00000000`00000002 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`03577240 fffff800`03532759 : fffffa80`0d4c2c70 fffffa80`0d4c2c70 fffffa80`0d4c2d28 fffff880`010bf778 : nt!VfErrorReport4+0x83
fffff880`03577330 fffff800`03532b63 : fffffa80`0d4c2c70 00000000`00000002 fffffa80`0bd69030 00000000`00000001 : nt!IovpCallDriver2+0x179
fffff880`03577390 fffff800`03538c2e : fffff980`2d718ca0 fffff980`2d718ca0 00000000`00000002 fffffa80`0bd69030 : nt!VfAfterCallDriver+0x353
fffff880`035773e0 fffff800`0353b4da : fffff980`2d718e48 fffffa80`0bd69030 fffffa80`0d32b430 fffffa80`0d4c2c70 : nt!IovCallDriver+0x57e
fffff880`03577440 fffff800`03538c16 : fffff980`2d718ca0 00000000`00000002 fffffa80`0d32b430 fffffa80`0adbd6e0 : nt!ViFilterDispatchPnp+0xea
fffff880`03577470 fffff880`00ec093c : fffff980`2d718e90 00000000`00000000 fffffa80`0c903170 fffffa80`0adbd6e0 : nt!IovCallDriver+0x566
fffff880`035774d0 fffff880`00eb92ce : 00000000`00000001 fffff880`035775e0 fffff880`03577500 fffffa80`0c903100 : Wdf01000!FxPkgFdo::ProcessRemoveDeviceOverload+0x74
fffff880`03577500 fffff880`00eb7dd6 : fffffa80`0c128602 00000000`00000002 00000000`00000000 fffffa80`0c903170 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x126
fffff880`03577570 fffff880`00e87245 : fffff980`2d718ca0 fffff980`2d718ca0 fffffa80`0db5e4b0 fffffa80`0db5e4b0 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`035775e0 fffff880`00e8714b : fffff880`035776c8 fffff980`2d718ca0 00000000`00000002 fffffa80`0db5e4b0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`03577610 fffff800`03538c16 : fffff980`2d718ca0 00000000`00000002 fffffa80`0db5e4b0 fffff800`0353437e : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`03577650 fffff800`0353b4da : fffff980`2d718ed8 fffffa80`0db5e4b0 fffffa80`0b475930 fffffa80`0d3f7290 : nt!IovCallDriver+0x566
fffff880`035776b0 fffff800`03538c16 : fffff980`2d718ca0 00000000`00000002 fffffa80`0b475930 fffffa80`0df1dbb0 : nt!ViFilterDispatchPnp+0xea
fffff880`035776e0 fffff880`0f28f35b : fffff980`2d718f20 00000000`00000000 fffff980`2d718ca0 fffffa80`0df1dbb0 : nt!IovCallDriver+0x566
fffff880`03577740 fffff980`2d718f20 : 00000000`00000000 fffff980`2d718ca0 fffffa80`0df1dbb0 00000000`00000010 : GEARAspiWDM+0x735b
fffff880`03577748 00000000`00000000 : fffff980`2d718ca0 fffffa80`0df1dbb0 00000000`00000010 00000000`00010246 : 0xfffff980`2d718f20


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  PxHlpa64+8938

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PxHlpa64

IMAGE_NAME:  PxHlpa64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  475dd06d

FAILURE_BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+8938

BUCKET_ID:  X64_0xc9_224_VRF_PxHlpa64+8938

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

azah · 14 Mar 2011

Jesus.. Had another BSOD today.
This time it said dxgmms1.sys
Attaching minidump

azah · 14 Mar 2011

And another one again today.
Minidump;

**yowanvista** · 15 Mar 2011

Reinstall your Nvidia drivers as one of its component, dxgmms1.sys caused the crash

Windows 7: Random BSOD's Please help!

Random BSOD's Please help! problems?