[SOLVED] Suddenly multiple BSODS

[Anubis161]

Hey there..

Today I've encountered multiple different BSOD's
For example 0x101 caused by hal.dll
Then there was 0x1c7 caused by cl.dll and 0x1a caused by ntoskrnl.exe

System is a:
-non-oc 4790k -> watercooled
-gigabyte z97x-ud5h-bk
-4x4gb Corsair Vengeance on 1333mhz
-Asus strix 1080 8gb
-120gb ssd for Win10 and programs
-4 hdds

Temps are fine
System is otherwise stable, atleast it has been untill today
Memtest shows no errors
Using Avira antivirus, pretty much all drivers are up to date, except the graphic drivers because the latest ones are causing issues, but that's non related..
sfc /scannow says everything's fine
chkdsk /f done

I sincerely have no clue and idea what to do next, except a reinstall, but I'm worried it's something else.....

 

[Colif]

Can you follow option one on the following link - here

and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD


that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a file sharing web site, and share the link here and I will get someone to convert file into a format I can read

 

[Anubis161]

There you go and thanks in advance, that is the latest BSOD from yesterday.. In the past 12 hours no errors..
Thing is they appear to happen randomly.. When gaming, when watching youtube, even when doing nothing and the pc is idle..
https://www.dropbox.com/s/62bubjfvaef5nj8/022219-13406-01.dmp?dl=0

 

[Colif]

I will ask @gardenman to convert those files for us into a format I can read. He may be asleep now but will look sometime tomorrow.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/JVVl.html

File information:	022219-13406-01.dmp (Feb 22 2019 - 13:33:46)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	memory_corruption (Process: SearchIndexer.)
Uptime:	0 Day(s), 3 Hour(s), 13 Min(s), and 53 Sec(s)

The overclocking driver "etocdrv.sys" from EasyTune Overclock (Giga-Byte Technology Co.) was found on your system.

The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite)

Possible Motherboard page: https://www.gigabyte.com/Motherboard/GA-Z97X-UD5H-BK-rev-10#ov There are 3 revisions of the board. I do not know which one you have. This link goes to Revision 1.0. It appears you already have the latest version installed.

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite)

this is also part of GPU Tweak 2 and since you have an asus GPU, that explains why its there.. might not be involved though.

sure are old drivers

Oct 11 2007

LVUSBS64.sys

Logitech Video USBS 64-bit driver

I guess Logitech don't have new ones? Might want a new web cam if Microsoft ever decide to block these from installing.


You have a collection of drivers that can cause problems like

May 05 2013

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/

Sep 14 2016

e2xw10x64.sys

Killer PCI-E Gigabit Ethernet Controller driver http://www.killernetworking.com/

no idea why search indexer crashed, its what windows uses to index your files.

What makes are the hdd? might want to check them out.

 

[Colif]

EasyCheat. Sys caused the BSOD, a line was missing from original dump report, Gardenman told me. Replace lan drivers as well.

 

[Anubis161]

Hey sorry for the late reply..
Gigabyte's Easytune was installed some time ago, so etocdrv.sys might be some leftovers
GPUTweak2 (iomap64.sys ) is idd installed and running, used to monitor the gpu temperature and tweak the fans, although, it is installed from fall 2018 and hasn't caused any problems then..

LVUSBS64.sys (Logitech Video USBS 64-bit driver) I don't have a logitech webcam? Might plugged in one a long time ago tho..
ScpVBus.sys (part of SCP Toolkit), used to emulate an Xbox controller using a wireless PS3 controller.. Also installed since forever, never caused any issues so far..
e2xw10x64.sys (Killer PCI-E Gigabit Ethernet Controller driver), motherboard has two lan controllers, one Intel and one Killer.. Using the latest driver from their site as far as I know

Hdd's are:
Kingston 120gb ssd for system and majority of programs
WD RED 3tb for games
Samsung 1.5tb for downloads
WD RED 6tb for backup

All of them are healthy tho

EasyAntiCheat.sys might actually make sense, since alot of the BSOD's happened during playing Fortnite which uses EasyAntiCheat.. Will have a look into it, thanks alot
Also, this was the last BSOD since friday, I changed nothing, and proceeded with my usual usage/behaviour..


Anyways guys, thanks a ton for the provided help with analyzing the dump file, I really appreciate it!!

 

[Anubis161]

