Sign in with
Sign up | Sign in
Your question

Cannot boot consistently, cannot locate the problem

Tags:
  • Windows 7
  • Blue Screen
  • Boot
Last response: in Windows 7
Share
September 15, 2014 2:22:24 PM

Hello all,

I've been having this problem for some time now. Running Windows 7 on a fairly-new build (~1.5 years). The PC crashes overnight, then won't boot, coming up to a bsod during the windows boot logo. This has happened about 4 times over the course of a year. Each previous time I wiped and did a clean install of Windows 7, and each time it crashes, it is the same error on the bsod.

The strange thing is, this time I have gotten it to boot back into windows, seemingly at random. It boots in fine, no errors, everything runs smoothly, and then will bsod overnight. Today I got in, and went to scan the HDD using Seagate Seatools, and an error about logging popped up and then it immediately crashed. I am currently posting from a Linux LiveCD, and the system is working fine. This may point to an HDD issue? But I scanned the HDD just now using Ubuntu's disk utility, and it found no errors. I can also access the files on the HDD through Ubuntu without issues.

The BSOD error code is: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800030879C7)

I have tried:
Dskcheck: No errors.
sfc/ scannow: Nothing.
Windows Memory Diag: No errors.
Memtest86: No errors.
Malwarebytes: No malware detected.
Avast!: No viruses detected.
Seagate Seatools: Failed, crash.
Ubuntu disk utility "Smart Data & Self-Test" test on the HDD: Everything OK, no errors.
System Restore: Failed.
"Last Known Good Config": Still no boot.
Safe Mode: Usually no boot, can SOMETIMES get in, crashes after about 45 seconds
Start Windows Normally: Sometimes logs in, usually BSOD, sometimes PC reboots with no warning, all happen during windows boot logo.
Uninstalling recently installed and/or suspect programs: no help.
Moved RAM stick to other slots: seemed to have no effect.
Unplugged all peripherals aside from keyboard and mouse: no help.
Ubuntu Live CD: seems stable as of this posting.

I know the best method here is to test by swapping one part out at a time until the problem stops, but I don't have adequate replacement parts lying around to test with (and neither does the computer repair place I called today).

IF this keeps happening the same way each time, then it points to a hardware rather than a software issue, yes? And by the looks of it, the HDD could be to blame if Linux is running fine off the LiveCD using all the other parts in the tower. However, why, then, has the Linux disk utility found no errors with the HDD?

Should I use ubuntu to grab the updated BIOS file and flash it? Or is the BIOS version irrellevant in this situation?

Any suggestions on where to go from here? I could get my important stuff off of the HDD, wipe and reinstall Windows...again....but this error is just going to happen again 3 months from now and I'm ready to tear my hair out!

