BSOD while gaming, mulitple error codes.

[Salamandrex]

Crashed again for the first time in a month nothing new installed. It ran fine after CHKDSK for a month so I guess I'll try that again. Was looking for anymore ideas as to the cause.

 

[Salamandrex]

Another crash happened I was able to play games for about 3 hours today then when browsing the internet got this BSOD.
Any help would be appreciated

 

[Salamandrex]

Crashed during the SFC start up and once before the SFC. One of the .dmp files didn't save. Ran Seatools and tests came back clean which I believe eliminates my hard drive. Any info from any of these .dmp's pointing me in the right direction or more tests would be appreciated.

 

[Arc]

I guess you need to check your RAM modules.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8000100caf0, 2, 1, fffff80002ea2066}

Probably caused by : memory_corruption

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff8000100caf0, 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: fffff80002ea2066, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
GetUlongFromAddress: unable to read from fffff800030c61c0
 fffff8000100caf0 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+c6
fffff800`02ea2066 4c894008        mov     qword ptr [rax+8],r8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80004402FB0

LAST_CONTROL_TRANSFER:  from fffff80002e96569 to fffff80002e96fc0

STACK_TEXT:  
fffff800`043fc228 fffff800`02e96569 : 00000000`0000000a fffff800`0100caf0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`043fc230 fffff800`00e951e0 : fffffa80`086c5780 fffffa80`086c5780 fffff880`03088180 fffffa80`079c7860 : nt!KiBugCheckDispatch+0x69
fffff800`043fc370 fffffa80`086c5780 : fffffa80`086c5780 fffff880`03088180 fffffa80`079c7860 fffff800`043fc390 : 0xfffff800`00e951e0
fffff800`043fc378 fffffa80`086c5780 : fffff880`03088180 fffffa80`079c7860 fffff800`043fc390 00001f80`01010000 : 0xfffffa80`086c5780
fffff800`043fc380 fffff880`03088180 : fffffa80`079c7860 fffff800`043fc390 00001f80`01010000 fffff800`0100cae8 : 0xfffffa80`086c5780
fffff800`043fc388 fffffa80`079c7860 : fffff800`043fc390 00001f80`01010000 fffff800`0100cae8 00000000`0000dace : 0xfffff880`03088180
fffff800`043fc390 fffff800`043fc390 : 00001f80`01010000 fffff800`0100cae8 00000000`0000dace fffffa80`09a32ee8 : 0xfffffa80`079c7860
fffff800`043fc398 00001f80`01010000 : fffff800`0100cae8 00000000`0000dace fffffa80`09a32ee8 fffffa80`079c7880 : 0xfffff800`043fc390
fffff800`043fc3a0 fffff800`0100cae8 : 00000000`0000dace fffffa80`09a32ee8 fffffa80`079c7880 00000000`00000043 : 0x00001f80`01010000
fffff800`043fc3a8 00000000`0000dace : fffffa80`09a32ee8 fffffa80`079c7880 00000000`00000043 fffff800`03009e80 : 0xfffff800`0100cae8
fffff800`043fc3b0 fffffa80`09a32ee8 : fffffa80`079c7880 00000000`00000043 fffff800`03009e80 00000000`00000000 : 0xdace
fffff800`043fc3b8 fffffa80`079c7880 : 00000000`00000043 fffff800`03009e80 00000000`00000000 fffff880`013e4d7b : 0xfffffa80`09a32ee8
fffff800`043fc3c0 00000000`00000043 : fffff800`03009e80 00000000`00000000 fffff880`013e4d7b 00000000`00000000 : 0xfffffa80`079c7880
fffff800`043fc3c8 fffff800`03009e80 : 00000000`00000000 fffff880`013e4d7b 00000000`00000000 00000000`00000000 : 0x43
fffff800`043fc3d0 00000000`00000000 : fffff880`013e4d7b 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInitialPCR+0x180