Hey again, a new BSOD today, for the past week there were none whatsoever..
https://www.dropbox.com/s/6h0hd3u9u6a5p6c/030119-14671-01.dmp?dl=0

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/Ufq6.html

File information:	030119-14671-01.dmp (Mar 1 2019 - 13:26:38)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: Avira.SystemSp)
Uptime:	2 Day(s), 9 Hour(s), 34 Min(s), and 18 Sec(s)

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

Who did you get the killer drivers from?

 

[Anubis161]

Intel Support

Intel® Customer Support home page

support.killernetworking.com

I don't have network manager installed tho, cause it caused issues previously and got me banned in some games..
Otherwise, no BSOD's for the past 12 days or so.. Nothing changed..

 

[Colif]

if you don't get anymore, its good.. it means its fixed. BSOD don't wave a flag and give us a sign they gone, beyond not happening again. So no BSOD is a good thing

I don't want to jinx us though

 

[Anubis161]

Yea, I know, I mean it's great and all, but it still bothers me how something like this can suddenly with no changes to the computer hardware or software-wise can "fix" itself..

Anyways, mucho thanks to all of you for the provided support and help, hope I won't need you again
But keep up the good work!!

 

[Colif]

The error you got was a hardware one called by CPU. It could be the circumstances that cause BSOD happen so rarely that you can go weeks/months without it happening. If you lucky, it never happens again.

The only BSOD I seen on this PC in 4 years was caused by me trying to run a program that wasn't fully installed at the time. Self inflicted

You could try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

 

[Anubis161]

Ran the test, everything passed: (lowest temps 37°c, max 80°c)

--- IPDT64 - Revision: 4.1.1.33
--- IPDT64 - Start Time: 21/03/2019 07:14:13

----------------------------------------------
-- Testing
----------------------------------------------
CPU 1 - Genuine Intel - Pass.
CPU 1 - BrandString - Pass.
CPU 1 - Cache - Pass.
CPU 1 - MMXSSE - Pass.
CPU 1 - IMC - Pass.
CPU 1 - Prime Number - Pass.
CPU 1 - Floating Point - Pass.
CPU 1 - Math - Pass.
CPU 1 - GPUStressW - Pass.
CPU 1 - CPULoad - Pass.
CPU 1 - CPUFreq - Pass.
CPU 1 - PCH - Pass.
CPU 1 - SPBC - Pass.

IPDT64 Passed
--- IPDT64 - Revision: 4.1.1.33
--- IPDT64 - End Time: 21/03/2019 07:18:09

----------------------------------------------
PASS

 

[Anubis161]

hey there.. comp started to act up again.. for no apparent reason.. might one of you dear fellas want to check these dumps out? Or point me in a direction where to get the debugger to do so myself if possible?
Anyways, 3 bsods today.. 2 while gaming, 1 when restarting the comp and it booted up again..
Again, nothing really changed (maybe 2 or 3 newly installed games), otherwise same as ever, and everyting fine for the past month..

https://www.dropbox.com/s/hoec51k57h4w73k/041419-14828-01.dmp?dl=0

Dropbox - File Deleted - Simplify your life

www.dropbox.com

https://www.dropbox.com/s/3jwtww6vwqti6sn/041419-15828-01.dmp?dl=0

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/FT35.html

Spoiler

File information:	041419-15828-01.dmp (Apr 14 2019 - 06:51:09)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: System)
Uptime:	0 Day(s), 13 Hour(s), 24 Min(s), and 22 Sec(s)

File information:	041419-15625-01.dmp (Apr 14 2019 - 08:09:15)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	GenuineIntel (Process: System)
Uptime:	0 Day(s), 1 Hour(s), 15 Min(s), and 32 Sec(s)

File information:	041419-14828-01.dmp (Apr 14 2019 - 06:52:41)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: ApCent.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 40 Sec(s)

Comment: The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite or GPU Tweak 2)

Comment: The overclocking driver "etocdrv.sys" from EasyTune Overclock (Giga-Byte Technology Co.) was found on your system.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

seems i jinxed us

try removing GPU Tweak 2 just to make sure its not cause.
You might find you need to run Asus Cleaner to actually get rid of its parts - https://rog.asus.com/forum/showthread.php?95038-AI-Suite-3-cleaner - otherwise autoruns linked below will stop it running at startup. ASio.sys seems to be hard to get rid of - I have it on my pc and I never installed it... blames MIcrosoft.

