Pending OP Response Long time random BSOD problem

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
So I've had this issue for a year or so and have tried many things including about 3 different win10 re-installs. I was finally able to get a minidmp file to save and uploaded it to dropbox. Here is the link:
https://www.dropbox.com/s/b60r7ojoww1ko7b/041019-8062-01.7z?dl=0
also the full memory.dump file: https://www.dropbox.com/s/x3y54stg2o71wbp/MEMORY.zip?dl=0
Usually INTERRUPT_EXCEPTION_NOT_HANDLED ntoskrnl.exe and I've also seen something like 'KMode Exception Not handled'
7700k @ 4.8ghz 1.35vcore
evga 2080ti
16gb 3200mhz ram, memtest for 12+ hours, no errors.
corsair rm750i psu
500gb ssd
3tb and 8tb storage sata drives, both 0% frag
It's really random.. most of the time it's when I'm asleep. I'll wake up and notice apps are open, indicating a full restart and then I check the task manager and sure enough it's only been up for a short while even though I left it on all night. I've been playing some borderlands and borderlands 2 recently so it's happened maybe once or twice in game, but not too often. It also happens when I'm browsing google, using chrome, etc. Nothing really stands out as as a trigger, just pretty random. Some times my computer can last several days with no issues, other times BSOD a few times a day but usually quite a few hours in between.
I've been googling the error for about an hour or two and have done this multiple times within the last year or so.. but ultimately leading nowhere.
I was hoping somebody could diagnose my dump file and see if there is some driver that may be causing this. or perhaps hardware?
Thanks!

Also, another minidump from last night: https://www.dropbox.com/s/xp30dqqdmz1gwyl/041119-7437-01.7z?dl=0
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the Attach button, bottom left of the dialogue input box
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
Ah sorry for using dropbox. I have attached them to this post since I can not edit the main post. Thank you.
 

Attachments

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
DirectX and video drivers look to be the cause of the two previous crashes.

Can I ask what version of Windows 10 you are running and after reinstalling Windows did you reinstall the drivers for the MB and starting with the chipset drivers first.
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
I've ran DDU every time with nvidia drivers, just to be safe.

Win10 Version 1809, Build 17763.316
I used drivers, including chipset, from here
https://www.msi.com/Motherboard/support/Z270-GAMING-M3
Also just recently updated my mb bios this morning, been pretty smooth since.

I am actually getting a replacement 2080ti from EVGA, RMA. I have a hard to describe issue but the best way is... every once in a while I'll get this random broken image flicker on the screen. After chatting with EVGA they decided RMA would be best option since I eliminated many other things such as OS/cables/displays/etc. So could it possibly be some sort of hardware failure with the card itself that is causing this or is that a reach?
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
Win10 Version 1809, Build 17763.316
Is that an Insider Preview version.

All your hardware is of good quality so atm I am suspecting a software issue, I would still take the replacement GPU though.
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
Is that an Insider Preview version.

All your hardware is off good quality so atm I am suspecting a software issue, I would still take the replacement GPU though.
Hmm I'm not sure, that sounds familiar but I got my iso through the media creation tool from microsoft. but do you think that could be a possible reason? should I get it from elsewhere?
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
We could do with a screenshot of your OS info, to get this go into Action Centre, Update & Security and then click on the OS Info tab on the right hand of the page, see attachment below;

To capture and post a screenshot;

Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... after typing in any response you have... click on Upload a File to add the screenshot.

Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.
 

Attachments

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
Apologies for the delay getting back to you Killmeplsnow, not been around for a couple of days :(

Looks the same as my Windows 10 Pro so not an insider preview.

How has the computer been behaving since Friday when you updated the BIOS.
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
No worries, thank you for your help.
Everything has been good so far actually.
Between the motherboard BIOS and replacement graphic card, I think everything should be set. I haven't had one BSOD or weird screen flicker since.
Thanks for all the help man!
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
Glad to hear that you appear to have been able to resolve the issue and thank you for letting us know (y)

Would you like to keep your thread open for a few more days.

You are welcome btw :)
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
Well looks like the third 2080ti EVGA sent me needs to go back and I'll need a fourth 2080ti, lol.
I'm going to copy/paste most of the next two paragraphs because I've been discussing it a lot lately today.

So got my 2080ti from Newegg on release date and first card had a dead fan. First RMA worked fine for about a month then started having a very rare and random flicker. I went on for about 5-6 months until it became much more frequent and I was sure it was real, not just in my head. RMA'd it just a week ago on and received my 3rd card last Friday. It was good until today.

I was playing Division 2 when small little triangles/shapes and colors appeared and crashed my game. I saw multiple errors in Event Viewer and google lead to DDU.
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
Graphics SM Warp Exception on (GPC 5, TPC 2, SM 0): Illegal Instruction Encoding

The message resource is present but the message was not found in the message table
Cleaned all my drivers in safe mode, internet disabled and restarted multiple times. Division 2 was just constantly crashing after 1min or so of loading, never got in game. Decided to run Borderlands 2 which had some artifacts but still opened/playable. I downclocked core and memory clock -500 and it finally went away. I'm able to launch Division 2 now but it crashes after a few minutes on all low settings. It actually just freezes the computer and needs two hard resets. If I reset the -500 back to 0, normal out of box settings, it starts artifacting and hard crashes the system.

