BSOD on startup - Please help

[mitsurugi]

Hi all,

For some reason I have been getting BSODs on startup to W7. It seems that these only happen after the computer has been off for a few days - not sure what is causing it.

This is on a desktop that I recently built - i5-750, 4770, W7 Professional - I can give all specs if needed. I've ran HD tests and Memtest86 and everything checks out fine.

I've uploaded the zipped minidump files - thanks in advance for the help!

 

[Jonathan_King]

Looks like it might be caused by memory. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run it for at least 5 passes.

I recommend running that memory test immediately after the computer has been left off overnight.

[FONT=lucida console]
BugCheck 24, {1904fb, fffff880031856d8, fffff88003184f40, fffff80002e29b60}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFcb+280 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff96000187b87, fffff880025e4ec0, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff96004116c98, 8, fffff96004116c98, 2}
Probably caused by : win32k.sys ( win32k!bSpEnableSprites+243 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {5005, fffff70001080000, eb, ec}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ff2a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {fffffa8404fa9190, 2, 0, fffff80002a67eeb}
Probably caused by : win32k.sys ( win32k!ComputeFileviewCheckSum+21 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

Update these old drivers or their repective programs:

[FONT=lucida console]
fffff880`04107000 fffff880`0410f000   BS_I2cIo BS_I2cIo.sys Mon Jun 16 02:45:18 2008 (48560BFE)
fffff880`04120000 fffff880`04128000   BIOS64   BIOS64.sys   Sat Jun 07 20:12:00 2003 (3EE27F50)
fffff880`04252000 fffff880`04266380   pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)[/FONT]

You might also consider uninstalling Trend Micro and replacing it with Microsoft Security Essentials:

fffff880`02a0c000 fffff880`02bf9000   vsapint  vsapint.sys  Fri Dec 04 03:29:15 2009 (4B18C85B)

 

[mitsurugi]

I've ran the Memtest86 a few different times and it checks out fine.

How do you update the drivers that you listed? Any other ideas to what might be causing this?

 

[Jonathan_King]

BIOS64.sys and BS_I2cIo.sys belong to BioStar. Please update your motherboard or chipset drivers: BIOSTAR :: Download

pcouffin.sys looks like it is related to a DVD program, like DVD Fab, etc.

Follow these instructions for enabling Driver Verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Be sure to upload any new dmps.

 

[mitsurugi]

Well, thought I maybe had it by setting better memory timings, but nope. Here are a couple of new dump files if you guys could help me out.

Also, this only happens after my computer has been off for a couple of days or more. If I shut it down and reboot it within a day or so, it works fine.

Thanks in advance for the help!

 

[Lordbob75]

This very much points to bad RAM. Take out each stick and boot with each one individually to see if it works.
I would also try cleaning out the RAM sockets with compressed air (short bursts).

It sounds like the RAM usually works, but not always.
I find it odd that this will only occur after a few days, not immediately. Definitely run MemTest, give it a good 5 or 6 passes. Do this for each stick if you can.

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


Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp1_623mindumps.zip\623mindumps\062310-13718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
Debug session time: Wed Jun 23 18:03:41.359 2010 (UTC - 7:00)
System Uptime: 0 days 0:00:22.453
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffe28019ce4a69, 1, fffff9600029bb64, 7}


Could not read faulting driver name
Probably caused by : memory_corruption

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

3: 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: ffffe28019ce4a69, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff9600029bb64, 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 fffff80002cc50e0
 ffffe28019ce4a69 

