Driver PNP Watchdog BSOD - Cannot even Boot to Recovery.

Thank-you very much for your reply Macboatmaster - it is most appreciated.
Especially as you breakdown various elements - I think it's very much a game of deduction now.

I'll answer each point for clarity, and to expand on my actions thus far:



I can't seem to get my hands on a Win10DVD ISO, just to see if it Boots from Disk rather than Hard-Drive or USB; but will keep trying.
That is not a problem presuming you have another computer to make it
https://www.microsoft.com/en-gb/soft...load/windows10
as here
Follow these steps to create installation media (USB flash drive or DVD) you can use to install a new copy of Windows 10, perform a clean installation, or reinstall Windows 10.
under heading using tool to create installation media



Yes, I know how to create one using the tool you specify - it's the same method I used to create the Boot USB. I was able to do this on one of my laptops.
Unfortunately, the only DVD-write capacity I have.....is on the computer that won't boot.
I've asked some friends who also may have capability for this to prepare one for me - hoping for some feedback in the coming days.
*I have doubts that this will work anyway, however, I must try in order to rule in/out Boot via DVD.


2. I know you have listed many aspects of what you have tried
This one
However, I CAN Boot into Ubuntu (Try part) and access my files. So it seems its some sort of Windows Driver issue, as the error code suggests.
3. suggests although you say the windows installation usb is good, that it is not, as that does not rely on anything of the present installation to do with booting from it, as of course you could boot from that, without any installed windows .




Here, I don't think it proves that the Win10USB is good as such, as Ubuntu is a different OS completely (operating at a lower level, thus not using Win drivers?). However, Booting from this Win10USB on my laptop functions correctly - I have access to menu options. This I think proves the Win10USB if nothing else. I needed to check this to be sure, of course, elsewhere than my broken PC.
Booting into Ubuntu from USB is an unknown entity to me - I've not used any Linux for over 30 years (yes I'm old!). However, being able to do so, I believe, would indicate that it is not dependent upon Windows drivers, and as such could be a reason why it works.
*In Ubuntu I'm also able to navigate files in my disk-drives, which suggests the disk-drives themselves are not 'dead'. **But at 12 years old, replacement is certainly recommended.


4. What is shown for the drives in the BIOS/UEFI GUI and what is shown as the boot order please.


I replaced my CMOS battery as a matter of course during this investigation; and on the motherboard backpanel is a BIOS reset button.
I used this to reset BIOS and one by one go through the tabs to ensure everything seemed 'logical' from my knowledge.
The Boot tab, as you point out, is the most interesting one:
AHCI was the default, and the one I used. I did also try reverting to (legacy as I understand it?) IDE. Same issue with both options selected.
I disabled 'Fast-Boot' as was recommended in several threads; I have option for UEFI and Legacy, for which again, I've tried both, and combinations of the two possibilities. In addition, I've tried all combinations with Secure Boot option too. All same issue, BSOD as reported, and unable to gain access to recovery.


5.
I've bought a new hard-drive (my system is old and needs a new build from scratch with new components), but nope, same issue with the new (blank) hard-drive.
This suggests it maybe a drive controller error in BIOS - what happens if you try the windows USB without the drive in.
It is just possible that a BIOS has it set incorrectly
Wrong SATA Controller Settings in BIOS: SATA controller has many modes like IDE, AHCI etc. If the SATA controller mode is wrongly configured in the BIOS, then it can trigger this error.


