BSOD on Windows 7 x64

Hey guys,

Recently, I have been having a very weird problem with my computer. This is a pretty new build. It was working nicely for about a month but about couple weeks back, I started having some strange issues.

Windows keeps giving me BSOD after shutting down the computer overnight. Note, this only happens if i shutdown the PC overnight (aka more than say 5-6 hrs). I have tested turning the PC back on after like 3 hrs, and everything worked. Its only after about 6hrs, the BSOD problem arises.

I have tried complete reformat/reinstallation of windows 7 (x64 ultimate) about 2-3 times, but same thing happens.

The BSOD error messages aren't consistent. Sometimes its memory_dump sometimes random alphanumeric letters.

Now past few days, I have found that resetting the RAM (removing and putting it back in) has solved the problem. But again once i shutdown the computer for more than 6hrs the problem comes back.

So thats the description of the problem. I have attached the windows dump files...there are 3 .dmp files zipped in the attachment.

Oh and if I dont turn off the PC for more than 6hrs, it keeps working normally...

Please help me find out the problem. Thanks

CrashOverride said:

Hey guys,

Recently, I have been having a very weird problem with my computer. This is a pretty new build. It was working nicely for about a month but about couple weeks back, I started having some strange issues.

Windows keeps giving me BSOD after shutting down the computer overnight. Note, this only happens if i shutdown the PC overnight (aka more than say 5-6 hrs). I have tested turning the PC back on after like 3 hrs, and everything worked. Its only after about 6hrs, the BSOD problem arises.

I have tried complete reformat/reinstallation of windows 7 (x64 ultimate) about 2-3 times, but same thing happens.

The BSOD error messages aren't consistent. Sometimes its memory_dump sometimes random alphanumeric letters.

Now past few days, I have found that resetting the RAM (removing and putting it back in) has solved the problem. But again once i shutdown the computer for more than 6hrs the problem comes back.

So thats the description of the problem. I have attached the windows dump files...there are 3 .dmp files zipped in the attachment.

Oh and if I dont turn off the PC for more than 6hrs, it keeps working normally...

Please help me find out the problem. Thanks

Hi and welcome

Well you are three for three. All three dmps point to memory corruption. There may be hardware that is causing it to corrupt but to find it you have to fix the memory first.

I would
Download memtestx86 and run it overnight.

Run a system file check type cmd in search>right click and run as admin
>sfc /scannow

If you are overclocking stop

Hope this helps and of course if you have more upload them


Ken J++



Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\010109-16395-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50
Debug session time: Sun Dec 6 17:16:20.745 2009 (GMT-5)
System Uptime: 0 days 0:00:43.118
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff3000a1f5a00, 1, fffff8800713f374, 7}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

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

1: 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: fffff3000a1f5a00, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800713f374, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e0
fffff3000a1f5a00

FAULTING_IP:
bowser!BowserProcessMasterAnnouncement+214
fffff880`0713f374 884c3440 mov byte ptr [rsp+rsi+40h],cl

MM_INTERNAL_CODE: 7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff88002f709f0 -- (.trap 0xfffff88002f709f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88002f70bc8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800713f374 rsp=fffff88002f70b80 rbp=fffff80002e285f8
r8=0000000000000001 r9=0000000000000000 r10=000000000000000e
r11=fffff8a001985a40 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe nc
bowser!BowserProcessMasterAnnouncement+0x214:
fffff880`0713f374 884c3440 mov byte ptr [rsp+rsi+40h],cl ss:0018:fffff880`02f70bc0=00
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d02b19 to fffff80002c84f00

STACK_TEXT:
fffff880`02f70888 fffff800`02d02b19 : 00000000`00000050 fffff300`0a1f5a00 00000000`00000001 fffff880`02f709f0 : nt!KeBugCheckEx
fffff880`02f70890 fffff800`02c82fee : 00000000`00000001 fffffa80`06e05c10 fffff880`02f70d00 fffffa80`039fd680 : nt! ?? ::FNODOBFM::`string'+0x40edb
fffff880`02f709f0 fffff880`0713f374 : fffffa80`06e05c10 fffffa80`07284e40 fffff800`02e28500 fffffa80`00000010 : nt!KiPageFault+0x16e
fffff880`02f70b80 fffff880`0712e41e : fffffa80`039fd680 fffffa80`07284e40 fffff880`071325d0 fffffa80`06acac50 : bowser!BowserProcessMasterAnnouncement+0x214
fffff880`02f70c50 fffff800`02f7e541 : fffffa80`06acac50 fffffa80`04df5b20 fffffa80`04df5b20 fffffa80`039fd680 : bowser!BowserDelayedThreadWorker+0x42
fffff880`02f70c80 fffff800`02c92161 : fffff800`02e28500 fffff800`02f7e504 fffffa80`039fd680 00000000`00000000 : nt!IopProcessWorkItem+0x3d
fffff880`02f70cb0 fffff800`02f28166 : 000004f4`00000000 fffffa80`039fd680 00000000`00000080 fffffa80`039739e0 : nt!ExpWorkerThread+0x111
fffff880`02f70d40 fffff800`02c63486 : fffff880`02d63180 fffffa80`039fd680 fffff880`02d6df80 000004f4`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f70d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !bowser
7 errors : !bowser (fffff8800713f2f6-fffff8800713ff76)
fffff8800713f2f0 48 8b 48 38 48 83 *d1 10 48 89 4c 24 30 48 8b 44 H.H8H...H.L$0H.D
...
fffff8800713f330 5c 01 00 00 74 0a *55 8a e6 44 88 74 24 40 eb 27 \...t.U..D.t$@.'
...
fffff8800713f370 41 0f 42 ce 88 4c *34 40 8b 46 2c 25 00 00 ff ff A.B..L4@.F,%....
...
fffff8800713fab0 83 ec 48 48 8b ea *58 8b 4d 40 33 ff 48 3b cf 74 ..HH..X.M@3.H;.t
...
fffff8800713fef0 00 00 00 ff 15 67 *11 ff ff eb 04 48 8b 5d 28 48 .....g.....H.](H
...
fffff8800713ff30 28 48 8b ea 48 8b *5d 28 33 ff 48 3b cf 74 05 e8 (H..H.](3.H;.t..
...
fffff8800713ff70 55 57 48 83 ec 28 *58 8b ea 48 8b 4d 40 33 ff 48 UWH..(X..H.M@3.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
---------

0x50 errors can be tied into antivirus. Follow Ken's excellent advice and also completely uninstall any antivirus software, to test. Any antivirus that starts with Windows or Spyware Doctor too. Uninstall the Ask Toolbar if you have that.

I'd get these drivers updated too:

Code:

emOEM64  emOEM64.sys  Fri Aug 31 17:13:47 2007
emBDA64  emBDA64.sys  Fri Aug 31 20:34:08 2007

New drivers and bios for your board in the link below.

To obtain more precise memory setting information for your board try asking a question at the GSkill forum.
DDR3 - GSKILL TECH FORUM

GIGABYTE - Support&Download - Motherboard - Driver - GA-MA770T-UD3P (rev. 1.0)