New
#1
BSOD on cold Boot
I am getting a BSOD almost like clockwork on every cold boot where the computer has been turned off overnight. It NEVER bsod's once booted or if I restart while the computer has already been on. Once it bsod's I simply turn the power point off and back on and it boots fine every single time.
Computer Specs:
Windows 7 Ultimate x64
Gigabyte P55-UD5
Intel i7-860
Gigabyte 6950 2gb
G.Skill Ripjaw F3-12800CL9-2GBRL (4 X 2GB)
G.Skill Falcon 128GB SSD (OS Drive)
2 x Samsung Spinpoint F3 Drives in Raid0 (Data)
Asus Xonar Esence STX Sound Card
Seasonic X Series 750w PSU
Lian Li Case
What I have tried:
- Clean install of Windows
- Run Memtest86+ for 90mins turn off computer for 2 hours and run again, NO errors detected.
- Just got a new Lian Li case so most things have been reseated (except CPU and Memory)
- Video card is also new and it was doing this before the new Video Card
- Latest Mobo bios installed
- Reset bios to defaults
- Tried running system drives off different sata controllers.
- Raid0 array is also new and problem was happening before
Minidump File:
Script:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010411-11419-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Tue Jan 4 08:57:30.760 2011 (UTC + 11:00)
System Uptime: 0 days 0:00:10.774
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffffffffffffc3, 1, fffff960001ffe34, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
7: 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: ffffffffffffffc3, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960001ffe34, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d040e0
ffffffffffffffc3
FAULTING_IP:
win32k!GetIMEShowStatus+8
fffff960`001ffe34 0f9540c3 setne byte ptr [rax-3Dh]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: LogonUI.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005445110 -- (.trap 0xfffff88005445110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff96000367d00
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001ffe34 rsp=fffff880054452a8 rbp=fffff88005445360
r8=0000000000000020 r9=0000000000010024 r10=fffff96000194064
r11=000007fffffde000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!GetIMEShowStatus+0x8:
fffff960`001ffe34 0f9540c3 setne byte ptr [rax-3Dh] ds:0024:ffffffff`ffffffc3=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4cf14 to fffff80002acc740
STACK_TEXT:
fffff880`05444fa8 fffff800`02b4cf14 : 00000000`00000050 ffffffff`ffffffc3 00000000`00000001 fffff880`05445110 : nt!KeBugCheckEx
fffff880`05444fb0 fffff800`02aca82e : 00000000`00000001 fffffa80`09904b60 fffff880`78747300 fffff880`0000000f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`05445110 fffff960`001ffe34 : fffff960`0019409a 00000000`00000000 00000000`00000000 00000000`0000012c : nt!KiPageFault+0x16e
fffff880`054452a8 fffff960`0019409a : 00000000`00000000 00000000`00000000 00000000`0000012c 00000000`00000000 : win32k!GetIMEShowStatus+0x8
fffff880`054452b0 fffff800`02acb993 : fffffa80`09904b60 fffff880`05445360 00000000`001359e0 00000000`00000020 : win32k!NtUserCallNoParam+0x36
fffff880`054452e0 00000000`77add19a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0029ec78 fffff800`02ac4080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77add19a
fffff880`054456c0 0000007f`fffffff8 : fffff880`05445840 fffff960`001fd9dc fffff800`02ae85be 00000000`00000000 : nt!KiCallUserMode
fffff880`054456c8 fffff880`05445840 : fffff960`001fd9dc fffff800`02ae85be 00000000`00000000 fffff880`054460b0 : 0x7f`fffffff8
fffff880`054456d0 fffff960`001fd9db : fffff800`02ae85be 00000000`00000000 fffff880`054460b0 00000000`00000000 : 0xfffff880`05445840
fffff880`054456d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!AssociateInputContextEx+0x1cb
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
6 errors : !win32k (fffff960001ff136-fffff960001ffe36)
fffff960001ff130 88 ad 00 00 00 80 *6b 07 80 a0 ad 00 00 00 7f 48 ......k........H
...
fffff960001ff930 01 48 85 c9 74 08 *c8 8b d7 e8 f2 eb f3 ff ba 08 .H..t...........
...
fffff960001ffa30 83 64 24 50 00 33 *7f 89 7c 24 40 48 3b 0d 8e 08 .d$P.3..|$@H;...
...
fffff960001ffab0 e8 6b b8 f8 ff 48 *09 44 24 48 eb 23 33 c0 48 89 .k...H.D$H.#3.H.
...
fffff960001ffd30 44 24 58 48 89 81 *d0 01 00 00 48 89 74 24 60 ff D$XH......H.t$`.
...
fffff960001ffe30 80 0b 1a 00 0f 95 *40 c3 90 90 90 90 90 90 90 90 ......@.........
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
---------
7: 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: ffffffffffffffc3, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960001ffe34, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffffffffffc3
FAULTING_IP:
win32k!GetIMEShowStatus+8
fffff960`001ffe34 0f9540c3 setne byte ptr [rax-3Dh]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: LogonUI.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005445110 -- (.trap 0xfffff88005445110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff96000367d00
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001ffe34 rsp=fffff880054452a8 rbp=fffff88005445360
r8=0000000000000020 r9=0000000000010024 r10=fffff96000194064
r11=000007fffffde000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!GetIMEShowStatus+0x8:
fffff960`001ffe34 0f9540c3 setne byte ptr [rax-3Dh] ds:0024:ffffffff`ffffffc3=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4cf14 to fffff80002acc740
STACK_TEXT:
fffff880`05444fa8 fffff800`02b4cf14 : 00000000`00000050 ffffffff`ffffffc3 00000000`00000001 fffff880`05445110 : nt!KeBugCheckEx
fffff880`05444fb0 fffff800`02aca82e : 00000000`00000001 fffffa80`09904b60 fffff880`78747300 fffff880`0000000f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`05445110 fffff960`001ffe34 : fffff960`0019409a 00000000`00000000 00000000`00000000 00000000`0000012c : nt!KiPageFault+0x16e
fffff880`054452a8 fffff960`0019409a : 00000000`00000000 00000000`00000000 00000000`0000012c 00000000`00000000 : win32k!GetIMEShowStatus+0x8
fffff880`054452b0 fffff800`02acb993 : fffffa80`09904b60 fffff880`05445360 00000000`001359e0 00000000`00000020 : win32k!NtUserCallNoParam+0x36
fffff880`054452e0 00000000`77add19a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0029ec78 fffff800`02ac4080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77add19a
fffff880`054456c0 0000007f`fffffff8 : fffff880`05445840 fffff960`001fd9dc fffff800`02ae85be 00000000`00000000 : nt!KiCallUserMode
fffff880`054456c8 fffff880`05445840 : fffff960`001fd9dc fffff800`02ae85be 00000000`00000000 fffff880`054460b0 : 0x7f`fffffff8
fffff880`054456d0 fffff960`001fd9db : fffff800`02ae85be 00000000`00000000 fffff880`054460b0 00000000`00000000 : 0xfffff880`05445840
fffff880`054456d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!AssociateInputContextEx+0x1cb
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
6 errors : !win32k (fffff960001ff136-fffff960001ffe36)
fffff960001ff130 88 ad 00 00 00 80 *6b 07 80 a0 ad 00 00 00 7f 48 ......k........H
...
fffff960001ff930 01 48 85 c9 74 08 *c8 8b d7 e8 f2 eb f3 ff ba 08 .H..t...........
...
fffff960001ffa30 83 64 24 50 00 33 *7f 89 7c 24 40 48 3b 0d 8e 08 .d$P.3..|$@H;...
...
fffff960001ffab0 e8 6b b8 f8 ff 48 *09 44 24 48 eb 23 33 c0 48 89 .k...H.D$H.#3.H.
...
fffff960001ffd30 44 24 58 48 89 81 *d0 01 00 00 48 89 74 24 60 ff D$XH......H.t$`.
...
fffff960001ffe30 80 0b 1a 00 0f 95 *40 c3 90 90 90 90 90 90 90 90 ......@.........
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
---------
7: 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: ffffffffffffffc3, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960001ffe34, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ffffffffffffffc3
FAULTING_IP:
win32k!GetIMEShowStatus+8
fffff960`001ffe34 0f9540c3 setne byte ptr [rax-3Dh]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: LogonUI.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005445110 -- (.trap 0xfffff88005445110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff96000367d00
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001ffe34 rsp=fffff880054452a8 rbp=fffff88005445360
r8=0000000000000020 r9=0000000000010024 r10=fffff96000194064
r11=000007fffffde000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!GetIMEShowStatus+0x8:
fffff960`001ffe34 0f9540c3 setne byte ptr [rax-3Dh] ds:0024:ffffffff`ffffffc3=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4cf14 to fffff80002acc740
STACK_TEXT:
fffff880`05444fa8 fffff800`02b4cf14 : 00000000`00000050 ffffffff`ffffffc3 00000000`00000001 fffff880`05445110 : nt!KeBugCheckEx
fffff880`05444fb0 fffff800`02aca82e : 00000000`00000001 fffffa80`09904b60 fffff880`78747300 fffff880`0000000f : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`05445110 fffff960`001ffe34 : fffff960`0019409a 00000000`00000000 00000000`00000000 00000000`0000012c : nt!KiPageFault+0x16e
fffff880`054452a8 fffff960`0019409a : 00000000`00000000 00000000`00000000 00000000`0000012c 00000000`00000000 : win32k!GetIMEShowStatus+0x8
fffff880`054452b0 fffff800`02acb993 : fffffa80`09904b60 fffff880`05445360 00000000`001359e0 00000000`00000020 : win32k!NtUserCallNoParam+0x36
fffff880`054452e0 00000000`77add19a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0029ec78 fffff800`02ac4080 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77add19a
fffff880`054456c0 0000007f`fffffff8 : fffff880`05445840 fffff960`001fd9dc fffff800`02ae85be 00000000`00000000 : nt!KiCallUserMode
fffff880`054456c8 fffff880`05445840 : fffff960`001fd9dc fffff800`02ae85be 00000000`00000000 fffff880`054460b0 : 0x7f`fffffff8
fffff880`054456d0 fffff960`001fd9db : fffff800`02ae85be 00000000`00000000 fffff880`054460b0 00000000`00000000 : 0xfffff880`05445840
fffff880`054456d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!AssociateInputContextEx+0x1cb
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
6 errors : !win32k (fffff960001ff136-fffff960001ffe36)
fffff960001ff130 88 ad 00 00 00 80 *6b 07 80 a0 ad 00 00 00 7f 48 ......k........H
...
fffff960001ff930 01 48 85 c9 74 08 *c8 8b d7 e8 f2 eb f3 ff ba 08 .H..t...........
...
fffff960001ffa30 83 64 24 50 00 33 *7f 89 7c 24 40 48 3b 0d 8e 08 .d$P.3..|$@H;...
...
fffff960001ffab0 e8 6b b8 f8 ff 48 *09 44 24 48 eb 23 33 c0 48 89 .k...H.D$H.#3.H.
...
fffff960001ffd30 44 24 58 48 89 81 *d0 01 00 00 48 89 74 24 60 ff D$XH......H.t$`.
...
fffff960001ffe30 80 0b 1a 00 0f 95 *40 c3 90 90 90 90 90 90 90 90 ......@.........
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
---------
Any help is greatly appreciated, I could just let it go to standby and it wakes fine and this really wouldn't be much of an issue... however I'm a bit of a perfectionist so these kinds of problem really bug me, just knowing it is there.
I realise it is probably a hardware issue so being able to pinpoint what actually needs to be replaced would be great instead of randomly guessing and wasting money.
Cheers
Last edited by RonDMC; 03 Jan 2011 at 17:59.