STACK_COMMAND:  .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
12 errors : !nt (fffff80002e96293-fffff80002ea2da3)
fffff80002e96290  00  41  0b *89  c4  01  00  00  0f  85  ce  01  00  00  fa  65 .A.............e
...
fffff80002e963a0  00  33  d2  66  0f  ef  c0  66  0f  ef  c9 *64  0f  ef  d2  66 .3.f...f...d...f
...
fffff80002e96480  00  00  45  0f  b6  83  f0  01  00  00  45 *89  8b  c4  01  00 ..E.......E.....
...
fffff80002e96680  8b  19  48 *89  79  08  48  8b  71  10  4c *89  61  18  4c  8b ..H.y.H.q.L.a.L.
...
fffff80002e96770  28  55  10  0f  28  5d  20  0f  28  65  30 *0d  28  6d  40  4c (U..(] .(e0.(m@L
...
fffff80002e96e20  45  80  4c  8b  4d  88  4c  8b  55  90  4c *89  5d  98  48  83 E.L.M.L.U.L.].H.
...
fffff80002ea20f0  24  00  0f  ae  e8  eb  ac  49  8b  cf  48 *29  c8  8b  05  25 $......I..H)...%
...
fffff80002ea23a0  15  73  2d *10  00  65  48  8b  0c  25  20  00  00  00  fe  49 .s-..eH..% ....I
...
fffff80002ea2a20  47  48  0f  be  79  42  44  8b  e2  4c  8b *c1  33  d2  48  8b GH..yBD..L..3.H.
...
fffff80002ea2d00  c1  80  f9 *00  0f  82  de  02  00  00  65  48  8b  0c  25  40 ..........eH..%@
...
fffff80002ea2da0  0d  5b  52 *f5  ff  48  8b  84  c1  40  ea  2a  00  48  8b  88 .[R..H...@.*.H..

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
---------

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, per RAM module per slot.

 

[Salamandrex]

Memtest came back clean after 9 passes. Got a new BSOD today after being fine all day yesterday.

 

[Arc]

It still shows massive memory corruption.
upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[JMV2009]

Use memtest from hcidesign

Use driver verifier (if you didn't already)

 

[Salamandrex]

Here's the MSINFO file hope it clears somethings up

 

[Arc]

There is nothing that can be faked as memory corruption. At least I am not seeing.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Salamandrex]

Had 2 BSOD's before i got driver verifier going today, got it going now thankfully. After the second BSOD however, when I went to turn the computer back on it cycled through the booting up sound made with nothing showing on the monitor for a minute until I manually turned it off again and rebooted.

 

[Arc]

It shows repetitive memory corruption, in both the dumps.

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000e740b, fffff880090a7fc0, 0}

Probably caused by : memory_corruption

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff960000e740b, Address of the instruction which caused the bugcheck
Arg3: fffff880090a7fc0, 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: 
win32k!DoTimer+103
fffff960`000e740b 488910          mov     qword ptr [rax],rdx

CONTEXT:  fffff880090a7fc0 -- (.cxr 0xfffff880090a7fc0)
rax=fffff900c0c53ba8 rbx=fffff900c068f480 rcx=fffff960002f6740
rdx=fffff900c068f438 rsi=0000000000000010 rdi=fffff900c2a073a0
rip=fffff960000e740b rsp=fffff880090a89a0 rbp=fffff880090a8ca0
 r8=0000000000000000  r9=0000000000001002 r10=fffff900c08230b0
r11=fffff900c07041e0 r12=0000000000000001 r13=fffff880090a8b68
r14=00000000000025ff r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!DoTimer+0x103:
fffff960`000e740b 488910          mov     qword ptr [rax],rdx ds:002b:fffff900`c0c53ba8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff960000db9b4 to fffff960000e740b

STACK_TEXT:  
fffff880`090a89a0 fffff960`000db9b4 : fffff900`c2a073a0 fffff880`090a8ca0 00000000`00000000 fffffa80`09dc2b50 : win32k!DoTimer+0x103
fffff880`090a8a00 fffff960`000dbbd5 : 00000000`00000000 fffff800`000025ff 00000000`00000000 fffffa80`ffffffff : win32k!xxxRealInternalGetMessage+0x6c0
fffff880`090a8ae0 fffff960`000d4627 : 00000000`05b4f100 fffffa80`09dc2b50 fffff880`00000000 00000000`00000000 : win32k!xxxInternalGetMessage+0x35
fffff880`090a8b20 fffff800`02e82253 : fffffa80`09dc2b50 00000000`05b4e7e8 fffff880`090a8bc8 00000000`74ea2450 : win32k!NtUserPeekMessage+0x77
fffff880`090a8bb0 00000000`74eefdea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05b4e7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74eefdea


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002e82293 - nt!KiSystemServiceExit+38
    [ 8b:89 ]
1 error : !nt (fffff80002e82293)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff880090a7fc0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

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

Do the memtest again? 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, per RAM module per slot.

Update display driver.

fffff880`03b86068  fffff880`048bffa4Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xb6fa4[/COLOR]
=====================================================
lmvm atikmdag
start             end                 module name
fffff880`04809000 fffff880`0522a000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    [COLOR=Red]Image name: atikmdag.sys
    Timestamp:        Sat Jul 28 07:18:09 2012[/COLOR] (501344D9)
    CheckSum:         009DA146
    ImageSize:        00A21000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

Download Memeter. During gaming, Alt+Tab and see the memory usage. Is it gradually increasing and approaching to 100% ? Let us know. It is the most vital information here.

 

[Vir Gnarus]

Aside from everything Arc has recommended, can you verify (punny) that Driver Verifier is up and running by opening it again and selecting "Display existing settings"? That way we'll be sure if it crashes again DV will be around to provide extra details in the crashdump.

The code corruption Arc has discovered are single bit errors. These are most commonly caused either by RAM, CPU, Mobo or PSU problems. Voltage issues such as from dust inside the case, as well as temperature or voltage instabilities can also cause these single bit flips. Clean the inside of the case properly and also re-seat cards and cables, and verify that your system is running at decent temperatures (Hwinfo with sensors only checked works great).