[SOLVED] stop code whea bsod

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

Mgwhitt

Prominent
Aug 18, 2019
51
1
535
I7 4790
980 ti
memtest86 4 passes 0 errors( only one 8gb )
ran blue screen viewer and the highlighted problems were hal.dll, nostoskrnl.exe , pshed.dll
currently running prime 95 for about an hour with temps staying around 75 c
planing on doing gpu stress test after prime 95.. any help is greatly appreciated. pretty sure i have tried other things as well such as upgraded windows to newest version and updated all drivers . updated drivers with driver booster 6
,
 
Solution
Darkbreeze
Mostly, it can't be, but there WERE some early BIOS versions that allowed for some exceptions.

I'm sure that's not the case but still it's a five year old system and you've no idea how hard it was pushed or anything else. If it were ME, I'd probably replace the PSU first and if that doesn't fix the problem I'd pull the CPU to check for bent pins. You have no idea if somebody else pulled the CPU to replace thermal paste, or whatever, and maybe got a bent pin on the motherboard. That would certainly, possibly, fit this kind of weird scenario where nothing seems to be wrong, yet is. PSU can certainly cause that as well.

What is your graphics card model?

What country are you in?

How much can you afford to put towards a power supply...
Sort by date Sort by votes
To clarify, I tried to run some extra details on the WHEA error records, however because it couldn't deduce the flags I couldn't find out some of the info I needed.

Typically one could deduce if it's CPU, Memory of GPU based.

The internal classified basically means the type of error is one I'd have to send to an Intel engineer and not one I can lookup using the error records.
 
Upvote 0 Downvote
Sorry, I had to read the thread twice and look at dump postings before I figured out what flags you two are talking about.

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

File information:091019-25953-01.dmp (Sep 10 2019 - 09:19:22)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 26 Min(s), and 14 Sec(s)

File information:091019-23437-01.dmp (Sep 10 2019 - 08:51:58)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: System)
Uptime:0 Day(s), 3 Hour(s), 54 Min(s), and 18 Sec(s)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/GA-H97-D3H-rev-10#ov
You have the latest BIOS (F7) already installed.

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.
 
  • Like
Reactions: Mgwhitt
Upvote 0 Downvote
1st dump mentions win32k.sys., this could be the system process. Its probably part of kernel, i just want to know what the initials mean. This BSOD blames Code corruption which isn't normal

Second error mentions intelppm in the stack, thats the microsoft intel processor driver. This error blames a WIn 8/10 driver.

no closer to understanding it all.
 
Upvote 0 Downvote
Fortunately it would seem the dumps are interpreted the same on both mine and Gardenmans dumps - just the other one on mine is still classed as MAE Unclassified, which I suspect is just a background definition thing they may have updated for the latest debugger.

However I can see no flag errors on Gardenmans report. Not sure if it is feasible @gardenman but are you able to run :
!errrec ffffd10cc4b9e028
on the FIRST dump file (091019-25953-01.dmp ) and post the result here?

I would say also run !tzinfo however I don't think the dump has the TZ info loaded.

I suspect the flags is an issue with the latest WinDBG update, they have had a lot of issues as they updated it overnight without any real warning. And it's the flags that are stopping me from running the ERRREC.
 
Upvote 0 Downvote
gardenman said:
Debugger results for @PC Tailor:
https://pastebin.com/S3XumHJL
Click to expand...
Thanks gardenman - much appreciated.

It was as I expected which is marked out as Internal Unclassified, which basically means the WHEA error code is not publicly released. I'm gradually trying to dwell in more into the WHEA records! I'm hoping OP is already on right tracks with the USB devices, as it wouldn't be unheard of, but we'll see!

Since yours was able to pull out the info, I thought I'd re-install WinDBG from SDK tools and try - then the dump worked absolutely fine with no flag errors, I since found the SDK has installed the correct flags needed to gather the WHEA information, and the Preview version has not.

So there's a change for me already!

Thank you my friend :) !
 
  • Like
Reactions: gardenman
Upvote 0 Downvote
pc still running well.. no blue or black screens with controller unplugged

edit: still running well, probably getting ahead of my self, but wondering about troubleshooting now.
 
Last edited:
Upvote 0 Downvote
have you got another PC you can test that controller in? Since so far nothing has happened with it unplugged, go see if it does same thing to your friends computers (No, only kidding.... )

but testing it elsewhere is a way to know for sure

It could be kb too, as its the victim when controller plugged in. It is the older part.

Test all your peripherals as from what we can see, its not hardware inside PC.
 
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
@PC Tailor I removed cpu. Studied the processor and the socket, every thing looks straight and in a line. No bent pins. Looked a little light on thermal paste. I guess that’s to be expected since it’s probably never been removed.
 
Upvote 0 Downvote
PC Tailor said:
Have you run Prime95? If not, I would try so.
Click to expand...

its actually mentioned in 1st post, but as thats 4 pages ago, I can understand missing it.

