BSOD, Any Help Appreciated

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

autological

Prominent
Nov 24, 2017
25
0
530
So, I've been experiencing a lot of BSOD crashes as of late. To be specific the WHEA_UNCORRECTABLE_ERROR. It seems to happen randomly. It might be worth mentioning that the error started occuring (some) time after I upgraded my graphics card. I have updated my drivers, cleaned the computer and reinstalled windows. I don't think its an overheating problem and I don't have overclocking turned on. Any suggestions on how to proceed?

Using the program BlueScreenView I am able to get this information, but I'm not entirely sure what to make of it: https://imgur.com/X7n3KI7
Here's a link to the minidump:
https://www.mediafire.com/file/k5uzzuroty51g59/112417-5953-01.dmp

Specs:
Intel(R) Core(TM) i7-6700K CPU @ 4.00 GHz 4.01 GHz
Installed RAM 16 GB
64-bit operating system, x64-based processor
Windows 10 Home, Version 1709
OS Build: 16299.64
Device ID: 71B419EB-CDD6-4BC0-BBD0-C90CDCE10243
Graphics Card: Gefore GTX 1080
Driver Version: 388.31
 
My description for Bdagent.sys was for BitDefender. I found the description here (I think): https://www.file.net/process/bdagent.exe.html

I just now found another page with different description: http://www.freefixer.com/library/file/bdagent.sys-222614/

I've updated my description of Bdagent.sys to be either BitDefender or BullGuard.

I don't think you have BitDefender (it has to be downloaded and installed, just like BullGuard does and you would probably remember that) so don't worry about that.
 
Or Bullguard uses Bitdefenders engine... it did in 2013, it isn't the only AV that uses it either (I don't have a full list). I only found that out after googling it.

Gardenman is the guy who suggested DriverStoreExplorer to me, and has a better idea of how it works. I will also ask others for any ideas about removing that file.

One hammer approach is reset windows 10 and hope the driver isn't installed by windows. It shouldn't, even though CPU can overclock, board can't so it shouldn't be there. Copy anything off PC you can't afford to lose and run a reset
Go to settings/update & security/recovery
Under reset this PC, click Get Started
2 choices
1. keep files/settings (Files = library folders. Library folders = Documents, pictures, movies, music (the default folders that come with windows). Settings = logins and desktop)
2. Wipe it all - deletes everything and set windows 10 up as new

I would go with 1 as its easier. Either choice, PC will restart and reinstall Win 10. You will need to reinstall all programs again
 


I'll give that a go.
 
DriverStoreExplorer worked for me when I tried it in my "testing" VM, but I didn't test it on my 'real' system. I'm pretty sure it will delete the driver, but I can never guarantee what the consequences of that will be. I *think* it will be OK, but I can't promise it will.

Another option would be to use AutoRuns to disable the driver.

I would create a good system backup then give it a try. If things go wrong, you can always restore from the backup.
 


Hi,

I did a wipe and for a while it worked. But I just got a BSOD and they are becoming quite frequent. I'm afraid I need your help again.

Here's some information. Please ask if you need anything else.
https://imgur.com/c5DwbWp
https://imgur.com/a/lWOiQ
http://www.mediafire.com/file/43dcyasxukd4lx1/031818-5546-01.dmp

Just for the record, the files that were causing problems before don't appear anywhere, so I don't think that's it.
 
Did you ever run the Intel Processor Diagnostic Tool? https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

I wonder if its tied into ICCWDT.sys which is the Intel(R) Watchdog Timer driver which is something I can't say I have noticed before but I have seen twice in recent days.
A watchdog timer is a hardware-monitoring tool that prompts system recovery after a failure, with a simple pinging mechanism. When the watchdog timer is not pinged after a certain amount of time, it saves system information to aid with debugging and then attempts to correct the problem by rebooting the system. The watchdog timer can help with recovery from problems including but not limited to: Problems with operating system task scheduling; Deadlocks from faulty interrupt handling; Faulty interrupt disabling or masking; Incorrect hardware configurations or hardware errors; General software failure.

https://www.intel.com.au/content/www/au/en/embedded/solutions/iot-gateway/enabling-and-configuring-watchdog-timer-app-note.html

wish i could find more info on it.

well. system was up 12 hours so its not a boot problem at least.

I would remove Intel One Boot Flash Utility since its from 2009
 


I did run Processor Diagnostic and it passed on all fronts. I did a new one just now, and still no errors.

The One Boot Flash Utility does not not appear in Apps. The same with a File Explorer search. How do I remove it? That is if its even there at all.
 
that file is showing as installed on last dump file

mage path: \SystemRoot\System32\drivers\flashud.sys
Image name: flashud.sys
ADA Info : Intel One Boot Flash Utility Driver https://downloadcenter.intel.com
Timestamp : Fri Mar 6 2009

its odd its there, from what i can tell its meant to be for server boards. Its used for flashing the bios (updating it), not sure why its there. It may not even be the cause. I do know it was on PC when you were getting WHEA errors before and since the errors went away, I have to assume its not the cause.

So its not CPU causing it. Thais a good thing.

it appears your bios is newer than the version of iccwdt you have installed, its part of the chipset drivers. It might be cause of whea errors

Image path: \SystemRoot\System32\drivers\ICCWDT.sys
Image name: ICCWDT.sys
ADA Info : Intel(R) Watchdog Timer driver
Timestamp : Sun Sep 20 2015

Bios:
VENDOR: LENOVO
VERSION: O1ZKT45A
DATE: 11/07/2017

Have you run auto update on this page? https://pcsupport.lenovo.com/au/en/products/desktops-and-all-in-ones/y-series/y900-34isz
 


