New
#1
Systematic crash on first boot
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.