CPU - tested
RAM - Tested
SSD - New
GPU was tested with benchmarks

We probably tested PSU as well, its why I started thinking it was a peripheral, since we had checked everything inside PC.

The WHEA error is saying
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT (this means win 10 as well, debugger sees no difference) which sure makes me think its software.

I assume I have already suggested Driver verifer by now?

How long did store test it for? Last time I got mine tested it ran perfect at store and only started crashing again once I got it home. Its what could make me think it was something you plugging into PC.
It isn't the controller
Did we check other keyboard/mouse? I remember you said they were old.
 
Upvote 0 Downvote
Colif said:
its actually mentioned in 1st post, but as thats 4 pages ago, I can understand missing it.

CPU - tested
RAM - Tested
SSD - New
GPU was tested with benchmarks

We probably tested PSU as well, its why I started thinking it was a peripheral, since we had checked everything inside PC.

The WHEA error is saying
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT (this means win 10 as well, debugger sees no difference) which sure makes me think its software.

I assume I have already suggested Driver verifer by now?

How long did store test it for? Last time I got mine tested it ran perfect at store and only started crashing again once I got it home. Its what could make me think it was something you plugging into PC.
It isn't the controller
Did we check other keyboard/mouse? I remember you said they were old.
Click to expand...

@Colif
driver verifier i have not done! I have checked all peripherals ... pc shop had it for about a week with the same issues i had inconsistent bsod. if i have read about driver verifier right, i just turn it on and hopefully it helps show something in the dump file?
 
Last edited:
Upvote 0 Downvote
Mgwhitt said:
@Colif
driver verifier i have not done! I have checked all peripherals ... pc shop had it for about a week with the same issues i had inconsistent bsod. if i have read about driver verifier right, i just turn it on and hopefully it helps show something in the dump file?
Click to expand...
Basically correct, it runs in the background.
You can see how to do it in my BSOD signature link below (which Colif wrote).
 
  • Like
Reactions: Mgwhitt
Upvote 0 Downvote
@PC Tailor followed instructions for driver verifier. also looked over the text for creating memory dumps and i dont remember doing some of those things.. can you tell from my dump files if its set up correctly.. i would hate to be giving you all dump files that arent set up correctly!
 
Upvote 0 Downvote
Mgwhitt said:
@PC Tailor followed instructions for driver verifier. also looked over the text for creating memory dumps and i dont remember doing some of those things.. can you tell from my dump files if its set up correctly.. i would hate to be giving you all dump files that arent set up correctly!
Click to expand...
The fact that you HAVE dump files means they are :)
Just some dump files will grab much more info. But for example a full Memory.Dmp file can also be over 1GB. So the minidump is typically sufficient for basic post mortem debugging :)
 
  • Like
Reactions: Mgwhitt
Upvote 0 Downvote
I have run the dump file and you can see the full report here: https://pste.eu/p/zlKY.html

Summary of findings:
BugCheck C4
Probably caused by : HWiNFO64A.SYS ( HWiNFO64A+1107 )

Bugcheck Description:
DRIVER_VERIFIER_DETECTED_VIOLATION
"This is the general bug check code for fatal errors found by Driver Verifier. For more information, see Handling a Bug Check When Driver Verifier is Enabled on Microsoft docs.

Parameter 1 identifies the type of violation. The meaning of the remaining parameters varies with the value of Parameter 1."

About your bugcheck:
"This bug check can only occur when Driver Verifier has been instructed to monitor one or more drivers. If you did not intend to use Driver Verifier, you should deactivate it. You might also consider removing the driver that caused this problem.

If you are the driver writer, use the information obtained through this bug check to fix the bugs in your code.

For full details on Driver Verifier, see the Driver Verifier section of the Windows Driver Kit (WDK)."
Click to expand...

Oddly enough it has actually pulled out a third party program and identified it as the HWInfo app. Which could be a culprit being as it is directly accessing hardware information, but could also be triggering an actual hardware error. So still could be either.

Regardless I would remove it and retest.
 
Upvote 0 Downvote
PC Tailor said:
I have run the dump file and you can see the full report here: https://pste.eu/p/zlKY.html

Summary of findings:


Oddly enough it has actually pulled out a third party program and identified it as the HWInfo app. Which could be a culprit being as it is directly accessing hardware information, but could also be triggering an actual hardware error. So still could be either.

Regardless I would remove it and retest.
Click to expand...

even if i just put hwinfo on my pc lke 2 days ago, and had bsod previously? i should just follow instructions on driver verifier page again?
 
Upvote 0 Downvote
Mgwhitt said:
even if i just put hwinfo on my pc lke 2 days ago, and had bsod previously? i should just follow instructions on driver verifier page again?
Click to expand...
Yes.

I highly suspect with you having a WHEA error, you do actually have faulty hardware, which is hard to diagnose without swapping the components directly and retesting.

I just suspect HWInfo maybe just forced the hardware into error - but obviously I am only speculating from experience.
 
  • Like
Reactions: Mgwhitt
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom