Need help with new rig, Windows 7 64 crash/lockup/BSOD

SamuelL421 · 31 Dec 2009

Hi everyone, as with the others posting to this forum, I'm here to ask you to share some knowledge with me. I'm in need of help after building a new pc recently. in the paragraph below I've outlined what exactly is happening and when I've seen it crash/lockup. I've also attached the .dmp below from my only BSOD I've encountered (also have a .sysdata file from the BSOD if its needed). Thank you very, very much in advance for any help you can give me.

Just before christmas I built new pc using Windows 7 Pro 64bit (the parts used are listed below). I have been experiencing issues that seem very random (frequent crashing or complete system lock required a hard shutdown/restart). For the past week I have had these issues, sometimes alot (repeated lock ups at the log on screen), and sometimes none at all (playing dx10 game, full settings for several hours, leaving pc to sleep mode, logged on the next morning and everything was fine).
Situations causing complete lock up: Windows 7 logon screen, firefox - youtube.com, IE 64 bit - msn.com, Steam (gaming app), testing DVD burn through windows, Everest, various games
Situations causing crash/reboot: IE 64 bit, various games
BSOD: Crysis 32 bit (flashed only for 2-3 seconds, too fast to record what it said)
NOTE: all programs/games/drivers current or patched to latest ver.

Currently, I'm thinking the issue could be related to the ram or the voltage settings I'm using. This pc is using a non-OC'd i7 920 on a Gigabyte EX58-UD5 with 6gb OCZ gold 1600. Thanks again

zigzag3143 · 31 Dec 2009

SamuelL421 said:

Hi everyone, as with the others posting to this forum, I'm here to ask you to share some knowledge with me. I'm in need of help after building a new pc recently. in the paragraph below I've outlined what exactly is happening and when I've seen it crash/lockup. I've also attached the .dmp below from my only BSOD I've encountered (also have a .sysdata file from the BSOD if its needed). Thank you very, very much in advance for any help you can give me.

Just before christmas I built new pc using Windows 7 Pro 64bit (the parts used are listed below). I have been experiencing issues that seem very random (frequent crashing or complete system lock required a hard shutdown/restart). For the past week I have had these issues, sometimes alot (repeated lock ups at the log on screen), and sometimes none at all (playing dx10 game, full settings for several hours, leaving pc to sleep mode, logged on the next morning and everything was fine).
Situations causing complete lock up: Windows 7 logon screen, firefox - youtube.com, IE 64 bit - msn.com, Steam (gaming app), testing DVD burn through windows, Everest, various games
Situations causing crash/reboot: IE 64 bit, various games
BSOD: Crysis 32 bit (flashed only for 2-3 seconds, too fast to record what it said)
NOTE: all programs/games/drivers current or patched to latest ver.

Currently, I'm thinking the issue could be related to the ram or the voltage settings I'm using. This pc is using a non-OC'd i7 920 on a Gigabyte EX58-UD5 with 6gb OCZ gold 1600. Thanks again

Hi and welcome

As you thought it is memory corruption

download memtestx86 and run it for 5 passes to confirm if memory or heat

Ken J+

Code:

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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Wed Dec 30 22:34:32.192 2009 (GMT-5)
System Uptime: 0 days 1:28:43.269
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {f48001f, d, 1, fffff80002c93c89}

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

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: 000000000f48001f, memory referenced
Arg2: 000000000000000d, 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: fffff80002c93c89, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0
 000000000f48001f 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KeAccumulateTicks+229
fffff800`02c93c89 188f1e00480f    sbb     byte ptr [rdi+0F48001Eh],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c8a0 -- (.trap 0xfffff80000b9c8a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000008b49c9b6 rbx=0000000000000000 rcx=0000000000000005
rdx=000000000002123d rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c93c89 rsp=fffff80000b9ca30 rbp=0000000000000001
 r8=0000000000000005  r9=0000000000000000 r10=fffff80002c1b000
r11=fffff80000b9cb08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeAccumulateTicks+0x229:
fffff800`02c93c89 188f1e00480f    sbb     byte ptr [rdi+0F48001Eh],cl ds:0001:00000000`0f48001e=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8c469 to fffff80002c8cf00

STACK_TEXT:  
fffff800`00b9c758 fffff800`02c8c469 : 00000000`0000000a 00000000`0f48001f 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c760 fffff800`02c8b0e0 : 00000000`00000000 fffff800`02e05e80 00000000`00002710 fffff800`00b9c960 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c8a0 fffff800`02c93c89 : 00000000`00000001 00001f80`00000200 00000003`00010003 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9ca30 fffff800`02c955f7 : 00000000`00000000 fffff800`02e05e80 00000000`00002710 00000000`00000000 : nt!KeAccumulateTicks+0x229
fffff800`00b9cac0 fffff800`03202895 : fffff800`03227460 fffff800`00b9cc70 fffff800`03227460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9cbc0 fffff800`02c893f3 : fffff800`02e05e80 fffff800`00b9cc70 fffffa80`064cab60 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9cbf0 fffff800`02c956d2 : fffff800`02e05e80 fffff800`00000002 00000000`00000002 fffff880`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002c93c82 - nt!KeAccumulateTicks+222
    [ 0f:0d ]
1 error : !nt (fffff80002c93c82)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

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

SamuelL421 · 31 Dec 2009

Thanks for quick help Ken.

Using a good copy of memtest x86 I got a complete lock up several times about 7 seconds into the test. What might be the primary reason for this? Is it more likely a bad stick of ram or bad voltage settings?

- I'm currently using The exact settings specified by OCZ for the ram, 8-8-8-24 1600mhz (w/ 12x multiplier) The ram is specified "1.65v", which isn't an option in the UD5 mobo, so it's set to 1.64v showing up as 1.63v in Everest. Could a .02 drop in voltage be killing my system?