Windows 7 x64, Help request to track down BSOD cause

[rurounikamv]

Hello, hopefully some of the gurus might be able to help track down the cause of a resent string of BSODs I'm seeing.

Quick background recap, I had previously been suffering from another unknown BSOD issue that was very quickly identified with help on these boards after dealing with the issue for several months and installs, but over the last couple of weeks a new one has seemed to appear.

I have run memtest for a 15 hour period without any errors and all of the hardware, except for the psu, was recently put through tests in the shop back in early august and came back clean.

My system information is as follows:
OS: Windows 7 Ent x64
Memory: Corsair Dominator 4x2gb
Mobo: GA-MA790FXT-UD5P Gigabyte
Drives: 2x 1.5TB Seagate 7200.11 (one currently not connected) , 1 x 1TB Seagate 7200.12 (primary)
GFX: Nvidia GTX 295
CPU: AMD Phenom II 955BE 3.2 Ghz
PSU: Zalaman 1000w - PSU is the only piece of hardware that was not tested.


I know they don't help much in way of hardware bsods but here is the reports from WhoCrashed:

On Sat 9/25/2010 7:55:28 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\092510-15818-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 9/23/2010 5:04:38 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\092310-15802-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 9/16/2010 4:47:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3D (0xFFFFF88002FFD090, 0x0, 0x0, 0xFFFFF80002C90203)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\091610-17596-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

My SFC SCANNOW Result: no integrity violations found

Minidumps and Windows 7 BSOD Tool and Perfmon report. Hopefully we can figure this thing out and thanks a lot to anyone willing to trudge through this stuff to help me.

 

[Capt.Jack Sparrow]

Hello and Welcome !

Seems like dumps are pointing to Core Windows Files. Lets try few basic steps.

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

Few crashes is pointing to USB Port. If you have anything connected to USB port disconnect it and 2 or 3 days and see if that crashes like Gaming pad, Webcam etc.

Follow this article and Enable Driver Verifier http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Bugcheck

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88002ffd090
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff80002c90203
Debugging Details:
------------------

CONTEXT:  fffff88002ffd090 -- (.cxr 0xfffff88002ffd090)
rax=0000000000216066 rbx=fffff88002fd5180 rcx=f7fffa8007112be0
rdx=0000319800000000 rsi=fffffa8006fd1900 rdi=f7fffa8007112be0
rip=fffff80002c90203 rsp=fffff88002ffda60 rbp=0000000000000000
 r8=fffff88002fdffc0  r9=0000000000000000 r10=000000000000cba6
r11=00000000002f9d00 r12=0000000000000000 r13=fffffa8008e8c400
r14=fffffa8008e8c600 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!KeAcquireSpinLockAtDpcLevel+0x43:
fffff800`02c90203 f0480fba2900    lock bts qword ptr [rcx],0 ds:002b:f7fffa80`07112be0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
CURRENT_IRQL:  5
LAST_CONTROL_TRANSFER:  from fffff80002c8532c to fffff80002c90203
STACK_TEXT:  
fffff880`02ffda60 fffff800`02c8532c : fffffa80`06fd19c8 00000000`00000000 fffffa80`06fd19c0 fffff800`02c96618 : nt!KeAcquireSpinLockAtDpcLevel+0x43
fffff880`02ffdab0 fffff800`02c85118 : 00000000`00000000 fffff880`02ffdb80 fffff880`02fd5180 00000000`00000001 : nt!KiScanInterruptObjectList+0x5c
fffff880`02ffdb00 fffff880`03f777f2 : fffff800`02c9724a 00000000`002fe711 fffffa80`08e8c498 fffff880`02fdffc0 : nt!KiChainedDispatch+0x128
fffff880`02ffdc98 fffff800`02c9724a : 00000000`002fe711 fffffa80`08e8c498 fffff880`02fdffc0 00000000`00000001 : amdppm!C1Halt+0x2
fffff880`02ffdca0 fffff800`02c91ebc : fffff880`02fd5180 fffff880`00000000 00000000`00000000 fffff880`040a9db0 : nt!PoIdle+0x53a
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x2c

FOLLOWUP_IP: 
nt!KeAcquireSpinLockAtDpcLevel+43
fffff800`02c90203 f0480fba2900    lock bts qword ptr [rcx],0
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KeAcquireSpinLockAtDpcLevel+43
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
STACK_COMMAND:  .cxr 0xfffff88002ffd090 ; kb
FAILURE_BUCKET_ID:  X64_0x3D_nt!KeAcquireSpinLockAtDpcLevel+43
BUCKET_ID:  X64_0x3D_nt!KeAcquireSpinLockAtDpcLevel+43
Followup: MachineOwner
---------

Hope this helps,
Captain

 

[rurounikamv]

Thanks for taking a look through the files Captain. I have a few time commitments I'm juggling atm but I'll go through the recommended steps and update when completed.