changing the letter worked. time to run the testHi Bawb,
these links have a couple of solutions:
Link Removed
Link Removed
Alright so. I got the mini dumps from stressing the drivers. PC blue screened almost instantly as the windows load screen started. So I assume that the it knows which driver was causing the issue.Ok Bawb, hope all goes well with the test.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2003, ffffe0005a38e108, fffff80095b80228, ffffd001135f4620}
Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
Followup: MachineOwnerIf not try running it again but this time without the MS drivers included. Here's the guide again:Select all the drivers on this screen, except those that say Microsoft Corporation under Provider. It’s very unlikely a Microsoft driver is causing the issue.
I did exclude the microsoft drivers. So now Ill try each ram stick separatelyHi Bawb,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {2003, ffffe0005a38e108, fffff80095b80228, ffffd001135f4620} Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c ) Followup: MachineOwner
when you ran the verifier did you follow the guide particularly this bit:
If not try running it again but this time without the MS drivers included. Here's the guide again:
How do I fix a Blue Screen in Windows using Driver Verifier?
Your other dump files were for memory corruption. If the verfier turns up nothing again try running on just one stick of RAM at a time. Sometimes even Memtest86 can miss errors so another way to test is to run on one stick. If you get a bsod swap for another making sure you make a note of which is which. Keep doing this until you find a stick which doesn't bsod then you know which sticks are bad.
I ran the test one stick of the time even trying the old sticks that I had. Same result for everything, fast blue screens. Attached more current dump files.Hi Bawb,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {2003, ffffe0005a38e108, fffff80095b80228, ffffd001135f4620} Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c ) Followup: MachineOwner
when you ran the verifier did you follow the guide particularly this bit:
If not try running it again but this time without the MS drivers included. Here's the guide again:
How do I fix a Blue Screen in Windows using Driver Verifier?
Your other dump files were for memory corruption. If the verfier turns up nothing again try running on just one stick of RAM at a time. Sometimes even Memtest86 can miss errors so another way to test is to run on one stick. If you get a bsod swap for another making sure you make a note of which is which. Keep doing this until you find a stick which doesn't bsod then you know which sticks are bad.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5002, fffff58010804000, 1b51, 800001b52ffffffe}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+154a4 )
Followup: MachineOwnerHi,Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5002, fffff58010804000, 1b51, 800001b52ffffffe} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+154a4 ) Followup: MachineOwner
the above bugcheck is for memory management although this doesn't always mean you have bad RAM. So I took another look through your driver stack and found some interesting results:
AsIO.sys Tue Aug 24 02:53:02 2010: Asus PCProbe Utility. This is too old for Windows 10 really and needs either removing or updating.
MpKsl89da5820.sys Wed May 20 02:50:37 2015: Microsoft Security essentials? If so please remove and just use the onboard Defender.
zamguard64.sys Mon Dec 14 10:13:23 2015: Anti Malware uninstall to test.
So when you say they don't exist do you mean you've looked in the remove programs section?I cant remove any of those things as it seems like they dont even exsist
yeah and the uninstall programs as well. I also checked CCleanerSo when you say they don't exist do you mean you've looked in the remove programs section?
The thing of it is. I highly doubt it has anything to the windows. Ive reinstalled windows a few times and more then that Ive upgraded to an ssd and swapped out the storage drive. So I highly doubt its a software issue.Hi Please except this reply as it is intended. Not to criticize anyone. I mean no disrespect to anyone here on the forum.
If this offends anyone, please delete this reply. I will understand.
IMHO there comes a time to bite the bullet and reinstall the OS when you have tried to fix BSOD and not found the solution!
Reinstall Windows: Reinstalling Windows is the nuclear option. It will blow away your existing system software, replacing it with a fresh Windows system. If your computer continues to blue screen after this, you likely have a hardware problem.