BSOD on cold boot

[dele2k]

Hi,

every time I do a cold boot, my computer crashes with bluescreen at exactly the same time, the Win7 loading screen. After this, I turn the computer off, than i turn off the power supply and a few seconds later, I turn it on again. If I now start the computer, it will boot without any problems as well as running high performance applications. I never had a bluescreen after this annyoing procedure.
EDIT: This error occurs since I've set up the computer.

I tried ram timings from G.Skill support forum, but it doesn't change anything.

So i decided to install Microsofts debugging tool, to analyze the BSOD, and guess what! I really need your help now, because I have no conception of analyzing bluescreens and stuff which comes with it.

My system configuration should be viewable in my profile details.

Excuse my bad English, I tried my best

Thanks in advance!

http://paste2.org/p/597245

or

[LIST=1]
[*]Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
[*]Copyright (c) Microsoft Corporation. All rights reserved.
[*]Loading Dump File [C:\Windows\MEMORY.DMP]
[*]Kernel Summary Dump File: Only kernel address space is 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.16385.amd64fre.win7_rtm.090713-1255
[*]Machine Name:
[*]Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
[*]Debug session time: Wed Jan  6 19:32:14.972 2010 (GMT+1)
[*]System Uptime: 0 days 0:00:08.392
[*]Loading Kernel Symbols
[*]...............................................................
[*].....................
[*]Loading User Symbols
[*]*******************************************************************************
[*]*                                                                             *
[*]*                        Bugcheck Analysis                                    *
[*]*                                                                             *
[*]*******************************************************************************
[*]Use !analyze -v to get detailed debugging information.
[*]BugCheck 7E, {ffffffffc0000005, fffff80002aa53d7, fffff880031a0538, fffff8800319fd90}
[*]Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
[*]Followup: MachineOwner
[*]---------
[*]2: kd> !analyze -v
[*]*******************************************************************************
[*]*                                                                             *
[*]*                        Bugcheck Analysis                                    *
[*]*                                                                             *
[*]*******************************************************************************
[*]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
[*]This is a very common bugcheck.  Usually the exception address pinpoints
[*]the driver/function that caused the problem.  Always note this address
[*]as well as the link date of the driver/image that contains this address.
[*]Arguments:
[*]Arg1: ffffffffc0000005, The exception code that was not handled
[*]Arg2: fffff80002aa53d7, The address that the exception occurred at
[*]Arg3: fffff880031a0538, Exception Record Address
[*]Arg4: fffff8800319fd90, Context Record Address
[*]Debugging Details:
[*]------------------
[*]EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
[*]FAULTING_IP:
[*]nt!MiPfnShareCountIsZero+77
[*]fffff800`02aa53d7 0fb6511a        movzx   edx,byte ptr [rcx+1Ah]
[*]EXCEPTION_RECORD:  fffff880031a0538 -- (.exr 0xfffff880031a0538)
[*]ExceptionAddress: fffff80002aa53d7 (nt!MiPfnShareCountIsZero+0x0000000000000077)
[*]   ExceptionCode: c0000005 (Access violation)
[*]  ExceptionFlags: 00000000
[*]NumberParameters: 2
[*]   Parameter[0]: 0000000000000000
[*]   Parameter[1]: ffffffffffffffff
[*]Attempt to read from address ffffffffffffffff
[*]CONTEXT:  fffff8800319fd90 -- (.cxr 0xfffff8800319fd90)
[*]rax=000fffffffffffff rbx=fffffa80037b3390 rcx=0002fa8003a14660
[*]rdx=0000000000000000 rsi=fffff68000001d28 rdi=0000000000000000
[*]rip=fffff80002aa53d7 rsp=fffff880031a0770 rbp=0000058000000000
[*] r8=0000100000135c22  r9=0000000000000006 r10=fffff8a0005ca8a8
[*]r11=0000000000000000 r12=2aaaaaaaaaaaaaab r13=fffffa8003a30f80
[*]r14=fffffa80037b3390 r15=fffffa8003a30f80
[*]iopl=0         nv up ei pl nz na po nc
[*]cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
[*]nt!MiPfnShareCountIsZero+0x77:
[*]fffff800`02aa53d7 0fb6511a        movzx   edx,byte ptr [rcx+1Ah] ds:002b:0002fa80`03a1467a=??
[*]Resetting default scope
[*]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
[*]PROCESS_NAME:  System
[*]CURRENT_IRQL:  2
[*]ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
[*]EXCEPTION_PARAMETER1:  0000000000000000
[*]EXCEPTION_PARAMETER2:  ffffffffffffffff
[*]READ_ADDRESS:  ffffffffffffffff
[*]FOLLOWUP_IP:
[*]nt!MiPfnShareCountIsZero+77
[*]fffff800`02aa53d7 0fb6511a        movzx   edx,byte ptr [rcx+1Ah]
[*]BUGCHECK_STR:  0x7E
[*]LOCK_ADDRESS:  fffff80002c8f400 -- (!locks fffff80002c8f400)
[*]Resource @ nt!PiEngineLock (0xfffff80002c8f400)    Exclusively owned
[*]     Threads: fffffa8003cf0b60-01<*>
[*]1 total locks, 1 locks currently held
[*]PNP_TRIAGE:
[*]        Lock address  : 0xfffff80002c8f400
[*]        Thread Count  : 1
[*]        Thread address: 0xfffffa8003cf0b60
[*]        Thread wait   : 0x218
[*]LAST_CONTROL_TRANSFER:  from fffff80002dfb824 to fffff80002a8cf00
[*]STACK_TEXT:
[*]fffff880`031a0770 fffff800`02abe88f : 00000000`00000001 fffff680`00001d28 52c00001`29113025 fffffa80`05829000 : nt!MiPfnShareCountIsZero+0x77
[*]fffff880`031a07e0 fffff800`02abdb51 : 00000000`00000000 fffff680`00001ff8 fffffa80`03cd1040 00000000`00000000 : nt!MiDeletePteRun+0x49f
[*]fffff880`031a0990 fffff800`02ac05d9 : 00000000`00000000 00000000`00f9ffff 00000000`00000000 00000000`00128487 : nt!MiDeleteVirtualAddresses+0x408
[*]fffff880`031a0b50 fffff800`02da2e50 : fffffa80`04d12820 0007ffff`00000000 fffffa80`057e49b0 fffffa80`057e49b0 : nt!MiRemoveMappedView+0xd9
[*]fffff880`031a0c70 fffff800`02da325b : 00000000`00000000 00000000`00290000 fffffa80`00000001 fffff800`02a8b000 : nt!MiUnmapViewOfSection+0x1b0
[*]fffff880`031a0d30 fffff800`02a8c153 : 00000000`00000000 00000000`000021d9 fffffa80`03cd1040 00000000`00003a34 : nt!NtUnmapViewOfSection+0x5f
[*]fffff880`031a0d80 fffff800`02a886f0 : fffff800`02e65699 00000000`00000000 fffff680`00007d00 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
[*]fffff880`031a0f18 fffff800`02e65699 : 00000000`00000000 fffff680`00007d00 00000000`00000000 fffff880`00000004 : nt!KiServiceLinkage
[*]fffff880`031a0f20 fffff800`02e657dc : ffffffff`80000178 fffffa80`08000000 00000000`00290000 ffffffff`800001b0 : nt!MmCheckSystemImage+0x319
[*]fffff880`031a1050 fffff800`02e659f7 : ffffffff`80000178 fffff800`00000001 fffffa80`03c602b0 00000000`00000000 : nt!MiCreateSectionForDriver+0xcc
[*]fffff880`031a1100 fffff800`02e7129a : 00000000`00000000 fffff880`031a12d8 fffffa80`03cf0b60 fffff880`02f63100 : nt!MiObtainSectionForDriver+0xd7
[*]fffff880`031a1160 fffff800`02e73ebd : fffff880`031a12d8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmLoadSystemImage+0x23a
[*]fffff880`031a1280 fffff800`02f07780 : 00000000`00000001 00000000`00000000 fffff880`031a1828 ffffffff`80000188 : nt!IopLoadDriver+0x44d
[*]fffff880`031a1550 fffff800`02d45cdc : fffff880`031a1860 fffffa80`00000000 00000000`c0000023 00000000`00000000 : nt!PipCallDriverAddDeviceQueryRoutine+0x390
[*]fffff880`031a1650 fffff800`02d45fea : 00000000`00000000 00000000`00000000 fffff880`031a1860 fffff880`031a1828 : nt!RtlpCallQueryRegistryRoutine+0xf4
[*]fffff880`031a16d0 fffff800`02e7772c : fffffa80`04a9a6e0 00000000`00000000 00000000`c0000034 fffff880`031a1828 : nt!RtlQueryRegistryValues+0x17e
[*]fffff880`031a17a0 fffff800`02e78ec2 : fffffa80`04a8c010 fffffa80`04a9a6e0 00000000`00000002 fffff8a0`0000004c : nt!PipCallDriverAddDevice+0x45c
[*]fffff880`031a1950 fffff800`02e7935c : fffff800`02c8cd80 00000000`00000000 00000000`00000001 fffff800`02cf971c : nt!PipProcessDevNodeTree+0x2b2
[*]fffff880`031a1bc0 fffff800`02b8d322 : 00000001`00000003 fffff800`02c305f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
[*]fffff880`031a1c10 fffff800`02a9a161 : fffff800`02b8d020 fffff800`02b8d001 fffffa80`03cf0b00 00000000`0000055a : nt!PnpDeviceActionWorker+0x302
[*]fffff880`031a1cb0 fffff800`02d30166 : 004c004c`0044002e fffffa80`03cf0b60 00000000`00000080 fffffa80`03cd1040 : nt!ExpWorkerThread+0x111
[*]fffff880`031a1d40 fffff800`02a6b486 : fffff880`02f63180 fffffa80`03cf0b60 fffff880`02f6dfc0 00440042`004b0009 : nt!PspSystemThreadStartup+0x5a
[*]fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a0b10 00000000`00000000 : nt!KxStartSystemThread+0x16
[*]SYMBOL_STACK_INDEX:  0
[*]SYMBOL_NAME:  nt!MiPfnShareCountIsZero+77
[*]FOLLOWUP_NAME:  MachineOwner
[*]MODULE_NAME: nt
[*]DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
[*]STACK_COMMAND:  .cxr 0xfffff8800319fd90 ; kb
[*]IMAGE_NAME:  memory_corruption
[*]FAILURE_BUCKET_ID:  X64_0x7E_nt!MiPfnShareCountIsZero+77
[*]BUCKET_ID:  X64_0x7E_nt!MiPfnShareCountIsZero+77
[*]Followup: MachineOwner
[*]---------
[/LIST]

 

[Capt.Jack Sparrow]

Hi,

every time I do a cold boot, my computer crashes with bluescreen at exactly the same time, the Win7 loading screen. After this, I turn the computer off, than i turn off the power supply and a few seconds later, I turn it on again. If I now start the computer, it will boot without any problems as well as running high performance applications. I never had a bluescreen after this annyoing procedure.

I tried ram timings from G.Skill support forum, but it doesn't change anything.

So i decided to install Microsofts debugging tool, to analyze the BSOD, and guess what! I really need your help now, because I have no conception of analyzing bluescreens and stuff which comes with it.

My system configuration should be viewable in my profile details.

Excuse my bad English, I tried my best

Thanks in advance!

Hi, Welcome to SF,

Could you post your Dump file. Good work on Dump analysis but we need to run a different command to check the drivers. If you could post that we would be glad to help you out.

Thanks,
Captain

 

[dele2k]

Hi Captain,

I think I've read over this part in the tutorials how to post. I'm sorry I've no access to the dumpfile today, but I'll post it tomorrow asap!

Kind regards,

dele2k

 

[Capt.Jack Sparrow]

As far i look the Dump analysis the possible reason could be Memory Corruption

Run the Memory Diagonostic & Hard Driver Diagonstic
So to Start > Run > cmd and Right Click and Run as administrator and Type SFC/ SCANNOW

Hope this helps

Edit: Its OK Mate .. Just try these step.. Maybe this would fix your issues

 

[chev65]

The power supply is the usual suspect in this type of cold boot problem, especially true when you need to power cycle the power supply in order for it to boot up correctly. If you google around you will see similar complaints about this problem and the cure is usually the same, replace the power supply. If you have another PSU to try that would be helpful.

It's not really a power supply output issue so much as the board getting a low voltage signal on cold start ups and then powering down the system because it was programmed to do so in low voltage situations. Some power supplies have this problem while others don't.

 

[dele2k]

Okay, I'll give it a try. What means memory cooruption? Broken?

 

[chev65]

Capt Jack means that sometimes when you use incorrect memory settings or unmatched memory you can sometimes corrupt the files on your Op system harddrives because improper instructions were written to it when the memory was messed up. Using sfc/scannow will usually fix those corrupted files for you.

 

[dele2k]

Capt Jack means that sometimes when you use incorrect memory settings or unmatched memory you can sometimes corrupt the files on your Op system harddrives because improper instructions were written to it when the memory was messed up. Using sfc/scannow will usually fix those corrupted files for you.

Many thanks for your fast reply. Could it be usefull do post my PSU manufactuer and product?

be quiet! Straight Power BQT E7-600W

 

[chev65]

That is cutting it kinda close with your GTX285 although it may be enough power it's hard to say. Most of the PSU manufactures are aware of the cold boot problem with i7 boards and certain power supplies so you might try and contact them to see if they will exchange or upgrade you to a more compatible model.

 

[computersplus]

Pwer Supply

you need a better power supply the minimum watts on that card is 550 and that PSU only has 18 amp +12 rails which just is not enough

the PSU makers need to wake up and quit selling these multi rail underpowered PSU units they are fine for an "average" computer but not for high draw gaming hardware

 

[computersplus]

Power Supply Info

The following issues are signs your power supply might not be up to the task:

1. During boot, your machine takes a very long time to get past the POST screen

2. During heavy graphics use, you start getting hard drive errors. The hard drives and the video card both live on the 12V rail and thus if the video card starts pulling too much power it can cause hard drive errors.

3. Memory errors in programs, but when you test the memory it tests clean. This is a similar issue to the second one. The electricity in a computer has to maintain a certain flow and that flow is used to run the memory. If that flow starts spiking around, it will cause memory errors.

4. Random shutdowns and reboots during CPU intensive activity. Like the memory, the CPU has to maintain a certain frequency across its calculations. That frequency is directly related to the voltage the CPU receives, and if this voltage fluctuates too much, the CPU will fail just like memory will. When memory fails, a program will crash, but when the CPU fails, the whole machine crashes.

5. Hangs during boot where POST never even comes up that can then be fixed by resetting the computer, sometimes multiple times. This is the same as the POST problem, where the hardware isn't getting checked properly and hangs while waiting.

6. Your computer starts to boot, but then just shuts down, or gets locked in a loop of constantly trying to boot.

 

[computersplus]

more info

There are some basic issues to consider. Wattage must be high enough to run everything, and for a modern machine that often means 500 watts or higher. However, people are buying 500-650 watt power supplies and still having problems, and the reason is that not all wattage is created equal. Amperage is just as important, and arguable more important on modern machines. Your video card especially will have an amp requirement. It should be right on the hardware specs where it will say "Requires a minimum of 28A on the 12V rail" or something similar.

Now, here is the tricky part: many modern power supplies share their amperage across multiple 12V rails. This was originally meant to distribute the current equally, making sure nothing failed. However, no one checked with the video card companies, who had figured out a way to dynamically alter the voltage required by the video card based on use. This gave us all those neat features like cards that can overclock when you start a game or where the fan changes speed based on the heat of the card. However, it also means those shared rails get all confused and try to balance the load, often causing graphical slowdown and hard drive errors.

This means a power supply may say "30A" and then have 4 12V rails sharing that 30A and balancing the load, which will not be enough for a video card that says "minimum 30A on the 12V rail". You will get tons of errors. This gives you two choices: shoot for about 5 amps higher than your card says, which may be pretty hard to find, or find a power supply that offers the amperage you need in a single rail.

 

[chev65]

I'm glad you agree with my assessment of the problem ComputersPlus.

This problem can also happen when the power supply has plenty of power. The problem mostly occurs on a cold boot because that is when power draw is highest. As soon as the board senses the power dropping below a certain level it will automatically shut down to save itself. It's a well documented problem with certain power supplies but total output sometimes isn't a factor.

I would still go with a higher output model for that system. I'd say 750 watts with plenty of amps on the 12 volts rails will do the job. I'm using a 1000watt modular unit myself for a single GTX280, which leaves plenty of power for my substantial overclock.

 

[dele2k]

Thanks for your answers.

I couldn't image, that my PSU is responsible for these errors, because I disagree with most of the points computersplus posted. If my system is once running, I could play crysis at ultra details 2 weeks long without errors or bluescreens. No errors, drive errors and random shutdowns at all while system is running. I'll upload the dump file tomorrow and we'll know a bit more than.

Good night from Germany

 

[computersplus]

Power Supply

I just wanted to post the info for you to digest this is something that gets overlooked all the time people focus on the other high power hardware PSU's are boring to most people but it is truly the heart of any good system and I have seen post after post here with people trying to run today's most demanding video cards with stock OEM power supply's or power supply's that promise lot's of watts but don't really deliver the goods these power supply's for sale are like the cheap stereo speakers and amps that say 1000 watts but only deliver 100 the way they rate the power supply's are trickery they list peak watt's which don't mean a thing you want constant power or they will rate it at 40 degrees celcius and not 50 because the lower the temp the more power it can deliver but it's not a relative factor we need to know what it can do at a high temp real world hot case not on a bench with no restrictive air flow issues so all is not what it seems.

Yes there are a lot of other things that could be causing the problem but until you resolve the power issue you will be chasing your tail in my opinion.

 

[computersplus]

I'm glad you agree with my assessment of the problem ComputersPlus.

This problem can also happen when the power supply has plenty of power. The problem mostly occurs on a cold boot because that is when power draw is highest. As soon as the board senses the power dropping below a certain level it will automatically shut down to save itself. It's a well documented problem with certain power supplies but total output sometimes isn't a factor.

I would still go with a higher output model for that system. I'd say 750 watts with plenty of amps on the 12 volts rails will do the job. I'm using a 1000watt modular unit myself for a single GTX280, which leaves plenty of power for my substantial overclock.

Loss of or unstable power good signal

 

[chev65]

Thanks for your answers.

I couldn't image, that my PSU is responsible for these errors, because I disagree with most of the points computersplus posted. If my system is once running, I could play crysis at ultra details 2 weeks long without errors or bluescreens. No errors, drive errors and random shutdowns at all while system is running. I'll upload the dump file tomorrow and we'll know a bit more than.

Good night from Germany

Like I said earlier power output may or may not be a factor. The board is causing the shutdowns due to low voltage at start up, it's a built in safty feature. Easy way to tell is to try out an another power supply and see if the situation changes.

 

[dele2k]

Here I come with the dump file. Bluescreen again today :/ But I found out, that I don't have to turn off the PSU, I only have to turn off my pc and turn it on again to get it working. Attachements are not working for me, so I uploaded it to a file hoster.
Btw: Updating to the latest bios version doesn't help.

Hotfile.com: One click file hosting

 

[computersplus]

Security Software

what are you using for security software? is this a brand new install? rootkit infections are everywhere and love to cause BSOD's

 

[dele2k]

The installation is about 1 month old. I currently don't use any antivir software.