[SOLVED] Constant BSoD Errors

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
E

eridamskiy

Aug 16, 2020
23
1
15
How's everybody doing? I've had an insane amount of blue screens with different stop codes, ranging from IRQL codes to DPC Watchdog violation, APC Index mismatch, kernal security check failure. This is all on a ASUS computer that I bought in April. Everything should be working fine. I only have a couple of games installed on my computer(Valorant, League of Legends) along with every other peripheral software (iCue, Razer Central, Glorious PC) Regardless of everything I try, the BSoD just keep coming. Last night, i went into my PC and unplugged the Network cable from the adapter itself(I have a network adapter inside my pc), and it did nothing. I can post minidump files, just would like this issue to not be a hardware issue and result in me dishing out more money on this. Thank you in advance, good people!
 
Solution
Colif
I would like to say that if you had asked this time last year the reply time would have been much faster but I am just not being consistent this month.

esrv_svc.exe is part of intel drivers. It was victim in 1st crash, I was just curious.

all of them mention the fltmgr.sys in the stack. its Microsoft Windows file system filter manager and from memory its something to do with using default drivers to do actions via minifilter drivers. I don't understand it fully myself - https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/filter-manager-concepts

now if its minifilter drivers that could be the cause. you have a few
Oct 22 2012lvbflt64.sysLogitech USB Video Class Filter Driver...
Sort by date Sort by votes
How's everybody doing? I've had an insane amount of blue screens with different stop codes, ranging from IRQL codes to DPC Watchdog violation, APC Index mismatch, kernal security check failure. This is all on a ASUS computer that I bought in April. Everything should be working fine. I only have a couple of games installed on my computer(Valorant, League of Legends) along with every other peripheral software (iCue, Razer Central, Glorious PC) Regardless of everything I try, the BSoD just keep coming. Last night, i went into my PC and unplugged the Network cable from the adapter itself(I have a network adapter inside my pc), and it did nothing. I can post minidump files, just would like this issue to not be a hardware issue and result in me dishing out more money on this. I saw posts of other people and saw Rainbow 6 as a problem file but I don't have that installed. Thank you in advance, good people!
 
Upvote 0 Downvote
Sorry I posted this twice. Been trying to upload .dmp files to drive but it says either drive isn't reading the files or I dont have administrator privileges (which i just checked that I had)
 
Upvote 0 Downvote
https://drive.google.com/drive/folders/1ftj1-fs5IIcq5bxVN4NeQFpmkxF6Or2U?usp=sharing

running memtest right now on 4th pass so far found nothing, chkdsk and sfc i’ve done so many times before.
question, it created two boot files on the usb, does this mean that it’s one per ram? I have 2x 8gb sticks. I’m finishing up the first one right now, hopefully won’t have to go through another 3 hour scan, but if i do so be it. thanks again :)
 
Upvote 0 Downvote
Finished with the memtest, 0 errors.

https://drive.google.com/drive/folders/19cT5sNPofAez4csNQRctFpFqQqc-4kIt?usp=sharing

BSoD post memtest

I've loaded into driver verifier and got 1 crash so far. Checked the mini dump file and there was no dump for the blue screen i got. I'm now waiting on another crash to see if the same thing will happen again. Someone on windows forums told me not much was told from my minidumps except ram errors and now that i've done the memtest nothing makes sense. will update if i get another crash
 
Last edited:
Upvote 0 Downvote
Hi, I ran the dump file(s) through the debugger and got the following information: https://jsfiddle.net/2awctokg/show This link is anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:081620-15140-01.dmp (Aug 16 2020 - 10:46:53)
Bugcheck:DRIVER_PORTION_MUST_BE_NONPAGED (D3)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 32 Min(s), and 26 Sec(s)

File information:081620-14937-01.dmp (Aug 16 2020 - 11:24:41)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 42 Sec(s)

File information:081620-14890-01.dmp (Aug 16 2020 - 17:01:54)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: servicehost.ex)
Uptime:0 Day(s), 0 Hour(s), 10 Min(s), and 25 Sec(s)

File information:081620-14875-01.dmp (Aug 16 2020 - 11:58:30)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:ntkrnlmp.exe (Process: uihost.exe)
Uptime:0 Day(s), 0 Hour(s), 33 Min(s), and 20 Sec(s)

