Main Forum > Tweaking.com Support & Help

Scan Interrupted, Can No Longer Boot to Visible Logon Screen

<< < (7/11) > >>

lmitchell:
No I didn't. I turned it off and unplugged it, as well as my Logitech mouse receiver. I've only just now plugged it in to copy files with Linux to clear the partition I had originally meant to use for the OS drive backup.

I made another attempt post chkdsk to boot prior to inserting and booting off the Linux disk. Still the same - black screen and mouse cursor.

The one time Startup Repair ran without reporting "no errors" it siad there was a "bad driver". I have to wonder since when the Safe Mode drivers load it stops at classpnp.sys (that may be normal for all I know). Once it went one driver further. I looked up the driver and it was a Toolwiz driver. I had a Toolwiz app installed but not one associated with that particular driver, which should not have been loading in safe mode. It may have been a fluke occurence. I ran multiple malware and virus scans earlier this week (5 or 6 different programs, including malwarebytes), before doing TWR. Everything came back clean.

Boggin:
I saw that you mentioned that you had tried LKGC from the advanced boot options - can you also get Safe Mode with or without Networking to see the screen using the on board VGA graphics ?

If you can get Safe Mode with Command Prompt or just Safe Mode to access the cmd prompt, enter eventvwr

I was in error before because that cmd isn't recognized from the recovery environment cmd prompt.

Where you would normally see Critical, Error etc. and clicking on each, the resultant pane may be empty but will populate when you click on View All Instances of This Event in the lower right pane.

We need to see what it has been recording.

If you can get Safe Mode with Networking then you can download Blue Screen View which will analyse the Memory Dump files as Windows doesn't have a default program to read those.

http://www.nirsoft.net/utils/blue_screen_view.html

If the cause is because of a driver conflict/corruption then the methods to repair the MBR may not work.

If you can access the cmd prompt without going into the recovery environment, I'm not sure if the cmd msinfo32 would work but there you can expand Components/Problem Devices to see if it snags anything.

If you can navigate using the cmd prompt then you may also be able to get devmgmt.msc to see if anything has an alert in Device Manager.

lmitchell:
Its the same with networking, VGA and all the other safemode options, except the black screen occurs after the driver loading list. I went through every option on the page. Alway the sense that something is happening or there, just overlain with a black screen.

I'll back out of Linux now, unplug the hub and anything else, try all options again and report back soon.

lmitchell:
Also, I already have Blue Screen View installed. I think I have the entire Nirsoft suite installed, but never needed to use it for anything serious.

lmitchell:
Regular start and standard Safe Mode both went through to black screen with mouse cursor.

Safe Mode with Networking and Safe Mode with Command Prompt are both hanging on the Loading Windows Files page at classpnp.sys. I hope this is progress and not degradation.

I gave the former about 3 minutes before interrupting it to try the nest option. I'm going to interrupt the latter now and try VGA, etc just to eliminate the other scenarios.

Navigation

[0] Message Index

[#] Next page

[*] Previous page