BSoDs with no identifiable cause.

spleenharvester · 28 Mar 2011 at 20:59

Keep getting BSoDs.

Firstly, it was related to a faulty DVD driver, PxHlpA64.sys. That cleared up a lot of the random BSoDing (was getting just about any bugcheck you can think of at just about any time imaginable).

Now, I keep getting repeated 0x000001E (although sometimes 0x000001A) BSoDs. Driver verifier shows nothing. Prime95 is completely stable. Memtest86+ returns nothing. Absolutely stumped.

Prepare for some extremely long crashdump debugs:

Code:

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!ExpInterlockedPopEntrySListFault16+0
fffff800`02897565 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ad00e8
 ffffffffffffffff 

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

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800028eb028 to fffff8000289f640

STACK_TEXT:  
fffff880`08b3b098 fffff800`028eb028 : 00000000`0000001e ffffffff`c0000005 fffff800`02897565 00000000`00000000 : nt!KeBugCheckEx
fffff880`08b3b0a0 fffff800`0289ecc2 : fffff880`08b3b878 00000000`00000000 fffff880`08b3b920 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`08b3b740 fffff800`0289d5ca : fffffa80`04a4f5f0 fffff800`028c82de fffffa80`04a4f5f0 fffffa80`04a87b60 : nt!KiExceptionDispatch+0xc2
fffff880`08b3b920 fffff800`02897565 : 00000000`00000000 fffff800`028acffc 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`08b3bab0 fffff800`028acffc : 00000000`00000000 00000000`00000000 fffff700`01080000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`08b3bac0 fffff800`0289d76e : 00000000`00000001 00000000`0ad6c000 00000000`034ee801 00000000`00083000 : nt!MmAccessFault+0x9dc
fffff880`08b3bc20 00000000`771e2373 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0464a568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771e2373


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02897565 498b08          mov     rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x1E_c0000005_nt!ExpInterlockedPopEntrySListFault16+0

Followup: MachineOwner

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff8a0085ca001
Arg3: 0000000000003dca
Arg4: fffff781c0000000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000293a767 to fffff800028e3640

STACK_TEXT:  
fffff880`09bfc368 fffff800`0293a767 : 00000000`0000001a 00000000`00041284 fffff8a0`085ca001 00000000`00003dca : nt!KeBugCheckEx
fffff880`09bfc370 fffff800`028d4309 : dca00001`00c89963 ffffffff`ffffffff 00000000`00000000 005398be`00404163 : nt! ?? ::FNODOBFM::`string'+0x4ac3
fffff880`09bfc3b0 fffff800`028d38b1 : fffff8a0`00000000 00000000`00000006 fffff6fb`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x179
fffff880`09bfc510 fffff800`02a0b5b1 : 80d2a76c`e86da92e d5f1a3e5`50e49442 3d9e5699`31efb8d2 00000000`000085b0 : nt!MiFreePagedPoolPages+0x12d
fffff880`09bfc660 fffff800`02a0f557 : 00000000`00000000 fffff880`09bfc830 fffff880`09bfc7b0 00000000`00000001 : nt!MiFreePoolPages+0x2b1
fffff880`09bfc770 fffff880`0116c18f : fffff8a0`085b0000 fffff880`09bfc844 00000000`6365734b fffffa80`00000000 : nt!ExFreePoolWithTag+0x7c7
fffff880`09bfc820 00fff880`0116c3ed : fffffa80`050dfc90 fffff800`028eb9f3 fffffa80`20206f49 00000a21`91e99e74 : cng!GatherRandomKey+0x52f
fffff880`09bfcbe0 fffffa80`050dfc90 : fffff800`028eb9f3 fffffa80`20206f49 00000a21`91e99e74 00000a22`00000082 : 0xfff880`0116c3ed
fffff880`09bfcbe8 fffff800`028eb9f3 : fffffa80`20206f49 00000a21`91e99e74 00000a22`00000082 00000a21`91e99e74 : 0xfffffa80`050dfc90
fffff880`09bfcbf0 fffff800`028eda21 : fffff800`02a80600 fffff800`02bd9f01 fffffa80`04970000 fffff800`00000000 : nt!KeRemoveQueueEx+0x323
fffff880`09bfccb0 fffff800`02b80cce : fffff880`05505690 fffffa80`04970040 00000000`00000080 fffffa80`042729e0 : nt!ExpWorkerThread+0x111
fffff880`09bfcd40 fffff800`028d4fe6 : fffff800`02a55e80 fffffa80`04970040 fffff800`02a63cc0 fffff880`0124ccb0 : nt!PspSystemThreadStartup+0x5a
fffff880`09bfcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cng!GatherRandomKey+52f
fffff880`0116c18f 488bbc2488030000 mov     rdi,qword ptr [rsp+388h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  cng!GatherRandomKey+52f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cng

IMAGE_NAME:  cng.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79e2d

FAILURE_BUCKET_ID:  X64_0x1a_41284_cng!GatherRandomKey+52f

BUCKET_ID:  X64_0x1a_41284_cng!GatherRandomKey+52f

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

Many more that won't save because my comp hard locks while saving the BSoD.

Tried reinstalling, no luck - think I'm losing my head.

Cheers

EDIT: And another

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff800028d5565, Address of the instruction which caused the bugcheck
Arg3: fffff88008824d20, 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!ExpInterlockedPopEntrySListFault16+0
fffff800`028d5565 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88008824d20 -- (.cxr 0xfffff88008824d20)
rax=0000001729ab0000 rbx=fffffa800484c220 rcx=fffff80002a509a0
rdx=ff00000000000001 rsi=0000000000000008 rdi=0000000000000000
rip=fffff800028d5565 rsp=fffff88008825700 rbp=fffff80002a509a0
 r8=ff00000000000000  r9=fffff8000285d000 r10=fffff80002a509a0