File information:081620-14843-01.dmp (Aug 16 2020 - 19:02:48)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:Npfs.SYS (Process: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 12 Min(s), and 25 Sec(s)

File information:081620-14812-01.dmp (Aug 16 2020 - 11:20:28)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 43 Sec(s)

File information:081620-14750-01.dmp (Aug 16 2020 - 11:03:15)
Bugcheck:APC_INDEX_MISMATCH (1)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 15 Min(s), and 53 Sec(s)

File information:081620-14687-01.dmp (Aug 16 2020 - 12:36:08)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 0 Hour(s), 26 Min(s), and 33 Sec(s)

File information:MEMORY.DMP (Aug 16 2020 - 11:24:41)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:amdppm.sys (Process: System)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 42 Sec(s)
System: ASUSTeK GA15DH

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
  • Like
Reactions: eridamskiy and PC Tailor
Upvote 0 Downvote
Repost as I added more info.

Only been able to look from my phone but based on what I have read in Garden man's report and how few loaded modules there were on the last dump file - I would do the following:
  • Check if BIOS is up to date (I was not able) and reset its settings to default.
  • Disable vanguard anti cheat driver (this has been known to cause multiple issues)
  • Run memtest on each of your RAM modules as per this guide: https://www.sysnative.com/forums/threads/test-ram-with-passmark-memtest86.24300/ (I can see you've already done a memtest above but not checked detail)
  • Test storage drives as per this guide: Sysnative HDD diagnostics as memory can also be referring to virtual memory.
  • Continue with driver verifier as it might be able to pull out something later.
 
  • Like
Reactions: gardenman and eridamskiy
Upvote 0 Downvote
Ran memtest, they were good. what do you mean by check detail? Did a stability update a while ago for my Bios to 301 (most recent version i’ve been able to find) did not work.
if vanguard is the issue, it would be the only thing i have installed on my computer besides the game itself and another riot game. It’s just the reason I bought this gaming PC was for games like this, and i happen to be at a high level in this game. so it puts me in a weird spot if that’s the only thing left causing issues. if it is i’d have to take it up with them and figure out why it’s causing the issue.
the only thing left would be to check the disk with cd burn windows method as u stated above?
will continue to run driver verifier it just makes everything painfully slow, so i’m frustrated doing it but if there’s a chance i’ll keep at it
thanks a lot
 
Upvote 0 Downvote
eridamskiy said:
Ran memtest, they were good. what do you mean by check detail?
Click to expand...
I was referring to me, don't worry :) I was saying I haven't checked the detail, I just saw it in passing.

The reason that we're limited to that is because Dump #9 has so little running, which would generally lead us to think it's one of those drivers, a firmware issue, or a hardware issue. Personally due to the wild eclectic mix of stop errors, I'm actually leaning towards hardware, but if a driver is to blame, Driver Verifier will likely pull it out.

Don't have to burn it to a disc, you can download it straight from here (Seatools for WIndows link: https://www.seagate.com/gb/en/support/downloads/seatools/ ) and run various tests, the guide will tell you how to go about it.
 
Upvote 0 Downvote
I just got home and got two blue screens in the sign in window back to back. The last two dumps that im uploading here : https://drive.google.com/file/d/1r9894kZSgVAkczna7GfSwFpdTLV_yIUb/view?usp=sharing
(5 in there but there are two back to back at 6:44-45 and there was nearly nothing running there.) Going into driver verifier now while I do my job training, then will resort to hardware seagate tests. Thank you again for helping out i really appreciate it.
 
Upvote 0 Downvote
driver verifier just entered boot loop. im excited. i haven't been able to get a dump file from it, it restored windows to previous version and gave me 1 dump file when i got 2-3 blue screens before it underwent automatic backtrack. hopefully it entails something. please....get back to me friends!
https://drive.google.com/file/d/1534iebf59IaBTZ6imwsizvC9jDtN05ha/view?usp=sharing


have been getting more blue screens as the night's been going just not on driver verifier, i'm afraid to go into another boot loop.
 
Last edited:
Upvote 0 Downvote
I have run the dump file(s) and you can see the full report(s) in the link below.
If you are prompted to ""Run only if trusted"" simply click play/run and the html will be viewed. This warning is always present.

Report: https://jsfiddle.net/mozakgcr/show

Summary of findings:
DRIVER_VERIFIER_DETECTED_VIOLATION
"This bug check can only occur when Driver Verifier has been instructed to monitor one or more drivers. If you did not intend to use Driver Verifier, you should deactivate it. You might also consider removing the driver that caused this problem.

If you are the driver writer, use the information obtained through this bug check to fix the bugs in your code.

For full details on Driver Verifier, see the Driver Verifier section of the Windows Driver Kit (WDK)."
Click to expand...

So it looks like it has indeed pulled out IMAGE_NAME: vgk.sys -----> Valorant Anti Cheat Driver. I would start by disabling this. Driver Verifier is not 100% accurate, and something else could be at play, but it is very likely this module is the cause of the issue.
 
Last edited:
Upvote 0 Downvote
so last night i complained to one of my buddies and he told me a fix...
he said valorant driver causing problems with ram running at 3200.
he told me to clock my ram down to 2133, and now i’m not having blue screens. if u have valorant, and have 3200 ram, with random blue screens, clock ur ram down.
 
Upvote 0 Downvote
Glad you have got it sorted. Anti-cheat drivers can cause all manner of issues!

PC Tailor said:
Check if BIOS is up to date (I was not able) and reset its settings to default.
Click to expand...
This would have returned RAM profile back to 2133 when the BIOS was reset. I thought this was done so I missed that.

You might also be able to run the RAM at highest native frequency before reaching OC as I also have seen Valorant work fine up to that point. I see quite a few run it at their boards highest native speed (often 2993) without issue.
 
Upvote 0 Downvote
PC Tailor said:
Yeah the BIOS UPDATE would have kept it the same, the BIOS RESET would have brought it to JEDEC 2133 as it would have brought BIOS settings to default.
Click to expand...
Hey @PCTailor, I just got another blue screen while i was cooking away from my computer, the only second I was away. Couldn't grab the error code. Would you let me know what the problem is? Thank you and sorry for the annoyance
https://drive.google.com/file/d/1VjqaFcMa_zGZFnSKHJKsaq4sabP4I7TI/view?usp=sharing
 
Upvote 0 Downvote
eridamskiy said:
https://drive.google.com/file/d/1uaJGuYm-bD80X98gUKGWrRPb-jUV-Jm4/view?usp=sharing


still having problems... can't figure it out
Click to expand...
Won't be able to look at them really today unfortunately, but all I will say initially is have you disabled the Anti-Cheat drivers? I know this is the main reason why you're using the computer but Valorant (and any other Anti cheat drivers for that matter) are known for wreaking havoc. And disabling it will allow us to see if it is indeed that.
 
Upvote 0 Downvote
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom