Windows 7 Home Premium White Cursor Reboot Loop

[ClickRight]

Hi All,

I've got a PC in running Windows 7 Home Premium 64-bit. It refuses to boot. Here's what happens:

1. PC POSTS
2. Windows 7 Loading Screen Appears and Goes By
3. White mouse cursor loads (KSOD)
4. PC hangs at above said state for about 1 minute, then reboots (During this time there is a BUNCH of HD activity).

During the time the cursor is up, I cannot Ctrl+Alt+Del, Ctrl+shift+ESC, nothing! It appears to happen before the login screen. Safe mode = Same thing. Disabling automatic reboot does nothing either, so I never see a blue screen.

Here's what I've tried

1. Chkdsk: no errors found
2. Last known good config: Nope
3. System restore: 1 restore point in June: Restore: Same issue
4. Offline SFC: no issues found
5. Manual Registry restore to the point in June: Same issue
6. Offline Malware scan (MBAM): Clean
7. D7 Malware Scan: nothing suspicious
8. Have tried to look at event logs but they show no activity since the 9th (all looks normal)

As always, a full diag has been run on the MB/CPU/RAM/HDD. Googling seems to turn up some results about this happening after a Vista to 7 upgrade (this machine came preloaded with 7) and some threads about updates (checking windowsupdate.log I see no recent updates installed).

This is the first time I've seen such an issue and not have a registry restore (manual or system restore) repair it. Has anybody seen this before. Has it been resolvable without a reinstall?

 

[ComputerRepairTech]

white cursor moveable or no?

I can't say i've seen that issue before.

Edit: any bad sectors?

 

[ClickRight]

Yes, the mouse cursor is moveable. No bad sectors on the HD, first thing we checked

 

[RockIT Man]

Have you tried booting to a live CD/USB? I've had great success with Kaspersky Rescue Disk 10. You'll want to make sure to update the definitions before running.

 

[NYJimbo]

Disabling automatic reboot does nothing either, so I never see a blue screen.

Does disabling still cause a reboot or does it just sit with a black screen as if its BSOD but with no display ? This is important.

 

[ClickRight]

Does disabling still cause a reboot or does it just sit with a black screen as if its BSOD but with no display ? This is important.

Disabling still causes a reboot.

 

[NYJimbo]

We just had the same thing but right after a install of SP2 to Vista. Same exact issue but if we told it not to reboot it would do all the activity and then sit there as if it was in fact BSODing but not showing it. We did the 10,000 possible fixes but ended up doing a nuke and pave.

 

[Vicenarian]

Can you boot into an offline environment and check autorun programs there? Might be something executing at boot? Also check for MBR rootkits, and shell hijacks?

 

[ClickRight]

Can you boot into an offline environment and check autorun programs there? Might be something executing at boot? Also check for MBR rootkits, and shell hijacks?

Thanks, yes I have done so with no success. I'm afraid those will be a N & P Job

 

[ArtemusComputerTechnology]

Thanks, yes I have done so with no success. I'm afraid those will be a N & P Job

Never had this issue before. Sounds strange to a full diagnostic and nothing looks suspicious and all is working from a full and complete diagnostic. I would try some more steps then if so, outsource the job. If you want.

 

[NYJimbo]

Thanks, yes I have done so with no success. I'm afraid those will be a N & P Job

There are just too many times we have to end up doing a N&P because of Microsoft leaving us no other choice.

I think most real techs would gladly chase down a BSOD or some other error or warning if we knew that a handful of fixes would take care of any specific problem, but in situations like this you can work on a machine for days and do countless "fixes" and get nowhere.

To this day I still see all kinds of total loss situations on installs of SP1 or SP2 on Vista and I still cannot come up with a fool proof method to resolve them all. Some fix works perfectly on one machine and the next almost identical machine does not respond to that fix.

Microsoft is responsible for this, they know what is going on in their code and they know how to get the info to fix it but their operating systems are such an enormous mess of layers of crap and so many fixes that only work for some situations that their favorite response to something like this is "A re-install of windows is the SOLUTION to this problem". Makes me sick.

 

[JasonLV]

My sentiments Exactly!! Your spot on with Microsoft. Were techs we want to know how to correct the issue but left with Nuke and Pave. I've had this happen with Vista the most, couldn't spend anymore time attempting to get the answer so off to N & P.

Best of Luck!!