r11=0000fffffffff000 r12=fffff80002a646c0 r13=0000000000000000
r14=0000000000000002 r15=0000000073496350
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`028d5565 498b08          mov     rcx,qword ptr [r8] ds:002b:ff000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800028d5565

STACK_TEXT:  
fffff880`08825700 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16


FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`028d5565 498b08          mov     rcx,qword ptr [r8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

STACK_COMMAND:  .cxr 0xfffff88008824d20 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

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

LiamJ · 28 Mar 2011 at 21:18

Start with a proper CMOS reset, to restore everything to stock settings. This should point to whether the issue is software or hardware related. If you still get errors, try re-installing Windows. After that, it's probably faulty hardware, although if stress tests are fine, it may be a HDD issue or something.

When did the BSODs start?

spleenharvester · 28 Mar 2011 at 21:24

Already tried mate. Messed around with no ends of settings.

When I reinstalled windows, I was completely BSoD free for about 2 weeks before the problem started up again. If it's a hardware problem, it's a bloody obscure one

Not sure when it started, was about 3 days ago I think, on the last install it was about a week after my new board which is around mid feb.

HDD was actually my next port of call, but I can't download the Samsung Diagnostics program, or get it running eitherway.

tntcoder · 28 Mar 2011 at 21:46

Are you running any weird drivers? It looks like heap corruption in the kernel but the fact that it's coming from variable places (nt and cng modules) is bad.

I would say it's either:

a) Memory fubared - try running on just 1 stick for a while
b) HDD fubared messing with memory paging - try another one.
c) Bad overclock - turn it off for diagnostics
d) Bad driver corrupting the kernel - Format again and just run a clean system for a while and install stuff bit by bit till it goes bad.
e) Malware - least likely - run malware bytes
f) Random piece of hardware failing - buy new PC bits one by one

No easy solution im afraid

spleenharvester · 28 Mar 2011 at 21:52

tntcoder said:
Are you running any weird drivers? It looks like heap corruption in the kernel but the fact that it's coming from variable places (nt and cng modules) is bad.

I would say it's either:

a) Memory fubared - try running on just 1 stick for a while
b) HDD fubared messing with memory paging - try another one.
c) Bad overclock - turn it off for diagnostics
d) Bad driver corrupting the kernel - Format again and just run a clean system for a while and install stuff bit by bit till it goes bad.
e) Malware - least likely - run malware bytes
f) Random piece of hardware failing - buy new PC bits one by one

No easy solution im afraid

a) will be my next port of call. Already swapped slots around, no dice.
b) is what I intend to try next
c) already tried
d) my guess would be the sound drivers if anything, that creative ****e is so dodgy under windows 7. Problem is, when I reformatted, it took three weeks for this specific incarnation of BSoD to pop up :confused:

e) already tried
f) my guess would be motherboard (I had two budget ones have the BIOS/VRM smoke on me, bought this one B-Grade and the BSoDs started not long after, screwed if it's the board

This could take a while eitherway.

Cheers

spleenharvester · 28 Mar 2011 at 21:55

Another thing of note is I can kind of get the system unstable sometimes - Leave facebook and youtube on in the background while playing WMP and with steam open. Sound goes a bit skippy occasionally and eventually it hangs with 0x1E.

LiamJ · 28 Mar 2011 at 22:27

Could be a sound issue for sure. Uninstall the card, boot to safe mode, then run driver sweeper.

Philtor · 29 Mar 2011 at 10:15

If you suspect this may be software related then who crashed might be worth a look.

spleenharvester · 29 Mar 2011 at 17:35

Used to use that, but WinDbg is more detailed.

Also, problem just got more complicated... left Memtest86+ on overnight, 11 passes - no errors. Boot back into windows and... well... I couldn't. It'd be about 10 seconds before it got the BSoD of whatever it felt like bugchecking at the time. It wasn't like this before.

Tried removing CPU overclock, no luck. Remove RAM overclock (so stock settings basically), much more stable but still fails under IBT testing.

Then I kept getting Nvidia driver hangs shortly followed by a BSoD, always either

0x00000019_BAD_POOL_HEADER

or

0x00000024_NTFS.sys (which I know isn't a good sign).

After that it wouldn't POST, after much screwing about I got it going again, restored default settings and all is fine so far, but touch any settings

The question is, WTF is happening? One odd thing I know, this morning my brother's graphics card was completely spectacularly fubared, might have been a surge?

Cheers

me227 · 29 Mar 2011 at 20:20

Sounds quite similar to my problem. I'll get a random BSOD or just a restart. Sometimes I can turn the pc back on fine and sometimes it'll not POST.

I tried diff HDD, PSU and one stick of RAM at a time. Still get the problem. Reinstalled windows and I was fine for about 3 days. I've just ordered a motherboard now to see if that will fix it.

A very annoying problem!

spleenharvester · 29 Mar 2011 at 21:59

So irritating isn't it

Disabled OnChip SATAAAAAAA, onboard audio, onboard 1394 and Xpress gate, problems started again. Will troubleshoot further when I can be bothered.

Molegrips6 · 29 Mar 2011 at 22:28

BSOD

Hi spleenharvester,

Cool handle by the way lol!!! have you done any tests to see if the HDD has any bad sectors? windows may be trying to read or write to the disk and getting corrupt data due that, or maybe even corrupting the boot sector / mbr, my guess is it it is either HDD related or memory due to the inconsistencies, Best of luck tracking it down anyway,

Regards

Mole

spleenharvester · 30 Mar 2011 at 00:23

Hey,

Eventually found my problem, ASUS Anti Surge of all things!

enabled stuff one by one and when I got to that it did the weird no-POST behaviour. All seems to be fine now.

Until next time

Cheers all

spleenharvester · 31 Mar 2011 at 16:25

And so it continues.

It worked brilliantly for a bit, then I thought hell, might as well put overclocks back on. That went fine. Came to it this morning, try to boot into windows... complete hard-lock. No BSoD, nothing, just a hard lock. Remove the overclock, and we're back to square one again -.-

Always 1E which can apparently be VCore, is it possible my chip has *already* degraded?

Cheers

div0 · 31 Mar 2011 at 16:31

So have you ever left it long enough to establish if your PC works flawlessly when running at stock?

If so, then it seems clear that your overclock is causing the problem.

spleenharvester · 31 Mar 2011 at 16:38

That's the problem, I did, then I put the OC back on and it messed up. Now it's unstable on stock again.

Pic related:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\033111-24398-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:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
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 Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02ca1e90
Debug session time: Thu Mar 31 16:28:26.923 2011 (UTC + 1:00)
System Uptime: 0 days 0:28:22.499
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

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

Probably caused by : Unknown_Image ( Unknown_Module_fffffa80`08438660>+37bc7a63 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
Unknown_Module_00000000`00000000>+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ae5f09 to fffff880014037f2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`02ae5f09 : 00000000`0029b957 fffffa80`05d04538 fffff800`02c5ccc0 00000000`00000001 : 0xfffff880`014037f2
fffff800`00b9cca0 00000000`0029b957 : fffffa80`05d04538 fffff800`02c5ccc0 00000000`00000001 fffff800`02c4ee80 : 0xfffff800`02ae5f09
fffff800`00b9cca8 fffffa80`05d04538 : fffff800`02c5ccc0 00000000`00000001 fffff800`02c4ee80 fffff800`02ae7bd7 : <Unloaded_Unknown_Module_00000000`00000100>+0x29b857
fffff800`00b9ccb0 fffff800`02c5ccc0 : 00000000`00000001 fffff800`02c4ee80 fffff800`02ae7bd7 00000001`158cb215 : 0xfffffa80`05d04538
fffff800`00b9ccb8 00000000`00000001 : fffff800`02c4ee80 fffff800`02ae7bd7 00000001`158cb215 00000001`158cb20f : 0xfffff800`02c5ccc0
fffff800`00b9ccc0 fffff800`02c4ee80 : fffff800`02ae7bd7 00000001`158cb215 00000001`158cb20f 00000001`158cb215 : <Unloaded_Unknown_Module_00000000`00000000>+0x1
fffff800`00b9ccc8 fffff800`02ae7bd7 : 00000001`158cb215 00000001`158cb20f 00000001`158cb215 00000000`0000004d : 0xfffff800`02c4ee80
fffff800`00b9ccd0 00000001`158cb215 : 00000001`158cb20f 00000001`158cb215 00000000`0000004d fffffa80`05d044a0 : 0xfffff800`02ae7bd7
fffff800`00b9ccd8 00000001`158cb20f : 00000001`158cb215 00000000`0000004d fffffa80`05d044a0 400000c2`400000c1 : 0x1`158cb215
fffff800`00b9cce0 00000001`158cb215 : 00000000`0000004d fffffa80`05d044a0 400000c2`400000c1 fffffa80`400000c3 : 0x1`158cb20f
fffff800`00b9cce8 00000000`0000004d : fffffa80`05d044a0 400000c2`400000c1 fffffa80`400000c3 00000000`def227ef : 0x1`158cb215
fffff800`00b9ccf0 fffffa80`05d044a0 : 400000c2`400000c1 fffffa80`400000c3 00000000`def227ef fffff800`00b96080 : <Unloaded_Unknown_Module_00000000`00000000>+0x4d
fffff800`00b9ccf8 400000c2`400000c1 : fffffa80`400000c3 00000000`def227ef fffff800`00b96080 fffffa80`042729e0 : 0xfffffa80`05d044a0
fffff800`00b9cd00 fffffa80`400000c3 : 00000000`def227ef fffff800`00b96080 fffffa80`042729e0 00000000`00000000 : 0x400000c2`400000c1
fffff800`00b9cd08 00000000`def227ef : fffff800`00b96080 fffffa80`042729e0 00000000`00000000 00000456`01b13f3f : <Unloaded_Unknown_Module_fffffa80`08438660>+0x37bc7a63
fffff800`00b9cd10 fffff800`00b96080 : fffffa80`042729e0 00000000`00000000 00000456`01b13f3f 00000456`01b19235 : <Unloaded_Unknown_Module_00000000`00000100>+0xdef226ef
fffff800`00b9cd18 fffffa80`042729e0 : 00000000`00000000 00000456`01b13f3f 00000456`01b19235 fffff800`02adf2a4 : 0xfffff800`00b96080
fffff800`00b9cd20 00000000`00000000 : 00000456`01b13f3f 00000456`01b19235 fffff800`02adf2a4 fffff800`00b96080 : 0xfffffa80`042729e0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Unknown_Module_fffffa80`08438660>+37bc7a63
fffffa80`400000c3 ??              ???

