• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 7 boot error

KentState

KentState

Diamond Member
I'm having some type of BSOD error that occurs right after the Windows animation occurs at boot. A BSOD screen flashes and the system quickly reboots. System repair, restoring a previous backup image, safe mode and all else doesn't resolve the issue. How can I find the error message that is thrown during the BSOD?
 
Boot with logging enabled, then read the log and see what it has to say. There should also be an option to disable automatic restart, which is why you're only quickly seeing the BSOD.
 
How do I enable logging and where is the log placed? The BSOD occurs every time Windows starts even in safe mode.
 
The log gets written to the root of the boot drive (so usually the C drive). As for how you enable logging, it's an option at the F8 menu when booting.
 
Previous versions of Windows had a boot option to not reboot on STOP that appeared after one occurred, is that not still the case?
 
sounds like voltage prob - you didnt say how long you had it running properly -
boot into bios and set failsafe defaults
option 2 is to boot from Win 7 DVD and go to repair your computer, and when it finds your install go to repair startup and run it a few times
If it doesnt find your install, just click the radio button on the upper left (tools) and then go next to repair startup
You can also do a sfc /scannow from Win 7 DVD command prompt, but I dont think corrupted sys files are the prob
BSOD on boot is normally a serious HW prob - like maybe a vid card/RAM not seated fully, bad cable etc

I hate these Win 7 BSOD's. It just wont let you boot until you fix things, in a big ol loop.
 
Last edited:
The system has been running without incident since last July/August. Not overclocked or had any of the timings/voltages changed from the defaults. I will have to do some more digging when I get home.
 
KentState said:
The system has been running without incident since last July/August. Not overclocked or had any of the timings/voltages changed from the defaults. I will have to do some more digging when I get home.
Click to expand...

Sounds like it could be either ram or a HDD going south. Perhaps try Memtest for a few full runs before you boot to windows.

Larry
 
Win7AdvBoot.png


Enable Boot Logging boots up Windows with a log
Disable Automatic Restart On System Failure will keep Windows from immediately rebooting on a BSOD (allowing you to read the BSOD)
 
Been a little crazy and was able to start digging into the issue a little more today.

Basically, my computer has two logical volumes, one on the SSD and the second on a RAID 5 array. When I installed Win7, by accident I put the system partition on the RAID 5 array and for some reason, it has to initialize before the system will properly boot.

I removed the SSD drive, put in a new disk and set it to the boot drive. Installed a new instance of Win7 and loaded the Intel Matrix drivers. The array is currently rebuilding/repairing. Hopefully I can put the old SSD back in and be up and running.

If that works, my next issue will be converting the RAID 5 array to RAID 10.
 
Thats a whole lot of information you left out of your first post
Two logicals, plus RAID array, both SSD and traditonal HD, Win 7 sys installed on RAID by mistake
Didnt think that was relevant to solve your prob?

FWIW, Win 7 needs boot files to be on a prim partition thats active.
The boot have to be on "C", they cant be on the sys reserved 100mb hidden no drive latter partition. But if you install with no reserved, and you only have one O/S, at boot Win will make it "C", no matter where it is and that partition whatever it was must be actve and contain bootmgr

If you are the type of person who is constantly changing things you should never make any extended/logicals, only primaries - 4 allowed per HDD
Based on tthis new info, and the fact no repairing options were allowed means you lost path continuity to active, or lost active designation for Win 7 in RAID. I still dont know the full story here, but you may also have created an active on each HDD, which means boot order is critical. In essence - your PC suffers from "confusion", not hardware breakdown

if it still doesnt work with what you are doing, you will have to study your disk management graphic - from another PC HDD if needed
For simpiest example here - the hidden reserved is primary/active with sys. The O/S is on "C" also primary not active with the boot files

vxfce8.jpg


Over and out!
 
Last edited:
bankster55 said:
Thats a whole lot of information you left out of your first post
Two logicals, plus RAID array, both SSD and traditonal HD, Win 7 sys installed on RAID by mistake
Didnt think that was relevant to solve your prob?
Click to expand...

Trust me, I didn't know that was the case until I started digging into the issues. It's been over 13 months since I did the install.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top