FAULTING_IP: 
win32k!GreSetBoundsRect+24
fffff960`0029bb64 4821749821      and     qword ptr [rax+rbx*4+21h],rsi

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880057ca230 -- (.trap 0xfffff880057ca230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880057ca448 rbx=0000000000000000 rcx=000000000c010263
rdx=000000000c010263 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600029bb64 rsp=fffff880057ca3c0 rbp=fffff880057ca520
 r8=0000000000000009  r9=0000000000000001 r10=fffff96000297eac
r11=fffff880057ca498 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!GreSetBoundsRect+0x24:
fffff960`0029bb64 4821749821      and     qword ptr [rax+rbx*4+21h],rsi ds:fffff880`057ca469=82fffff880057ca5
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b0c789 to fffff80002a8d600

STACK_TEXT:  
fffff880`057ca0c8 fffff800`02b0c789 : 00000000`00000050 ffffe280`19ce4a69 00000000`00000001 fffff880`057ca230 : nt!KeBugCheckEx
fffff880`057ca0d0 fffff800`02a8b6ee : 00000000`00000001 fffffa80`05146980 00000000`00000000 fffff960`000bfb49 : nt! ?? ::FNODOBFM::`string'+0x40e4b
fffff880`057ca230 fffff960`0029bb64 : fffff900`c2394010 00000000`00000000 fffff900`c2394010 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`057ca3c0 fffff960`00297f18 : fffffa80`05146980 fffff880`057ca520 00000000`0c010263 fffff880`057ca520 : win32k!GreSetBoundsRect+0x24
fffff880`057ca450 fffff800`02a8c853 : 00000000`0c010263 00000000`00000000 00000000`00000009 fffff960`0029a420 : win32k!NtGdiSetBoundsRect+0x6c
fffff880`057ca4a0 000007fe`fdb8704a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`024bec78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdb8704a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    fffff9600029bb66 - win32k!GreSetBoundsRect+26
    [ 70:74 ]
1 error : !win32k (fffff9600029bb66)

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

~Lordbob

 

[mitsurugi]

Thanks for the reply. I did a search about cold boot problems with G. Skill memory (the kind that I have) and it seems that lots of people have reported issues with BSODs after the computer is off for a while. I'll check my sticks separately and see where that gets me. I'll let you guys know what I find.

 

[Jonathan_King]

In my experience, several cold boot issues were solved by increasing the RAM voltage slightly.

 

[mitsurugi]

So I ram Memtest on each ram stick individually for 7 passes, and found no errors on either. This is getting a little frustrating.

How do I increase the voltage slightly, and what should I increase it to? Thanks

 

[Lordbob75]

So I ram Memtest on each ram stick individually for 7 passes, and found no errors on either. This is getting a little frustrating.

How do I increase the voltage slightly, and what should I increase it to? Thanks

You will need to go into the BIOS and manually change it.
Make sure that you look up documentation for your motherboard and RAM so you know what the safe voltage range is.

~Lordbob

 

[mitsurugi]

Ok, so I tried increasing the ram voltage to 1.6 and I thought I fixed it, but had another cold boot BSOD today.

I've uploaded the most recent dump file if you guys could help me out again. Thanks

 

[Lordbob75]

The dump doesn't tell us much. The stop code points to memory again.

You might have a bad slot. Can you take out all but one stick and see if that helps?

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


Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp2_7-8-10mindumps.zip\7-8-10mindumps\070810-16156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c57e50
Debug session time: Thu Jul  8 18:03:57.953 2010 (UTC - 7:00)
System Uptime: 0 days 0:00:08.046
Loading Kernel Symbols
...............................................................
....................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80036e8a40, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80036e8a40
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002afdede to fffff80002a8a600

STACK_TEXT:  
fffff880`03f5a828 fffff800`02afdede : 00000000`0000001a 00000000`00041790 fffffa80`036e8a40 00000000`0000ffff : nt!KeBugCheckEx
fffff880`03f5a830 fffff800`02abdcc9 : 00000000`00000000 000007fe`fe650fff fffffa80`00000000 fffff683`ff7f3080 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`03f5a9f0 fffff800`02da4170 : fffffa80`051c1140 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`03f5ab10 fffff800`02da457b : 00000980`00000000 000007fe`fe450000 fffffa80`00000001 fffffa80`04f8c010 : nt!MiUnmapViewOfSection+0x1b0
fffff880`03f5abd0 fffff800`02a89853 : 00000000`00000000 00000000`0032f580 fffffa80`050969d0 00000000`77239360 : nt!NtUnmapViewOfSection+0x5f
fffff880`03f5ac20 00000000`7716fffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0032f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7716fffa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02afdede cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

Followup: MachineOwner
---------

~Lordbob

 

[mitsurugi]

Hey guys, just thought I'd update this thread with my solution.

It turns out that my memory was the problem even though I couldn't get memtest to show anything. Seems like others on the web have had a similar "cold boot" problem with the particular G Skill memory that I have. Anyway, I sent it back to G Skill under warranty and they sent me brand new memory - problem solved and no more booting/blue screen issues.

Thanks to everyone that helped me troubleshoot this issue - you guys are great

 

[Jonathan_King]

Thanks for the report! I'm glad to hear the solution.