SYMBOL_STACK_INDEX:  e

SYMBOL_NAME:  Unknown_Module_fffffa80`08438660>+37bc7a63

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

Even stranger, it then goes on to blame USBPORT.sys after it failed IBT:

Code:

Loading Dump File [C:\Windows\Minidump\033111-16707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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 Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02ca5e90
Debug session time: Thu Mar 31 15:58:45.890 2011 (UTC + 1:00)
System Uptime: 0 days 0:08:44.466
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6339323862623035
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  linpack64.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b0ab8 -- (.exr 0xfffff880009b0ab8)
ExceptionAddress: fffff80002a1b76c (hal!HalPutScatterGatherList+0x000000000000001c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009b0b60 -- (.trap 0xfffff880009b0b60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00fffa80049ab730 rbx=0000000000000000 rcx=fffffa80060feea0
rdx=00fffa80049ab730 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a1b76c rsp=fffff880009b0cf0 rbp=fffffa8004a8c390
 r8=0000000000000000  r9=0000000000000002 r10=00000000ffffffff
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
hal!HalPutScatterGatherList+0x1c:
fffff800`02a1b76c 488b5a08        mov     rbx,qword ptr [rdx+8] ds:0013:00fffa80`049ab738=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad7ffe to fffff80002ae0610

STACK_TEXT:  
fffff880`009afb98 fffff800`02ad7ffe : fffffa80`05dbe010 fffffa80`059691a0 fffff880`009b0310 fffff800`02b0c2a0 : nt!KeBugCheck
fffff880`009afba0 fffff800`02b0bf6d : fffff800`02ce7a10 fffff800`02c23c78 fffff800`02a60000 fffff880`009b0ab8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009afbd0 fffff800`02b0ad45 : fffff800`02c27028 fffff880`009afc48 fffff880`009b0ab8 fffff800`02a60000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009afc00 fffff800`02b1bdc1 : fffff880`009b0ab8 fffff880`009b0310 fffff880`00000000 fffffa80`04a8c010 : nt!RtlDispatchException+0x415
fffff880`009b02e0 fffff800`02adfcc2 : fffff880`009b0ab8 fffffa80`057d21a0 fffff880`009b0b60 fffffa80`057d2050 : nt!KiDispatchException+0x135
fffff880`009b0980 fffff800`02ade5ca : fffffa80`057d21a0 fffffa80`057d2101 fffffa80`07c85b60 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`009b0b60 fffff800`02a1b76c : fffffa80`057d21a0 00000000`000003d8 00000000`00000000 fffffa80`07bba8f0 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0cf0 fffff880`13013023 : fffffa80`057d21a0 fffffa80`04a8c390 fffffa80`057d2050 fffffa80`057d21a0 : hal!HalPutScatterGatherList+0x1c
fffff880`009b0d50 fffff880`13013ab7 : fffffa80`04a8c002 fffffa80`07c238e0 00000000`ffffffff fffffa80`057d2ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`009b0e30 fffff880`1301164f : fffffa80`057d2ea8 fffffa80`057d21a0 fffffa80`057d3040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`009b0e90 fffff880`13002f89 : fffffa80`057d2050 00000000`00000000 fffffa80`057d2e02 fffffa80`057d2ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`009b0ed0 fffff800`02aebb1c : fffff880`02fd3180 fffffa80`057d2ea8 fffffa80`057d2ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`009b0f00 fffff800`02ae3165 : 00000000`00000000 fffffa80`04d27b60 00000000`00000000 fffff880`13002db0 : nt!KiRetireDpcList+0x1bc
fffff880`009b0fb0 fffff800`02ae2f7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`08ccdbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`13013023 4533c0          xor     r8d,r8d

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID:  X64_0x1E_0_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

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

EDIT: Advancement. Stripped system down to bare essentials. What I've tried;

Stick 1 in slot 1 on its own - no post after 3 attempts
Stick 2 in slot 2 on its own - POSTed perfectly
Then put stick 1 in slot 1 again - also POSTed perfectly again :confused:

Removed WiFi card - made system much, much more stable, but always crashes after the message saying it successfully passed IBT with either TDR_DRIVER_TIMEOUT or 0x1E?

If it's the board, FML. It has an Asus RMA sticker on it and was B-grade, can't help but wonder if OcUK never tested it properly before putting it up...

me227 · 31 Mar 2011 at 19:24

I've just got my new motherboard, will probably fit it over the weekend and will let you know if my problem disappears.

spleenharvester · 31 Mar 2011 at 20:25

Okay, cheers dude, and good luck

Think I *may* have fixed it, completely stripped the system down, cleaned all contacts to everything, blew dust out of every last slot (even the BIOS chip slot), system currently seems stable. It's only a matter of time before it goes again I bet, this has happened a fair few times :|

If my board's had it I'm selling the lot and getting a netbook. Doesn't help that my BSoDs uncover near to nothing (quote from another forum):

Getting:
0x000001E KMODE_EXCEPTION_NOT_HANDLED (about 80% of the time)
0x0000124 WHEA_UNCORRECTABLE_ERROR
0x0000116 VIDEO_TDR_ERROR
0x0000050 PAGE_FAULT_IN_NONPAGED_AREA
0x1000009 BAD_POOL_HEADER
0x0000024 NTFS_FILE_SYSTEM (only twice)
0x000000A DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000004E PFN_LIST_CORRUPT (this happened after I reset the BIOS, could not boot, took 5 attempts to get in)
0x000001A MEMORY_MANAGEMENT

Drivers blamed include csrss.exe, PxHlpA64.sys (removed), nvklkkdm.sys (or whatever it is), win32k.sys, USBPORT.SYS (that was an odd one), and more.

Fillado · 1 Apr 2011 at 15:38

I'm currently joining this club

AMD Phenom II X2 555 (depending unlocked to 4 cores) on a MSI 870A-G54 board with a single Corsair XM3 4GB 1333MHz RAM stick and a Radeon HD 3500 Pro graphics card. Graphics card was in a previous build so that isn't (shouldn't be!) a problem.

New build and totally random BSODs. Happened while just downloading one of the times. At first I thought it was me unlocking the cores but it happened when it was a dual core too.

Prime95 (for an hour) - stable
BOINC overnight with 4 cores + GPU going at full whack - stable
Games - stable (except for just now)

It just crashed now playing MW2 and the only thing I changed (I was playing it earlier) was unplugging a rear PCI exhaust blower. The exhaust blower was also on while BOINCing over last night. It hasn't really been on in the past since it's slightly louder than everything else in there.

Current theory:

My Motherboard.

The graphics card stretches the length of the motherboard. So when in a computer it both produces a lot of heat and keeps it trapped underneath it. I think due to how long it is it's making the southbridge overheat. The rear PCI exhaust fan obviously gets rid of a lot of the heat down there and stops it happening.

I'm currently testing with an 80cm fan blowing onto the southbridge. Propped into position with the second PCI-E power cable

spleenharvester · 1 Apr 2011 at 16:03

What codes you getting mate? Might be able to help with this, having spent my nights for the last 3 weeks trying to sort mine

Mine was like that to begin with but eventually mine became unstable in IBT completely. Not sure why.