Constant BSODs, going mental. Any advice?
- Thread starter Relish
- Start date
I checked my network drivers for Intel and they are up to date
Are there any drivers from the drivers list that you think need updating? Also attached the memory dump here
MEMORY DUMP#3:
Are there any drivers from the drivers list that you think need updating? Also attached the memory dump here
MEMORY DUMP#3:
ubuysa
The BSOD Doctor
Have you checked that the AMD chipset drivers are up to date using the tool I linked earlier?I checked my network drivers for Intel and they are up to date
Are there any drivers from the drivers list that you think need updating? Also attached the memory dump here
MEMORY DUMP#3:
MEMORYDUMP#4: https://1drv.ms/u/s!AmWYpHRGqNmJgP8vAjfZzOX5oEnz5g?e=cqx8em
AHH this is so frustrating. I've been at it for two days trying to watch youtube videos for fixes, messaging people, doing my own research on it but these bluescreens just wont go away 🙃
AHH this is so frustrating. I've been at it for two days trying to watch youtube videos for fixes, messaging people, doing my own research on it but these bluescreens just wont go away 🙃
ubuysa
The BSOD Doctor
The third dump is a DRIVER_IRQL_NOT_LESS_OR_EQUAL, which as you might expect is always a driver issue.
The stack trace does show a network operation in progress and we see a TCP send function call (tcpip!TcpEnqueueTcbSend+0x3dc) which is followed immediately by a page fault, and that's why you got the BSOD.
In the driver calls list for the active thread (which was part of the RiotClientServices.exe process) are two driver errors.....
This one is for vgk.sys, which is part of the Riot Vanguard game security software...
And this one is nvlddmkm.sys, the Nvidia graphics driver...
There is no way to tell which one occurred first, however the vgk.sys error is at a higher address than the nvlddmkm.sys error and since the kernel address space grows downwards that would suggest that the vgk.sys error occurred first and the nvlddmkm.sys error was probably a symptom of that.
I'm downloading your fourth dump now but already I think you'd be wise to do two things:
Thing1: Download Memtest and run that overnight on your RAM. Let it complete all four iterations of the 13 tests. There's no particular reason to suscpet RAM but you're getting a range of driver error and it's thus wise to check your RAM.
Thing2: Unplug all hardware except monitor, mouse and keyboard. Clean install Windows, delete all UEFI partitions, allow Windows Update to install all drivers that it can, run the AMD driver tool to install the AMD chipset drivers, then manually install the Nvidia driver downloaded from the Nvidia website. That will give you the cleanest operating system platform you can get, so your goal now is to not pollute it with stuff you don't absolutely need to test it. Install the absolute minimum software you can to test the PC.
You're trying to make it BSOD with a pristine operating system platform, if you can then we'll know it's a hardware issue. But the more software you install and the more you pollute your pristine operating system the less certain you can be whether your problem is hardware or software. It's also vital to get these third party drivers out of play so that we're dealing as far as possible with natice WIndows drivers.
Reinstalling now is a troubleshooting process, not restoring your system. If you don't absolutely definitely need it to test the PC then don;t install it. Keep it clean.
The stack trace does show a network operation in progress and we see a TCP send function call (tcpip!TcpEnqueueTcbSend+0x3dc) which is followed immediately by a page fault, and that's why you got the BSOD.
In the driver calls list for the active thread (which was part of the RiotClientServices.exe process) are two driver errors.....
This one is for vgk.sys, which is part of the Riot Vanguard game security software...
Code:
ffffc10c`ebdf01c8 fffff801`6769031dUnable to load image \??\C:\Program Files\Riot Vanguard\vgk.sys, Win32 error 0n2
vgk+0x1031dAnd this one is nvlddmkm.sys, the Nvidia graphics driver...
Code:
ffffc10c`ebdecaf8 fffff801`6c37dd12Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3784df9edffd3314\nvlddmkm.sys, Win32 error 0n2
nvlddmkm+0x17dd12There is no way to tell which one occurred first, however the vgk.sys error is at a higher address than the nvlddmkm.sys error and since the kernel address space grows downwards that would suggest that the vgk.sys error occurred first and the nvlddmkm.sys error was probably a symptom of that.
I'm downloading your fourth dump now but already I think you'd be wise to do two things:
Thing1: Download Memtest and run that overnight on your RAM. Let it complete all four iterations of the 13 tests. There's no particular reason to suscpet RAM but you're getting a range of driver error and it's thus wise to check your RAM.
Thing2: Unplug all hardware except monitor, mouse and keyboard. Clean install Windows, delete all UEFI partitions, allow Windows Update to install all drivers that it can, run the AMD driver tool to install the AMD chipset drivers, then manually install the Nvidia driver downloaded from the Nvidia website. That will give you the cleanest operating system platform you can get, so your goal now is to not pollute it with stuff you don't absolutely need to test it. Install the absolute minimum software you can to test the PC.
You're trying to make it BSOD with a pristine operating system platform, if you can then we'll know it's a hardware issue. But the more software you install and the more you pollute your pristine operating system the less certain you can be whether your problem is hardware or software. It's also vital to get these third party drivers out of play so that we're dealing as far as possible with natice WIndows drivers.
Reinstalling now is a troubleshooting process, not restoring your system. If you don't absolutely definitely need it to test the PC then don;t install it. Keep it clean.
ubuysa
The BSOD Doctor
The fourth dump is another KERNEL_SECURITY_CHECK_FAILURE, again for a list entry failure due to a stack buffer overrun. That's pretty much certain to be a driver error.
The process in control again was chrome.exe (when you do a reinstall do not install Chrome). The stack trace for the active thread shows a security check failure almost as soon as the kernel is entered.
In the list of driver calls for the active thread is, once again, an error for nvlddmkm.sys...
There seems to be a problem either with your Nvidia graphics driver, with your grtaphics card itself, or with some of the other software you have that interacts with the graphics driver. That's why it's vital to start afresh and keep the newly installed system as clean as you can.
The process in control again was chrome.exe (when you do a reinstall do not install Chrome). The stack trace for the active thread shows a security check failure almost as soon as the kernel is entered.
In the list of driver calls for the active thread is, once again, an error for nvlddmkm.sys...
Code:
fffff101`62bc31f8 fffff802`746fdd12Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3784df9edffd3314\nvlddmkm.sys, Win32 error 0n2
nvlddmkm+0x17dd12There seems to be a problem either with your Nvidia graphics driver, with your grtaphics card itself, or with some of the other software you have that interacts with the graphics driver. That's why it's vital to start afresh and keep the newly installed system as clean as you can.
ubuysa
The BSOD Doctor
Great.
Download the Media Creation Tool and use that to make a bootable (8GB min) USB stick with the latest Windows install files.
Boot that USB stick and select a Custom Install.
Delete all four UEFI partitions (MSR reserved, System EFI, Recovery, and Primary (Windows)).
Select the unallocated space that results and click the Next button. The installer will do the rest.
Once the Windows setup has completed run Windows Update repeatedly, even across reboots, until no more updates are found.
Run the AMD Driver & Support tool to install the chipset drivers.
Download the latest graphics driver for your card and OS from the Nvidia website and install it manually. DO NOT select any Nvidia audio components.
See whether you can make it BSOD in that state. If not, install one game or one item of software that has made it BSOD in the past. You want to install the very minimum software you need to get it to BSOD.
I would leave that off for a while.
ubuysa
The BSOD Doctor
That's an very interesting and potentially useful observation. I've no idea what it means but it's something to note....
memtest can back clean but I got a big issue now.
I tried to reinstall windows using the USB but it won't let me finish the set up without BSODs. It's probably BSOD like 25 times now as I tried to complete the windows set up, I'm just stuck in a loop.
Currently I'm trying to reset windows through the OS but this is also causing BSODs through setup. WTF is going on, how is it blue screening mid set up?
I tried to reinstall windows using the USB but it won't let me finish the set up without BSODs. It's probably BSOD like 25 times now as I tried to complete the windows set up, I'm just stuck in a loop.
Currently I'm trying to reset windows through the OS but this is also causing BSODs through setup. WTF is going on, how is it blue screening mid set up?
ubuysa
The BSOD Doctor
That's not much fun.
That does kinda sound like hardware now then. I would suggest you pop all cards out and reinsert them firmly. Do the same with the RAM, though here I'd suggest you run just one stick and leave one out. If it BSODs on installation then swap the RAM sticks and try it again. I know Memtest ran clean but it can only show that your RAM is faulty, it can't ever show that it's good.
It's worth checking all cables and connectors, especially ones going to the motherboard.
What stop codes are you getting with the BSODs?
ubuysa
The BSOD Doctor
The stop code would have been KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION and that's not a common hardware BSOD.
I would suggest that you make up another USB stick. In situations like this I'd recommend a new USB stick (8GB min) and using a PC that you know is stable to download the Windows install files. It could well be that your installation USB stick is corrupt somehow. Given that stop code corrupted installation files makes more sense than a hardware failure.
I would suggest that you make up another USB stick. In situations like this I'd recommend a new USB stick (8GB min) and using a PC that you know is stable to download the Windows install files. It could well be that your installation USB stick is corrupt somehow. Given that stop code corrupted installation files makes more sense than a hardware failure.
ubuysa
The BSOD Doctor
I doubt it, the specs say 8GB min. It rather sounds as though that stick may be flaky?