I kind of bought the new hard-drive with three concepts in mind:
a) It's newer, and if I can successfully get my PC to work, this will then become my new C: replacing the much older, original one.
b) It is 2TB, thus twice the size; important for using modern gaming with Steam.
c) In the event I need to build a new PC from scratch (on my mind anyway, given future funding), it will form my F: for storing music and pictures only instead; while faster new SSD's and legacy DVD/Blu-Ray will be the other drives.
Drive controller is what is also on my mind, perhaps corrupted. I've removed each and all hard-drives, and still see the same issue if disk(s) are connected or not.....it seems to make no difference if they are present or otherwise.
A corrupted Windows drive controller driver might also explain why Ubuntu can see my disks, and not Windows(?).
Having no hard-drives in, and Booting from Win10USB gives the same result (BSOD) as if they were present. Always the same issue.
This includes when using WinPE USB's.
When in BIOS, and Win10 (or Ubuntu USB) is inserted - I get two entries in BIOS UEFI-USBname and (just) USBname.....both give the same outcome - BSOD.


Once again, thanks for your input, its much appreciated.

The biggest take-away I can deduce from this is: No matter what I do, I always get the same BSOD, except when Booting from USB to Ubuntu.

If you have any further thoughts, or are aware of a method to check Drive Controller Driver without actually getting into Recovery mode (as I can't), that would be great.

Hi Macboatmaster,

Yes, time and date in BIOS are correct; Interesting how this is, as I replaced the battery and didn't have to manually add this.

Yes, the '3 power-cycles' method is what I first tried to get into some sort of Recovery position. This never happens, only BSOD with Driver PNP Watchdog issue.

The error seems to be consistent; no matter what I try, with anything Win based. Only doesn't do this, when Booting into Ubuntu (Try) USB.

1. Have you installed any new hardware - particularly something that is Plug and play.

I moved 2 RAM sticks. I actually had all 4 x 8GB sticks already installed, but system was reporting just 16GB total. Looking at the manual, I can see why - so I moved them, while I was inside to replace the CMOS battery.
BIOS counts all 32GB now, and reports 'OK' on them. Do you think simply moving 2 sticks might cause an issue? System was off, obviously, when I moved them, so no corruption should be possible. BIOS says all is 'OK' in a report, and running a memory test while in Ubuntu returned no errors.


2. Are you connected hard wired - ethernet or wirelessly.

Only with WiFi. This is also a USB stick, as motherboard isn't WiFi native. I've tried with this both in and out.


3. Just to be clear - please, how many actual discs - drives are in the computer -apart from the optical media drive.

I have 4 hard-drives - 2 x SATA3 and 2 x SATA2. C: is primary SATA3.
I have 3 optical-drives - 1 x BluRay and 2 x DVD writer.

During testing to try and get to Boot, I have removed all except C: and all, including C:

I've also removed joysticks, pedals, and anything else connected.

Top of the morning to you Macboatmaster! Or afternoon as it is here now in Barcelona.


What was it that was apparently causing this as you say
Looking at the manual, I can see why


When I first built my PC, Christmas 2012, I read the manual while working on it. I correctly used the primary RAM ports for the first two sticks; Then I just stuck with the colour coding on the motherboard for the 2nd 2 sticks. This was an error - in order to get four sticks to work out of the 8 slots available, they must be used in the correct order. I just assumed, and was wrong. I corrected that this week by moving the 2nd set of sticks. Which you point out may be problematic.
I kind of get that it was a physical change I did to my PC, thus, is a potential reason for an issue. Do you have any deeper thoughts on why, as my system says memory is OK. Definately worth a go though, for sure. Though it is a bit involved as it means I need to remove CPU heat-sink again to get access. I'll re-check the manual to check which RAM port order again.


My recommend is to
1. Leave the wireless usb disconnected
2. Connect hard wired and try that

If that still will not boot to windows without the BSOD - see if will boot to the 10 installation usb.
==============
If that is no good I recommend you shut down, disconnect power lead to tower
HOLD DOWN power button for 20 seconds.
That will discharge all remaining voltage across the board

Take out the ram and try with just ONE STICK of ram in D1 which is second slot from left of dimms nearest to I/O plate I think



I don't think I have a cable for Ethernet, so will just leave both connectivity off. I don't need any internet connection for Booting anyway - can restore WiFi once 'in'.
I'll follow the remainder of your instruction, hopefully, later today if I get time, and advise.