BSOD often when booting but also during use

[Arc]

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


Loading Dump File [C:\Users\Arch\AppData\Local\Temp\Rar$DI01.087\011213-28579-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff780`ffff0000?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000003`00001f80?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000006?
Symbol search path is: SRV*C:\SymCache*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
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`0309f670
Debug session time: Sat Jan 12 19:24:46.033 2013 (UTC + 5:30)
System Uptime: 0 days 0:01:11.047
Loading Kernel Symbols
....Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
....Missing image name, possible paged-out or corrupt data.
.....................Image path too long, possible 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.
..Image path too long, possible corrupt data.
..Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
........Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
...
..Missing image name, possible paged-out or corrupt data.
..................Image path too long, possible corrupt data.
.........Image path too long, possible corrupt data.
......Image path too long, possible corrupt data.
............Missing image name, possible paged-out or corrupt data.
..............Missing image name, possible paged-out or corrupt data.
..Image path too long, possible corrupt data.
.
...............Missing image name, possible paged-out or corrupt data.
...............Image path too long, possible corrupt data.
...
Loading User Symbols
Loading unloaded module list
......
ERROR: Unable to find system thread 81
ERROR: The thread being debugged has either exited or cannot be accessed
ERROR: Many commands will not work properly
ERROR: Exception 80000003 occurred on unknown thread 81

I need to ask somebody more experienced.

 

[gabeg]

okay. thanks. I appreciate greatly

 

[Vir Gnarus]

The dump is corrupt and incomplete, that's all it's saying. Unfortunately it is worthless and should be discarded. Hopefully a more reliable crashdump will be produced in the future. If this is consistent, there's most likely a hardware failure occurring during dump generation.

 

[gabeg]

Ok...i had a crash this morning...will post the dump later.

 

[gabeg]

Latest Dump

 

[Arc]

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80018b2be4b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ef7d68, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fd100
GetUlongFromAddress: unable to read from fffff800030fd1c0
 fffff80018b2be4b Nonpaged pool

FAULTING_IP: 
nt!RtlLookupFunctionEntry+28
fffff800`02ef7d68 852c03          test    dword ptr [rbx+rax],ebp

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800e1e16b0 -- (.trap 0xfffff8800e1e16b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007ffffff0000 rbx=0000000000000000 rcx=0000000000000290
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031c310a rsp=fffff8800e1e1840 rbp=0000000000000290
 r8=0000000000000290  r9=fffff8800e1e1940 r10=fffffa8007371840
r11=fffff8800e1e1988 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!ObpCaptureObjectCreateInformation+0x8a:
fffff800`031c310a 0fb601          movzx   eax,byte ptr [rcx] ds:00000000`00000290=??
Resetting default scope

EXCEPTION_RECORD:  fffff8800e1e1608 -- (.exr 0xfffff8800e1e1608)
ExceptionAddress: fffff800031c310a (nt!ObpCaptureObjectCreateInformation+0x000000000000008a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000290
Attempt to read from address 0000000000000290

LAST_CONTROL_TRANSFER:  from fffff80002e748e0 to fffff80002ecdfc0

STACK_TEXT:  
fffff880`0e1e03e8 fffff800`02e748e0 : 00000000`00000050 fffff800`18b2be4b 00000000`00000000 fffff880`0e1e0550 : nt!KeBugCheckEx
fffff880`0e1e03f0 fffff800`02ecc0ee : 00000000`00000000 fffff800`18b2be4b 00000000`00000000 fffff800`031c310a : nt! ?? ::FNODOBFM::`string'+0x437f6
fffff880`0e1e0550 fffff800`02ef7d68 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0e1e06e0 fffff800`02ef7580 : fffff880`0e1e0e40 fffff880`0e1e0798 00000000`00000003 fffff880`0e1e0ed0 : nt!RtlLookupFunctionEntry+0x28
fffff880`0e1e0750 fffff800`02f08851 : fffff880`0e1e1608 fffff880`0e1e0e60 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0xd0
fffff880`0e1e0e30 fffff800`02ecd642 : fffff880`0e1e1608 fffffa80`0a9c56b0 fffff880`0e1e16b0 fffffa80`07371840 : nt!KiDispatchException+0x135
fffff880`0e1e14d0 fffff800`02ecc1ba : 00000000`00000000 00000000`00000290 00000000`00000000 fffffa80`0a9c56b0 : nt!KiExceptionDispatch+0xc2
fffff880`0e1e16b0 fffff800`031c310a : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`080e0060 : nt!KiPageFault+0x23a
fffff880`0e1e1840 fffff800`031c53ab : fffffa80`0a9c5610 fffffa80`07371840 00000000`00000000 fffffa80`080e21b0 : nt!ObpCaptureObjectCreateInformation+0x8a
fffff880`0e1e18c0 fffff800`031a5536 : 00000000`00000000 00000000`00d60070 fffffa80`0aec5a01 fffff880`0851f825 : nt!ObOpenObjectByName+0xbb
fffff880`0e1e1990 fffff800`02ecd253 : fffffa80`0ac86770 fffff880`0e1e1ca0 fffffa80`0ac86770 fffffa80`0ac098e0 : nt!NtQueryAttributesFile+0x145
fffff880`0e1e1c20 00000000`774516ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0234fb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774516ea


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
11 errors : !nt (fffff80002ecd760-fffff80002ef7f00)
fffff80002ecd760 *e8  48  cf  0f  ae  55  ac  0f  28  45  f0  0f  28  4d  00  0f .H...U..(E..(M..
...
fffff80002ecd7d0 *c8  01  00  00  48  8d  a9  80  00  00  00  44  0f  20  c0  0a ....H......D. ..
...
fffff80002ecddd0 *44  24  50  48  0f  ba  6c  24  48  00  48  8b  cc  e8  5e  7c D$PH..l$H.H...^|
fffff80002ecdde0 *01  00  4c  8b  a4  24  88  01  00  00  4c  8b  ac  24  90  01 ..L..$....L..$..
...
fffff80002ef7620 *e3  0f  84  7a  ae  f8  ff  3c  eb  0f  84  7e  03  00  00  3c ...z...<...~...<
...
fffff80002ef7d60 *64  15  41  80  78  07  00  0f  85  2c  03  00  00  80  7e  06 d.A.x....,....~.
...
fffff80002ef7d80 *28  4c  89  7c  24  30  45  33  f6  45  0f  20  c7  41  80  ff (L.|$0E3.E. .A..
...
fffff80002ef7db0 *05  00  10  0f  82  a1  9e  f8  ff  40  32  ff  4c  89  64  24 [email protected]$
fffff80002ef7dc0 *60  40  84  ff  0f  85  98  9e  f8  ff  45  33  e4  ff  85  00 `@........E3....
...
fffff80002ef7e30 *c1  f9  48  63  c1  48  8d  3c  40  49  8b  84  fa  88  e4  1e ..Hc.H.<@I......
...
fffff80002ef7f00 *c1  f8  49  63  c0  48  8d  0c  40  8b  04  8f  4c  8d  14  8f [email protected]...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Have you taken these tests earlier time?

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the CPU.
Hardware - Stress Test With Prime95

A search revealed that you are using nForce as the chipset driver, and that is very old, of April 2010. You need to try to update nForce, as it contains not only the storage controller, but also network controller and a lot of other vital drivers.

Go to Drivers - Download NVIDIA Drivers, search for nForce, as per your motherboard's chipset specifications.

And, your Creative Hardware Abstract Layer Driver is extremely old, it is of 2007. You must to update it, from Creative Worldwide Support.

Let us know the results.

 

[gabeg]

I've done all of those things

 

[Arc]

I've done all of those things

You are to be informative. From this statement nothing becomes clear. If you want to continue with the issue, let us know the results and the current situation.

 

[gabeg]

I've done all of those things

You are to be informative. From this statement nothing becomes clear. If you want to continue with the issue, let us know the results and the current situation.

You asked if I had done the things you list previously. I did. The one exception is the creative labs driver, which I just did.

I didn't mean to be terse, just letting you know I had taken those steps.

 

[Arc]

Lol .... ok.
Information are more important. If you let us know what the result you obtained from those tests, it would be easier to infer and proceed further, nothing else.

Form the next time, I will always ask for the results

 

[Vir Gnarus]

I really don't know what to say, these symptoms all reek of hardware failure and the last one is a solid piece of evidence convicting it.

For Prime95, while the article says use Small FFTs, I recommend you set it to Blend next time. Of course, make sure the CPU is properly cooled for the endeavor, as it's gonna be at its hottest for this, and you're going to leave it running Prime95 overnight too.

The hardware that are primarily responsible for this kinda problem are the CPU, RAM, Motherboard and PSU. RAM has been tested, and CPU should be tested thoroughly after this next Prime95, so the only thing after that left behind would be Mobo and PSU. Unfortunately, aside from swapping them out, there are no diagnostic tools that you can use for em.