Win7 Laptop "classpnp.sys" hangs than bootloops.

Reaction score
811
Location
(Call me Jacob)
I have a Win7 laptop in store (at home for the night as of writing)

They tried to update the drivers from some web-ad (yay :mad:)

Now it just boot loops. when trying any safemode it hangs on the Classpnp.sys then bluescreens and restarts.

Can't do system restore, Windows Repair, Run in last good configuration. They all bootloop

Took the HDD out and ran hard disk sentinel on it. Still in good condition. Did the HP hardware diagnostics. everything passed and ran normal.

any ideas to try?
 
Download AVG Rescue Scanner (or one of the many others) and burn the .iso to a usb. (Rufus or Yumi etc)
Boot it up and run the virus scan with ALL options selected.
I suspect it has a malware infection.
I will try this tomorrow when I get back into work!
I honestly didn't even think about virus/malware. I was still assuming the driver installer he got just tried to install "all the drivers" and messed it up.

My brain usually turns off 45 minutes to closing -.-
 
I have a Win7 laptop in store (at home for the night as of writing)

They tried to update the drivers from some web-ad (yay :mad:)

Now it just boot loops. when trying any safemode it hangs on the Classpnp.sys then bluescreens and restarts.

Can't do system restore, Windows Repair, Run in last good configuration. They all bootloop

Took the HDD out and ran hard disk sentinel on it. Still in good condition. Did the HP hardware diagnostics. everything passed and ran normal.

any ideas to try?
Remember in safe mode, when you see all those files whizzing up the screen, the last one displayed is the last one that successfully executed. The one it's hanging on is the one you don't see. Yeah I know, they didn't think that through.
 
Remember in safe mode, when you see all those files whizzing up the screen, the last one displayed is the last one that successfully executed. The one it's hanging on is the one you don't see. Yeah I know, they didn't think that through.
Oh... See. I didn't know this.
So how do I find the one that is causing the problem? Assuming that @Barcelona s solution doesn't solve the problem?
 
I don't think i've ever done it but bluescreenview should be able to load up the crash dump from a slaved drive and then you can see what drivers were loaded into memory when it crashes.
 
Back
Top