06-08-2020, 12:12 PM
|
#1
|
Franchise Player
|
Win 10 - Blue screen of death
I'm been having the blue screen of death pop up on me regularly. About 2-3 times a week it pops up, offers zero solutions, and I'm forced to hard-reset and wait for it to happen a couple days later.
The internet searches haven't been too helpful TBH. I've updated my videocard driver (AMD Radeon), updated my other drivers (nothing pending) as per what some sites have said. Yet the damn thing persists regularly. I am using a SSD to host my OS and programs, so I don't believe it's hard drive failure.
So what is the ACTUAL solution to fixing this??
|
|
|
The Following User Says Thank You to Huntingwhale For This Useful Post:
|
|
06-08-2020, 12:21 PM
|
#2
|
Franchise Player
|
My first suspicion is a bad driver. If you don't want to stab in the dark, get windbg tools:
https://docs.microsoft.com/en-us/win...download-tools
It's not all that intuitive to use, but you can load the crash dump and analyze it. It will often point you to the faulty driver which you can then try reinstalling or find a newer or older version.
|
|
|
The Following User Says Thank You to Fuzz For This Useful Post:
|
|
06-08-2020, 06:46 PM
|
#3
|
Franchise Player
|
I guess that didn't work either . Even the dump file somehow corrupted itself lol.
|
|
|
06-08-2020, 06:48 PM
|
#4
|
Franchise Player
|
Ooof. Are there older crash dumps you can find?
|
|
|
06-08-2020, 07:25 PM
|
#5
|
Lifetime Suspension
|
Post your system specs.
|
|
|
06-08-2020, 08:29 PM
|
#6
|
Franchise Player
|
Quote:
Originally Posted by Fuzz
Ooof. Are there older crash dumps you can find?
|
Looks like it overwrites that one file each time, as all historical reports point to that single file.
The only other log I can find says:
Problem signature
Problem Event Name: BlueScreen
Code: 100000ea
Parameter 1: ffff850c26175080
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_17763
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17763.2.0.0.768.101
Locale ID: 4105
Quote:
Originally Posted by zamler
Post your system specs.
|
AMD FX 4350 4.2ghz quad core
8GM Ram
AMD Radeon R7 200 video card
SSD
Win 10
|
|
|
06-08-2020, 08:40 PM
|
#7
|
Franchise Player
|
Look in
C:\Windows\minidump
There should be a dump file for every crash. It's not the full memory dump but usually has what you need.
|
|
|
06-08-2020, 11:02 PM
|
#8
|
Lifetime Suspension
|
Need to know the motherboard.
Also run event viewer>windows logs>system
shortcut to event viewer search eventvwr
|
|
|
The Following User Says Thank You to zamler For This Useful Post:
|
|
06-09-2020, 12:27 PM
|
#9
|
First Line Centre
Join Date: Nov 2007
Location: Airdrie, Alberta
|
Remember when it started happening and look back to what was installed/changed near that time, also open up the case and remove the ram and reseat it.
|
|
|
06-09-2020, 12:36 PM
|
#10
|
Franchise Player
|
Quote:
Originally Posted by Raekwon
Remember when it started happening and look back to what was installed/changed near that time, also open up the case and remove the ram and reseat it.
|
I usually suggest "what changed" first, but now with Windows update installing whatever it wants whenever it wants, including driver updates, it gets harder to nail that bit down. But ya, it could be something as simple as "it started when i plugged in this USB device".
If it is a RAM error you often see a different crash source in every mindump. If it's the same one every time, you know where to start. But ya, if you can't find any cause, run memory scan.
|
|
|
06-09-2020, 01:24 PM
|
#11
|
Norm!
|
Did you do a rollback out of curiousity?
__________________
My name is Ozymandias, King of Kings;
Look on my Works, ye Mighty, and despair!
|
|
|
06-09-2020, 06:01 PM
|
#12
|
Franchise Player
|
Quote:
Originally Posted by Fuzz
Look in
C:\Windows\minidump
There should be a dump file for every crash. It's not the full memory dump but usually has what you need.
|
Nothing in that folder, however the folder was modified the exact time my PC crashed. Checked and no folders/files are hidden. Just an empty folder.
Quote:
Originally Posted by zamler
Need to know the motherboard.
This is the motherboard
Also run event viewer>windows logs>system
shortcut to event viewer search eventvwr
|
Nice I think I see the 2 errors here right at the moment it happened.
The amdacpksd service failed to start due to the following error:
The system cannot find the file specified.
The amdacpusrsvc service failed to start due to the following error:
The system cannot find the file specified.
Quote:
Originally Posted by CaptainCrunch
Did you do a rollback out of curiousity?
|
No haven't done that yet. I actually did have my AMD driver update a couple weeks ago, so maybe that is it. It would time out with when the issue started happening.
I uninstalled then re-installed the driver. Hopefully that will fix the issue! If not I'll be back to complain more.
|
|
|
06-09-2020, 06:04 PM
|
#13
|
Franchise Player
|
That could very well be it. Interesting the minidumps folder is empty. Never seen that before. Hope that solved it.
|
|
|
06-09-2020, 06:21 PM
|
#14
|
Lifetime Suspension
|
That blue screen is almost always because of a crashing GPU driver. Can change it so Windows does not overwrite the crash file by going search>SystemPropertiesAdvanced>Startup and Recovery>Settings
you'll see the option
|
|
|
06-09-2020, 09:43 PM
|
#15
|
Draft Pick
Join Date: Jul 2009
Location: Edmonton
|
I had that happen on a dell of mine a couple years back. I had to update the BIOS and that fixed it
|
|
|
06-11-2020, 10:03 AM
|
#16
|
CP Gamemaster
Join Date: Feb 2010
Location: The Gary
|
Windows 10 did a major update recently, and I had the first blue screen of death I've ever had on two computers since that update. I really wish these updates wouldn't change or reset so many system settings. Seems like my USB devices get recognized from scratch after these big updates, for example.
|
|
|
06-11-2020, 10:16 AM
|
#17
|
Franchise Player
|
Did you install the feature update? I'll be skipping that for awhile...
|
|
|
06-11-2020, 10:58 AM
|
#18
|
Franchise Player
|
As bizarre as this sounds (because it's supposed to be more login than normal OS usage/crashes), rebuilding the MBR strip has helped me in the past for some situations in fixing BSOD. Technically it was hard resetting due to BSOD that required MBR strip repair in the first place, but after that repair, the BSOD sometimes would go away. Can't remember why I was getting BSOD in the past though...
Worth trying?
|
|
|
06-11-2020, 11:46 AM
|
#19
|
CP Gamemaster
Join Date: Feb 2010
Location: The Gary
|
Quote:
Originally Posted by Fuzz
Did you install the feature update? I'll be skipping that for awhile...
|
I assume it was since it did a "Welcome to Windows" screen on login. Since Windows 10 doesn't actually tell what any updates are, it's hard to say!
|
|
|
06-12-2020, 07:25 AM
|
#20
|
Franchise Player
|
Quote:
Originally Posted by Mazrim
I assume it was since it did a "Welcome to Windows" screen on login. Since Windows 10 doesn't actually tell what any updates are, it's hard to say!
|
I like how the "check for updates" button doesn't just check for updates. It downloads and installs them too. Maybe I just want to "check for updates" and see what is there. But no. The button doesn't do what it says it does.
|
|
|
Thread Tools |
Search this Thread |
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -6. The time now is 09:11 PM.
|
|