Consistent reboot after splash screen...?

Jester5510

New Member
Reaction score
0
I've seen a ton of issues in my day, but oddly enough, I've never seen this one.

I contract for a company where we custom built 80% of their computers. The majority are rock solid and have been. This one employee's computer has been great for months, but recently started rebooting after the splash screen and before the login screen.

This employee is rather tech savvy and swears he has not installed any software, changed anything, etc. He came in one morning and it was down. He booted it up and the rebooting started.

We can't get into safe mode (reboot). Can't get into Windows 7 Pro proper (reboot). Startup repair shows zero errors. CHKDSK showed a couple of errors and were repaired. Second CHKDSK showed no errors. HDTUNE showed no further errors. I did the RAM dance (just in case), including replacement RAM, still the same issue.

I doubt it's a PSU issue since it happens at the exact same point every power cycle. My first thought was the errors that CHKDSK corrected could have been a portion of the OS that was corrupted and that could be the issue. I'm not leaning towards any MBR issues since it goes through the entire boot sequence until the login screen.

I'm going back in tomorrow with the following plan of action:

1) Windows 7 Pro disc system restore to the last good point now that CHKDSK has repaired the few issues.
2) Inserting the HD into a spare setup they have (exact same HW config) in case it IS a HW problem (mobo, PSU).


Anybody ever dealt with something like this? I want to be aware of all possibilities before I go in tomorrow so I can plan accordingly to fix this.
 
What command did you run with Chkdsk?

When I get problems like this where I cannot boot into the operating system in any mode I will use a live disk version of Spinrite scan at Level 2.

I also use the version of Chkdsk found in the Active@Boot Disk live cd. These programs will fix errors that Windows Chkdsk miss or can't fix.
 
This employee is rather tech savvy and swears he has not installed any software, changed anything, etc.

Tech savvy people are the kind of people that NEVER do anything to their computers ;)

Sounds Driver to me, possibly related to an anti virus issue. I'd boot it from a live CD of some sort just to make sure it's doesn't happen there. I'd then use that live CD to Check out what drivers are loading in SafeMode and disable thoes that are NOT default basic Windows drivers. Then Try to restart it insafe mode.

Just curious, is it using onboard Video?
 
What command did you run with Chkdsk?

When I get problems like this where I cannot boot into the operating system in any mode I will use a live disk version of Spinrite scan at Level 2.

I also use the version of Chkdsk found in the Active@Boot Disk live cd. These programs will fix errors that Windows Chkdsk miss or can't fix.

chkdsk /R

I'll give that other CHKDSK a shot as well.

Forgot to finish my thought... Try running sfc /scannow from a command prompt.

No errors, no BSOD, just a random reboot. I didn't even think of sfc /scannow. Way too long of a day, yesterday.

Tech savvy people are the kind of people that NEVER do anything to their computers ;)

Sounds Driver to me, possibly related to an anti virus issue. I'd boot it from a live CD of some sort just to make sure it's doesn't happen there. I'd then use that live CD to Check out what drivers are loading in SafeMode and disable thoes that are NOT default basic Windows drivers. Then Try to restart it insafe mode.

Just curious, is it using onboard Video?

Haha, no joke. Anyway, very good idea on the driver disabling via the boot CD. Going to give that a shot as well. Thanks!
 
Update:

So, I ran sfc /scannow, no issues. Ran a deeper CHKDSK, nothing. So I decided to minimize downtime and just re-install on a new HD, since 100% of the saved work is on a network drive. Well, that went fine. I installed every program, rebooted one last time, and got the dreaded blinking cursor after post. Went into command prompt and attempted a bootrec /fixMBR and no luck. Tried /rebuildbcd and "element not found". This was a brand new drive. So, I plugged the drive into a spare backup machine we had, installed everything again and it was all good.

My best guess is that the drive controller was having issues on the MB. We'd had a history of this certain model/brand of MB having serious, random issues. So far so good on the new MB.

Every day you learn something new.
 
Good that the customer is happy in the end.... but weird you got it all setup, programs installed before it went south again. Glad it worked out for ya.
 
You didn't mention if you disabled auto-restart on blue screens, or if there were any crash dumps created before the reboot and what an analysis of them showed.

I'm also not sure what the RAM dance is, but when onsite I prefer to directly swap questionable RAM with known good.

Just some things to keep in mind for the future I guess.
 
Back
Top