Maybe (I'm hoping) you've seen something like this before and can point me in the right direction. Thank you all.

If you require more info, please let me know.



System Specs:

Mobo: ASUS M5A97 LE R2.0
CPU: AMD Phenom II x4 955
RAM: Kingston Hyper X Blu 8GB 1600mhz (one stick) model khx16c10b1/8r
PSU: Rocket Fish 550w
HDD: SeaGate 500GB SATA "Barracuda" ST3500418AS (CC45) (Came from a Dell)
GFX: ATI Radeon HD 5770

More about : boot consistently locate problem

a b $ Windows 7
September 15, 2014 3:01:56 PM

I had problems with that memory too, make sure the voltage is set to at least 1.65v.

I would reset my cmos/bios first, then reconfigure it leaving out any overclocks (OC can bring this error too) and finally retest.
m
0
l
September 15, 2014 4:04:28 PM

Ok, by reset the CMOS/BIOS you mean reset it with the pins on the motherboard, right? Then reconfigure... i never overclocked the system, it is running at stock capacity.

I see many voltage settings, I'm not sure which one I should be looking at. Not sure I know how to alter the RAM voltage in ASUS UEFI BIOS?

And by retest, do you mean run all previous scans, or just try to boot into windows?
m
0
l
Related resources
a b $ Windows 7
September 17, 2014 6:39:50 PM

You either need to figure it out yourself or post up your motherboards make and model# so we can help you :-)
m
0
l
a b $ Windows 7
September 18, 2014 8:09:51 AM

bugcheck 0x7f with parameter 1= 8 is a double fault

If it is a driver problem I would be looking for having two drivers installed for the same device.

if you could post the memory .dmp file
or even better: change your memory dump type from minidump to kernel dump,
run verifier.exe and set debugging flags
http://www.sevenforums.com/crash-lockup-debug-how/65331...
reboot and run until you get a bugcheck, then post the new memory .dmp file on a public server and I can take a quick look in the windows debugger.


m
0
l
September 24, 2014 12:49:20 PM

popatim said:
I had problems with that memory too, make sure the voltage is set to at least 1.65v.

I would reset my cmos/bios first, then reconfigure it leaving out any overclocks (OC can bring this error too) and finally retest.


popatim said:
You either need to figure it out yourself or post up your motherboards make and model# so we can help you :-)


I have my motherboard model in my original post. ASUS M5A97 LE R 2.0


I can now get it to boot into windows if i reset the CMOS, but the crash is still happening. Sometimes during a reboot, sometimes while the computer is running.

I just switched yesterday from my HDD to a brand new Crucial SSD (cloned OS over), and the error came back. So we can rule out hard drive failure for sure, right?

I filled out the RMA form for the Kingston RAM, but the stick is discontinued so they can only "repair" it. How do you "repair" RAM??? If I can single RAM out as the problem for sure, I will just get a new stick or kit. I'm ready to bash my face into the Mobo, lol.

--------------------------------------------------------------------------------------------------------------------------------------------------------
johnbl said:
bugcheck 0x7f with parameter 1= 8 is a double fault

If it is a driver problem I would be looking for having two drivers installed for the same device.

if you could post the memory .dmp file
or even better: change your memory dump type from minidump to kernel dump,
run verifier.exe and set debugging flags
http://www.sevenforums.com/crash-lockup-debug-how/65331...
reboot and run until you get a bugcheck, then post the new memory .dmp file on a public server and I can take a quick look in the windows debugger.





Johnbl, thanks for offering to check that out, but I'm not sure how to post the memory .dmp file, nor do I know how to change from minidump to kernel dump. If you could please clarify.

Using the verifier.exe seems straightforward enough, but I don't want to do it until I know where I'll be grabbing the dump file from afterward.
m
0
l
a b $ Windows 7
September 24, 2014 4:13:47 PM

Run TurboV, it runs in windows, and can make real time voltage changes to your ram. Up to to the figures listed on the ram sticks which I beleive is 1.65v
m
0
l
September 25, 2014 8:48:35 AM

Okay, I'll have to triple check on the actual voltage before i do that, as the HyperX models all look similar but are slightly different in design, and have varying voltages listed (1.5 and 1.65). Is there a way to check this for sure? It doesn't have the specs on the stick itself.

EDIT: Just searched the part number on the Kingston website and found it; the 8GB single stick is listed at 1.5V, the 2x4GB kit is listed as 1.65V (I have the single stick). Alright, I'll bump it up using the ASUS software and see if it helps.

Update: I just checked in TurboV, the computer is giving it 1.5V. So it's already at the correct voltage.
m
0
l
October 4, 2014 5:50:31 PM

Update #2: I successfully RMA'd the memory, they gave me a blue FURY stick as a replacement. Flashed CMOS, booted successfully (except the items in my taskbar tray on the bottom right were bugged and invisible....). After restarting the computer, I got the BSOD on boot again. Restarting from that point always resulted in BSOD.

However, unplugging the PC from wall for 15 seconds and then trying again has me booted successfully, app tray is working properly too.

So it's not the RAM, not the hard drive..... ugh. lost.
m
0
l
a b $ Windows 7
October 4, 2014 5:59:17 PM

you might want to google on how to post the memory dump. Otherwise it is just very hard to get a idea why your system is failing.
most often you will get a double fault when a kernel stack overflows. This would happen if too many drivers are servicing the same device.
(could happen if you have several virus scanners installed, or software that scans IO to other devices)
m
0
l
!