30-09-2024, 12:32 PM
(30-09-2024, 12:03 PM)Wainuitech Wrote: Had the Odd case, mainly with DRIVER_PNP_WATCHDOG. This means ( from MS) This indicates that a driver has failed to complete a PnP operation within a specific time.
What I would normally do is look deeper at the logs, Event Viewer really doesn't tell you a lot ( most of the time)
In Search, type in Reli Open Reliability History -- There are often more details pointing to a problem.
Failing that, you need to read the dump files - If you are not too sure or do not have the actual Software to read them fully, download "Who Crashed" Download Here
The instructions on using Windows bebugger. Described here and HERE , These really get into the nitty-gritty - Details.
But Who Crashed will also give you a good idea and point to what actually crashed, it gives you someplace to start. They will tell you exactly what drivers crashed so something to look at.
Yeah event viewer is not overly helpful I find.
Given that this time its a fresh install of windows that failed to load, I will have to export the dump files for analysis on another computer since that this machine no longer can boot up.
Actually thinking about it, it might be easier to run who crashed off a windows PE boot disc, its very unusual for a BSOD to appear during a windows install nonetheless, it happens during the first bootup, right at the last percentage of configuring hardware while it spins around.
I tried installing with an older build as I was wondering if a windows update may have had something to do with it and still does the same thing.
Given that i used the same build to install windows with at the beginning with zero issues, it tells me something has happened with the hardware over this time.
Will be interesting what i find in the memory dumps anyway.