Windows 7: Systematic crash on first boot

gregfrip04 · 13 Jul 2010

Hello,

I am new on this forum. I am not an expert but neither am I a total novice; I have assembled my own systems for a while a never experience such a problem before.

I have a systematic crash on first boot every day. I get the BSOD after the black Windows starting screen, before the blue windows cession opening screen.
The only working solution I found so far is to stop (cut off power) and restart about 1 minute later. Then Windows will start normally. Any shut down and restart afterward will go on without trouble. The problem only happens on first boot when the system has been shut down for a while (overnight!).

So far I have tried the following:
I ran the Windows repair CD
I re-installed Windows 7 Ultimate 64

Then I thought of a hardware problem so:
I changed the PSU for a brand new Corsair HX520w
I changed the HDD for a brand new WD Caviar Black 750 Gb
I changed the GPU for a brand new Sparkle NVIDIA GT220 1Gb DDR3

I ran MEMTEST86+ overnight without error
I ran a LinX Test without error

I use WhoCrashed Home Edition 2.10 to read minidump files. They're different most of the time. The last one from this morning read the following:

Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 13/07/2010 07:10:35 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFFB960000B5DFD, 0x8, 0xFFFFB960000B5DFD, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\071310-15584-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

Conclusion
1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

If you have any idea about my problem, please help.

Thank you, Greg.

ttran · 13 Jul 2010

Can you please upload the actual crash dump file so that we can take further look? stop code 50 usually hardware come into play sometime
https://www.sevenforums.com/crash-loc...d-problem.html

gregfrip04 · 13 Jul 2010

Sorry, I ran Ccleaner and the .dmp file is now lost.
I'll send you the next one tomorrow!

Jonathan_King · 13 Jul 2010

Please use these instructions after is generates more dumps: https://www.sevenforums.com/crashes-d...tructions.html

gregfrip04 · 13 Jul 2010

I followed instructions and attached the report and Windows7_BSOD file.

I will post again tomorrow after new BSOD with dmp file.

Regards, Greg.

Jonathan_King · 13 Jul 2010

Sorry, there are no dmps in that report. Has the system crashed at all since then?

Try increasing the RAM voltage slightly.

gregfrip04 · 14 Jul 2010

Hello,

Thank you for your advice. I increased the RAM voltage to 1.70. I can only increase by 0.10 steps. I initially set voltage on 1.60 as RAM manufacturer indicates voltage should be 1.65.

However I had again two crashes this morning: the first time did not generate a dmp I only had a BSOD with a short notice so I pushed the reset button and the system crashed again and generated a dmp on the second time. Them I cut power off, waited 1 minute and restarted normally.

Thanks again for your help.

Regards, Greg.

reventon · 15 Jul 2010

Hi,

BUGCHECK SUMMARY

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jul 14 17:39:04.501 2010 (GMT+12)
System Uptime: 0 days 0:00:09.937
BugCheck 50, {ffffb8a000a2db78, 0, fffff800035b4726, 7}
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+22 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

No 3rd party driver mentioned directly, however one thing drew my attention immediately.

Code:


AsIO.sys     Mon Aug 03 19:03:16 2009 (4A768BB4)

That driver has caused many BSODs before, it needs to be removed.

Remove it by uninstalling any ASUS hardware monitoring or overclocking software that you have.

Do that and see how it goes,

Regards,
Reventon

gregfrip04 · 15 Jul 2010

Hello,

Thanks for you advice and the time you spent on my trouble.
The only ASUS monitoring/overclocking software that I have is EPU-6 Engine. It's been useful as it decreases a lot of the fan noise. Anyway, if it's causing trouble then I will remove it.

I am currently on holidays so I don't have access to my desktop computer. I'll be back on July 21. I'll follow your advice then post to let you know the results.

Thanks again.

Regards, Greg

reventon · 15 Jul 2010

Quote:

The only ASUS monitoring/overclocking software that I have is EPU-6 Engine. It's been useful as it decreases a lot of the fan noise. Anyway, if it's causing trouble then I will remove it.

Yes, EPU-6 is what the driver would be a part of. You may want to investigate other controllers for your fan.