I've already started my fourth RMA but what I'm really concerned about is the PSU. The EVGA tech suggested to go into BIOS and we monitored the 12V which stayed the same for the whole time so they determined RMA is best choice atm. I'm thinking if resetting to out of box settings starts artifacting/crashing and it needs to be at -500 to run desktop, it can't be the PSU - it has to be the GPU right? If it was the PSU, it would have to just BSOD, restart or completely shut down right?

One other random thing... I just updated to the next Windows 10 build. My last windows update was around February and I use OOSU10 to completely block all windows telemetry, updates, etc then use it to unblock, update, and block again. Right after the update, I noticed amazingly smooth gameplay in Division 2 for an hour or so until this happened. but I went through DDU, safemode, internet off, etc so I don't think any Windows 10 update would affect this, it's gotta be GPU related right?

Sorry to keep bothering you with these walls of text...
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
2,467
413
55
I'm going to copy/paste most of the next two paragraphs because I've been discussing it a lot lately today.
May I ask who you have been discussing this with.

The EVGA tech suggested to go into BIOS and we monitored the 12V which stayed the same for the whole time so they determined RMA is best choice atm.
BIOS readings can in no way be relied upon as the computer is under the least amount of load that it can be, fire up a game increases the demand on the PSU and generates heat neither of which can be checked in the BIOS.

it's gotta be GPU related right?
Nope, bad drivers, Windows DirectX problems and OC settings are just a couple of other things that can cause this.

You may need to start from scratch with this, clean install of Windows, clean install of the chipset drivers, using earlier drivers for the GPU that were proven to be stable and no OCing, if you get the same issue with this set up it would go some way to suggesting a hardware issue but atm it still looks like being software related.

My last windows update was around February and I use OOSU10 to completely block all windows telemetry, updates, etc then use it to unblock, update, and block again.
You could have done with mentioning this earlier, this was most likely what was making it look like you were running an Insider Preview version of Windows (which is beta software and therefore prone to bugs) why are you doing this, Windows should be allowed to check for updates as and when it needs to, it not only makes sure that any bugs are quickly ironed out it also makes the OS more secure which in turn helps protect you from malware attack.

Programs like OOSU10 make changes to the Windows registry which is a big no no as it will eventually end in disaster, not being personally familiar with OOSU10 I cannot say for sure but I strongly suspect that blocking Windows updates is not something that the OOSU10 programmers would be endorsing.
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
May I ask who you have been discussing this with.
There is one other forum but mostly Discord. Lots of funky suggestions but no actual expertise lol.

Nope, bad drivers, Windows DirectX problems and OC settings are just a couple of other things that can cause this.
So normally I would agree with this but in this case everything was working on the same OS for months. The third card was working really well for 7-8 days at full load. GPU drivers had been same for those 7-8 days. This suddenly happened during gameplay, the actual artifacting was very present and crashed the game/system. Biggest concern is that when I downclock -500 on core/memory both, the artifacting goes away while on desktop but if I reset it back to factory defaults, 0, then it starts artifacting - even while on the desktop. I really need to get another rig to stick this card into but most of my rl friends have weak computers with 300/400w PSU lol. Would a Windows USB boot key work? Like a portable version of Windows installed onto a USB drive.


You could have done with mentioning this earlier, this was most likely what was making it look like you were running an Insider Preview version of Windows (which is beta software and therefore prone to bugs) why are you doing this, Windows should be allowed to check for updates as and when it needs to, it not only makes sure that any bugs are quickly ironed out it also makes the OS more secure which in turn helps protect you from malware attack.
Hmm I've never actually had a problem using this program for a few years now. I typically don't like Windows update because it breaks a lot of things, especially for gamers. There have been numerous updates that drop FPS in a lot of games that I like to avoid. I usually wait for some major updates to drop, wait a few weeks and then DL it if all reports are good. I thought the last one was at the beginning of April and it all seemed good. I might try a restore point later... would that restore /rollback registery/updates too?

Programs like OOSU10 make changes to the Windows registry which is a big no no as it will eventually end in disaster, not being personally familiar with OOSU10 I cannot say for sure but I strongly suspect that blocking Windows updates is not something that the OOSU10 programmers would be endorsing.
Hmm I think that's kind of the whole point of OOSU10. My main reasoning for getting it was to stop all the spying Windows 10 likes to do. I may have to reconsider if this is what is causing these issues.
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
Just another small update, couldn't hit Edit so had to post again, but I did a system restore and first thing on reboot, artifacting. All the MSI afterburner -500 settings were reverted too, so I had to restart a few more times but got the -500 core/memory setting back in there and it's stable at the desktop again, lol. I'll prob just leave it like this for now and use 365 day deferred windows updates.
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59
One more update, sorry again, I was able to get OCCT to start working by using DirectX 9 instead of DirectX 11. The test is running at 95% gpu usage, 250 fps but limited to 30% power through MSI and -500 core/memory. I want to remove these settings but I'm 99% sure the artifacting and system crash will follow, lol. The test has been running on the PSU tab for about 10 minutes but I'm going to leave this on for a few hours if possible to try to rule out the PSU... do you think OCCT would be a good determination of PSU working if it's going for a while on DirectX9 with 250FPS?
 

Killmeplsnow

PCHF Member
PCHF Member
Apr 12, 2019
11
0
59

Attachments