I followed the path to the flashud.sys file but I can't delete it: https://imgur.com/a/P3hCN, same with ICCWDT.sys. Should I try with the DriverStore-thing again?

I ran the auto update but this happened:
https://imgur.com/a/tqO6m
These drivers were listed even after I did the update (and a restart). Is that indicative of a problem?
 
AOUXUb8.png

Intel Serio I/O is the touchpad driver
IRST = Intel Rapid Storage Tech - not useful unless your laptop has a smaller SSD used to boot a slower hdd
Realtek Card Reader is what it says it is.

I don't know if any of those would help

Have you had any more BSOD? If so, upload the mini dumps as more we have, more chance we find cause.

Are any errors showing in Reliability History? Search cortana for that and choose the control panel choice.

WHEA can be any hardware, not just the CPU. Since you don't have any overclocking software this time, I have to look elsewhere. It can still be a driver for other hardware I guess.

My next suggestion would be run driver verifer but it can be painful as it can put you in a boot loop. MY steps below include ways to escape it. I am going on theory its software since you managed to fix this same error before. Lets see if that flashud driver comes up or not

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again. Download the Windows 10 media creation tool and use it to make a win 10 installer on USB

Also helps to run system restore before hand to create a restore point to roll back to if necessary. this is probably more useful than the safe mode method below.

Once it bsod, upload the minidump file and we see what it shows us.

The instructions to stop it looping are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode
Now open command Prompt
type verifer /reset and press enter
restart PC


Just in case I can't figure this out, read the top of this page and supply them the info they need, and see if they can figure it out. If they do, I would love to know what it is - https://www.tenforums.com/bsod-crashes-debugging/

I am not giving up, just thought I offer an alternative as there are people around who can read dumps better than I can. Some use this forum but people here hardly ever look at threads that others are answering, so unlikely to look at this. You can link to this thread there so they don't repeat suggestions. Might be a lot faster than me too.
 


I have only had one BSOD since last time I posted, but to be fair; I haven't really used to the computer all too much.
Here's the new dump:
http://www.mediafire.com/file/38ucq58u0qf34e2/031918-4937-01.dmp
Here's the reliability history:
https://imgur.com/a/0tjfc

I will try the driver verifier later when I have some more time and probably post over at the other forum at that time too.
Thanks for the help so far.
 
Hi, I ran the dump file(s) through the debugger and got the following information: https://pste.eu/p/FxgS.html

File: 031918-4937-01.dmp (Mar 19 2018 - 12:48:09)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: GOG Galaxy Notifications Renderer.exe)
Uptime: 0 Day(s), 22 Hour(s), 27 Min(s), and 00 Sec(s)

The overclocking driver "IOCBios2.sys" was found on your system.
New driver that I haven't seen before: FBFsmon.sys
I think I've seen YLED.sys before but never got a good description on it. (I re-read the above, seems YLED.sys was pointed out here before).

I can't help you with this. Wait for additional replies. Good luck.
 
de ja vu?? The overclocking driver + YLED are repeats, they were there before... so what loaded them again?

can you look in update history of windows update and see if you got any updates that happened before the 1st WHEA error. I think windows might be loading a driver pack for laptop including those 2 files. I am not sure though as looking on the Lenovo web site doesn't show that many intel drivers besides

Intel Management Engine Interface
Intel AMT (Active Management Technology)
Intel chipset driver
Intel Serio I/O
Intel Bluetooth
Intel Rapid Storage Technology
Intel Wifi

which is quite a few but none would normally include overclocking drivers I don't think
FBFSmon.sys is a lenova file, short search leads to that conclusion. Lenova eeboot optimiser perhaps? I don't see it on web site for the laptop
Yled.sys still remains a mystery as to what it is.

If we can kill the overclocking driver, I would suggest it would fix whea errors.

Try on Tenforums, I feel like I am going around in circles
 


I deleted the BIOS driver with revo and haven't had any problems since. I'll return here and Ten Forums if something happens. Thanks again for the help
 


Hi. The BSOD is returning... I am certain it's the overclocking driver causing it, because I have been deleting it every time it (somehow) gets reinstalled using the revo uninstaller program and that fixes things until, as I mentioned, it gets reinstalled. Unfortunately, I can't keep doing that, since the revo free trial has timed out. Any other programs I could use? Or better yet, do you know what could be reinstalling it again and again?

I'm sorry that I have to bother you this many times, but I would really appreciate the assistance.
 
AutoRuns should very much allow you to disable the driver. Leaving it on your system is OK if it's disabled. If it is somehow getting re-installed or re-enabled, then you have some additional software on your system that is re-installing it or re-enabling it. Look for any system software that might be doing that and disable or remove it.

The file wasn't detected in this latest dump file. If it's disabled in AutoRuns then it's not causing the problem.

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

File: 042818-5781-01.dmp (Apr 28 2018 - 04:27:00)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 17 Min(s), and 58 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.
 


Sorry, could you guide me through how update the BIOS? What I'm doing doesn't seem to work..
 

I enabled the CSM Support in BIOS mode, but, when it restarted, the monitor black screens after showing logos and that stuff. I don't know if it's because the monitor isnt receiving a signal or if it's the computer not starting properly. Do you have a solution?
 
I know why it black screened, its cause it was trying to boot a hdd that didn't exist. Your hdd is formatted to support UEFI but it should have booted off the USB, not tried to find a hdd. disabling CSM would likely mean PC will boot but then BIOS update may not work.

I would go ask Lenova for assistance as someone there might have a better answer. Not trying to get rid of you but we aren't getting anywhere. We been trying to fix this for 6 months... they should at least be able to help update BIOS and might have a better idea of how to fix the BSOD.