Which might be relative harmless to move around.
My bootlog shows cdrom.sys to be loaded after classPNP and the AVG-sys files. So the general answer is 'it depends on which driver is causing the problems. If windows needs that driver and you remove it it will fail to boot succesfully. a liveCD, and file or registry editing on the disk might be needed).Ģ.) Does removing the offending driver (once I know what that is) from sys32/drivers all I have to do to move around it?
However since your windows will not even boot in safe mode this might be hard to set. You can also mark the boot log option, which will write a log to %systemroot%\nbtlog.txt (usually C:\Windows\ntbtlog.txt). This displays a list of loaded drivers during windows startup. If you working computer then you can run msconfig, select the 'boot' tab and mark OS boot information. Unless you also installed AVG this seems to be a dead end.įor the record (or rather, for others who might find this post later) Without those classPNP.sys would have been the last one. On my desktop (also win7-amd64), with OS boot information enabled the last displayed loaded drivers are: It usually is, unless classpnp.sys is the last driver loaded. that would be very much appreciated.1.) Does that mean that the driver that is failing is the one loading after classpnp.sys? I have tried looking on Microsoft help center and tried Googleing my problem, but found nothing useful. Here is the start of the log: Startup Repair diagnosis and repair logĪnd whole load of successful tests then the last part Root cause found:ĪCLs on file C:\Windows\system32\drivers\USBSTOR.SYS are not proper. I restarted it a few times and nothing happened, so I ran the Startup Repair tool. I just restarted my computer and for some reason it gets stuck on the logo screen.
0 kommentar(er)
