BSOD and Random Driver Display Errors

[Vanja126]

It is actually SSD that was checked. I did not have any viruses/malware showed by Malwarebytes once this problem started,( I had one Troyan detected months later tho that was removed). I used Who Crashed for BSOD analytic" https://prnt.sc/inq7ux

Reliability History screenshot: https://prnt.sc/io7x40

 

[Cycloid Torus]

Thank you. WhoCrashed may not give us the fault, but it does say there is a replicable error.

Please go into Reliability History and review the errors by following the blue links in the 'critical errors' sections for Application and Miscellaneous.

Any detail which identifies a failing module or service?

 

[Vanja126]

The only indicator I can see at around time when I got BSOD is video hardware error with code: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80003489556, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\030518-8299-01.dmp. Report Id: 030518-8299-01.

 

[Cycloid Torus]

I wish I could just have your system for an hour...too bad.

This may sound like a step backwards, but it might work. Unplug everything that you do not need - so you can just boot the system - one storage drive, no CD/DVD drives, only keyboard and mouse directly attached by USB on motherboard, GPU and monitor.

Boot the limited system and try to induce the BSOD by running HW. If you still get the error, remove all but one stick of RAM. If you still get the error, swap for another stick of RAM.

 

[holdum323]

0x0000001e https://support.microsoft.com/en-us...urs-intermittently-in-windows-7-sp1-and-windo
Every thing I have seen points to RAM??
Quote taken from the above MS link.
This issue occurs because of an NTFS file system memory leak issue. Specifically, when an application opens a file that has an oplock on it for modification in a transaction, NTFS will break the oplock and will leak nonpaged pool memory. This causes excessive memory usage and memory allocation failures.

 

[Cycloid Torus]

0x0000001e https://support.microsoft.com/en-us...urs-intermittently-in-windows-7-sp1-and-windo
Every thing I have seen points to RAM??
Quote taken from the above MS link.
This issue occurs because of an NTFS file system memory leak issue. Specifically, when an application opens a file that has an oplock on it for modification in a transaction, NTFS will break the oplock and will leak nonpaged pool memory. This causes excessive memory usage and memory allocation failures.

If so, would that appear in task manager? On the tab which tracks memory use?

You may have found it. Might be worth trying.

 

[holdum323]

If so, would that appear in task manager? On the tab which tracks memory use?

You may have found it. Might be worth trying.

Hi @Cycloid Torus I don't have a answer for you about task manager. I'm not sure what the memory tab shows. Above my pay grade. I think it's a good thing if you're using a lot of your memory. https://www.howtogeek.com/169823/be...to-know-about-using-the-windows-task-manager/

 

[holdum323]

Hi! I'm out of my comfort zone here. I know very little about how to use Task Manager. I don't know any thing about tracking memory usage. You will have to take over from here @Cycloid Torus . Here's article from HTG. I have read it several times. Some things I understand. Some things I don't! It's been a pleasure working with everyone on this issue, but I think I'm above of my pay grade at this time. I have learned a lot while replying on this thread. Team work is a good thing! I have survived on TS forum because I have learned how to use Google. There is no way I could know all these things about BSOD and remember them. BSOD are not easy to solve. There are a lot of things that can cause them. When all else fails, go nuclear and do a clean install.
Let us know how things go!
https://www.howtogeek.com/169823/be...to-know-about-using-the-windows-task-manager/

 

[Vanja126]

Hi everyone, thank you for your answers! After your indications about RAM issue, I checked RAM memory in BIOS and found out it still running on 1666mhz even I set BIOS settings by default long. Ram was bought with stock 1666mhz but I now downclocked it manually on 1333mhz last night which should be more suited for Sandy Bridge processors. Since then I noticed a significant drop in temperatures of both GPU and CPU http://prntscr.com/ioiqd7
Also, I not had single display driver error (which may be coincidence), however, I am still getting BSOD after starting HW info. I guess next step should be testing out ram one by one when I get some time for messing up with it

 

[Cycloid Torus]

Well done...a nuance easily overlooked...ever consider an IT job?

 

[Vanja126]

IT related jobs were always my passion I guess.

 

[holdum323]

Hi @Jona Roy Welcome to techspot. 1-2-3 All three are good advice for BSOD's. Team work is a good thing!
Especially update the graphics driver. (y)
https://www.howtogeek.com/98465/htg-explains-when-do-you-need-to-update-your-drivers/