Run Autoruns and use it to stop the Easytune process you say you removed already


both errors are hardware again... but could be the overclocking drivers.

there is one way to see what drivers it might be

Have a look at this: https://forums.tomshardware.com/threads/how-to-use-driver-verifier-relatively-safely.3471039/

 

[Anubis161]

Hah, no worries.. I was never certain in the first place that it's "fine" now..
Will try to remove the suggested software, but I doubt that's it..

On the other hand.. monday and tuesday were fine.. the only succeding BSOD happened yesterday (wednesday eveing), something to do with memory management if I recall correctly, dump wasn't saved tho..

 

[Anubis161]

Hey there, back again with the same persisiting issue.. Although, I managed to reinstall Win10 meantime and there were hardly any BSOD's happening.. maybe 3 or 4 since my last post..
Today I got 3 in a row basically, two happened mid-gaming (Rainbow Six Siege), one, just after a reboot. Only two of them produced minidumps tho..
So if someone's willing to do a debug on them (thanks gardenman and Colif in advance), I'd appreciate it..
Also, yes I know I still, or better said again have ASUS Gpu tweak and Gigabyte App Center installed, but as I've tested before, those two do not produce the BSOD.. (uninstalled them and the BSOD's persisted..)

Both recent minidumps in the links below

https://www.dropbox.com/s/xoit522r7cyrt4w/060819-18671-01.dmp?dl=0

Dropbox - File Deleted - Simplify your life

www.dropbox.com

 

[Colif]

at least you know what he will point out

I assume its not overclocked still

try running this on CPU and get 2nd opinion apart from Intel test tool - https://www.mersenne.org/download/

 

[Anubis161]

Haha yea right.. But I highly doubt that this software would be the issue.. Also, mainly only reason I'm using any of those two is fan speed management.
No not overclocking any component whatsoever.

Also.. From the last post.. 3 more BSOD's one after another (I'm going nuts)

First Memory Management (playing fortnite)
-> Hard reboot cause it didn't reboot itself
Whea_Uncorrectable_Error (logon screen)
-> Hard reboot again
Clock_Watchdog_Timeout (logon screen)

So we're dealing with 6 within two hours, and nothing whatsoever in the computer hardware / software or configuration has been changed. After the previous post I've installed the 399.24 geforce drivers tho, just to be sure..

Again, the last three minidumps in the links below..

https://www.dropbox.com/s/gqa50yk56nmugqr/060819-14046-01.dmp?dl=0

Dropbox - File Deleted - Simplify your life

www.dropbox.com

https://www.dropbox.com/s/k13sqvwl6v1j4xt/060819-19750-01.dmp?dl=0

 

[Colif]

WHEA & Clock watchdog are both hardware errors. Both called by cpu but not necessarily caused by it.

Fact BSOD survived a clean install means they likely hardware... need to work out what hardware. So 2nd CPU test was just a way to 2nd guess Intel test, as I have found its not perfect.

need to reduce hardware being used to isolate causes. It could be the GPU but hard to play games without it... I would suggest running off just the motherboard display outs and take GPU out and see if you still get BSOD.

The errors can be any hardware... makes them difficult to identify.

they can be anything. Even hdd can be to blame, so test everything attached to PC.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/i2HX.html

Spoiler

File information:	060819-19750-01.dmp (Jun 8 2019 - 14:42:44)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	GenuineIntel (Process: Avira.VpnServi)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 21 Sec(s)

File information:	060819-18796-01.dmp (Jun 8 2019 - 12:55:42)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	memory_corruption (Process: RainbowSix.exe)
Uptime:	0 Day(s), 0 Hour(s), 09 Min(s), and 21 Sec(s)

File information:	060819-18671-01.dmp (Jun 8 2019 - 12:03:58)
Bugcheck:	CRITICAL_STRUCTURE_CORRUPTION (109)
Probably caused by:	Unknown_Image (Process: FortniteClient)
Uptime:	1 Day(s), 19 Hour(s), 51 Min(s), and 16 Sec(s)

File information:	060819-18437-01.dmp (Jun 8 2019 - 14:41:02)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: Avira.SystemSp)
Uptime:	0 Day(s), 0 Hour(s), 52 Min(s), and 00 Sec(s)

File information:	060819-14046-01.dmp (Jun 8 2019 - 14:45:23)
Bugcheck:	CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:	Unknown_Image (Process: PresentationFo)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 34 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.