[SOLVED] Had many BSOD even after a clean install, can someone analyze the dump file of my last BSOD.

[wass1991]

Hello, I had many BSOD in the past year so I decided to reinstall windows in December. Everything was ok until February, I've had two BSOD in less than 24hours. I was either on zoom calls or browsing. (not gaming ) . Had another one last night while on zoom I heard a weird buzz sound and then BSOD again. I turned my pc back on and put the dumpfile on a drive her is the link to my last dump file if someone can pinpoint the issue or point me in a direction it would be appreciated . ( Also could it simply be that I need to update my motherboards Bios (PRIME Z390-A BIOS 1502 ) Here is the Dumpfile of the last BSODThanks
Edit:
XMP was always disabled an BIOS remained untouched at default settings
Windows 10 Pro version 20H2 , OS Build 19042.804
G. Skill F4–3200 C16d-16gtzb Trident Z Series 16 Go (2 x 8 Go) 288-pinddr4–3200 MHz
Asus ATX LGA 1151 Motherboard - (Prime Z390-A)
Corsair TX Series TX750M 750W 80 PLUS
Corsair Carbide Series 275R Mid-Tower
Cooler Master Hyper 212 EVO
Seagate BarraCuda 2TB SATA 3.5'' 7200RPM Desktop Hard Drives (ST2000DM008)
Intel Core i5-9600K Coffee Lake 6-Core/6-Thread Processor | Socket LGA 1151, 3.7 GHz Base/ 4.6 GHz Max Turbo Frequency | 95W Gen9 Retail Boxed Unlocked (BX80684I59600K) | (Compatible with 300 series chipset motherboard Only)
GIGABYTE GeForce RTX 2060 OC 6G REV 2.0 GDDR6 | 1755 MHz Boost Clock, 14000 MHz Memory Clock | PCI-E 3.0, 1x HDMI 2.0b, 3x DP1.4 | GV-N2060OC-6GD REV 2.0
Samsung 970 EVO 1TB NVMe M.2 SSD (MZ-V7E1T0BW)

 

[jojesa]

Hello, I had many BSOD in the past year so I decided to reinstall windows in December. Everything was ok until February, I've had two BSOD in less than 24hours. I was either on zoom calls or browsing. (not gaming ) . Had another one last night while on zoom I heard a weird buzz sound and then BSOD again. I turned my pc back on and put the dumpfile on a drive her is the link to my last dump file if someone can pinpoint the issue or point me in a direction it would be appreciated . ( Also could it simply be that I need to update my motherboards Bios (PRIME Z390-A BIOS 1502 ) Here is the Dumpfile of the last BSODThanks

Could you post your system specs (with model #)
-Have you checked or monitored you system temperatures. A system componente overheating could cause that BSOD.
-Try resseting the BIOS to default, since a a misconfiguration in the BIOS could cause the issue.
-What's your RAM model and configuration. Faulty, unstable or misconfigured RAM could also cause that BSOD.
Test your RAM with Memtest86 from a USB flash drive. Disable any overclocking or XMP profile and see if the issue goes away.
-In rare cases a faulty CPU/CPU socket could cause the BSOD.

 

[wass1991]

Thanks for the quick response ,
-Im on a Windows 10 Pro version 20H2 , OS Build 19042.804
I checked my ram with the windows tool but will check with memtest86 now and here is my build
G. Skill F4–3200 C16d-16gtzb Trident Z Series 16 Go (2 x 8 Go) 288-pinddr4–3200 MHz
Asus ATX LGA 1151 Motherboard - (Prime Z390-A)
Corsair TX Series TX750M 750W 80 PLUS
Corsair Carbide Series 275R Mid-Tower
Cooler Master Hyper 212 EVO
Seagate BarraCuda 2TB SATA 3.5'' 7200RPM Desktop Hard Drives (ST2000DM008)
Intel Core i5-9600K Coffee Lake 6-Core/6-Thread Processor | Socket LGA 1151, 3.7 GHz Base/ 4.6 GHz Max Turbo Frequency | 95W Gen9 Retail Boxed Unlocked (BX80684I59600K) | (Compatible with 300 series chipset motherboard Only)
GIGABYTE GeForce RTX 2060 OC 6G REV 2.0 GDDR6 | 1755 MHz Boost Clock, 14000 MHz Memory Clock | PCI-E 3.0, 1x HDMI 2.0b, 3x DP1.4 | GV-N2060OC-6GD REV 2.0
Samsung 970 EVO 1TB NVMe M.2 SSD (MZ-V7E1T0BW)

 

[scout_03]

could you use whocrashed and se what it report in plain text also that buzz sound check if it is not coming from psu .

 

[wass1991]

could you use whocrashed and se what it report in plain text also that buzz sound check if it is not coming from psu .

Here is a screenshot of my whocrashed report and the buzz sound is coming from my headset, not from the physical pc itself.

 

[Colif]

its pointing at intelppm, which is a part of windows used to talk to the cpu.

Have you got latest chipset/Intel Management Engine Interface drivers?
latest version of IMEI if 2nd Feb 2021 - https://www.asus.com/au/Motherboard...ds/All-series/PRIME-Z390-A/HelpDesk_Download/
bios update might help - https://www.asus.com/au/Motherboards-Components/Motherboards/All-series/PRIME-Z390-A/HelpDesk_BIOS/

mind you, MCE errors often point there but since one of the causes in outdated BIOS, its a good place to start.

 

[The Good]

its pointing at intelppm, which is a part of windows used to talk to the cpu.

Have you got latest chipset/Intel Management Engine Interface drivers?
latest version of IMEI if 2nd Feb 2021 - https://www.asus.com/au/Motherboard...ds/All-series/PRIME-Z390-A/HelpDesk_Download/
bios update might help - https://www.asus.com/au/Motherboards-Components/Motherboards/All-series/PRIME-Z390-A/HelpDesk_BIOS/

mind you, MCE errors often point there but since one of the causes in outdated BIOS, its a good place to start.

Perfect, I'll look into this. I am the one that built the system for OP so I have been trying to help him with the issue. Will make sure the BIOS is updated as well as all the Intel drivers. On the other hand, do you happen to know anything about the error due to ntoskrnl.exe? I thought that one might have caused the intelppm failure. With recent weird windows update, I have seen a few BSOD with a crash address pointing ntoskrnl.exe, unless that's just out of coincidence?

 

[jojesa]

...On the other hand, do you happen to know anything about the error due to ntoskrnl.exe? I thought that one might have caused the intelppm failure. With recent weird windows update, I have seen a few BSOD with a crash address pointing ntoskrnl.exe, unless that's just out of coincidence?

When the module: ntoskrnl.exe appears on a BSOD, you should look into the drivers or apps that could be causing it to crash...so it could be that the intelppm coulld be causing the ntoskrnl.exe BSOD.

Configuring your system for a full memory dump will provide more extensive data about the crash.
To configure your system for a full memory dump:
Right-click My Computer, and then click Properties.
Click the Advanced tab, and then under Startup and Recovery, click Settings (or Startup and Recovery).
Under write debugging information select full or complete memory dump.
A reboot might be required.

 

[Colif]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause. Who crashed always sees it as the cause, as it is what crashed. Whocrashed would be more useful if it found why it crashed.

crashes where the process that stopped is ntoskrnl make up about 90% of the crashes I see. What caused it? depends on the BSOD, as Machine Check Exceptions can be hardware or software

I didn't notice the dump files, I will ask a friend to convert them as it might show more than what who crashed is.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/7mvzbnqe/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	020921-13687-01.dmp (Feb 9 2021 - 21:26:58)
Bugcheck:	MACHINE_CHECK_EXCEPTION (9C)
Probably caused by:	memory_corruption (Process: System)
Uptime:	5 Day(s), 8 Hour(s), 26 Min(s), and 18 Sec(s)

Possible Motherboard page: https://www.asus.com/us/Motherboards/PRIME-Z390-A/
There are BIOS updates available for your system. You are using version 1502 and the latest is 1802. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

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

 

[The Good]

Update for everyone:

Work I've done on OP's computer:

System scan (SFC /scannow) found and corrected some corrupted file
Motherboard BIOS was updated to 1802.
Intel MEI was uninstalled (Old Version) and the latest version was successfully installed
Memory Dumps were updated to strictly be complete in the future, rather than automatic
No driver update for other Intel components was found

For now, I think these few steps might ensure that the system is now stable (Hopefully), but at least it will allow us to cross-out some options if it happens again.

 

[Colif]

complete (IE, full memory dumps) might be a problem if he continues to BSOD mainly as the person I ask to check them (gardenman) doesn't have great internet and memory.dmp files can get silly big compared to mini dumps which are much smaller and generally include enough info

No drivers stand out as obvious causes.

 

[The Good]

Alright guys, OP has had other instances of BSOD. I will attach a new link for the newest minidump as well as a screenshot of the whocrashed report.

DMP File: https://drive.google.com/drive/folders/1fXxyl00yxyBF9fVd4bCIsOgBnybVB9rg?usp=sharing

Screenshot: https://drive.google.com/drive/folders/1RNxPyDtuQErVLPZxEirvFHSEIcZ-R7bV?usp=sharing

If someone could teach me how to actually upload images it would be great hahaha. My noob ass never knows how.

 

[gardenman]

You can post images at https://imgur.com/ and it will give you a link that you can use in the forums.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/xb1sgpwe/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	022521-14390-01.dmp (Feb 25 2021 - 10:02:52)
Bugcheck:	MACHINE_CHECK_EXCEPTION (9C)
Probably caused by:	memory_corruption (Process: System)
Uptime:	13 Day(s), 14 Hour(s), 01 Min(s), and 33 Sec(s)

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

 

[Deleted member 14196]

Have you tested with memtest86? Maybe bad ram stick

 

[Colif]

Have you tested with memtest86? Maybe bad ram stick

jojesa already suggested this, op said he would test but not sure if it was done.

Machine check exceptions are really close to WHEA errors except they more commonly software related causes. can still be hardware.
their dump text never tells me anything.
system had been up 13 days at this point so its not like it happens every day.

G. Skill F4–3200 C16d-16gtzb Trident Z Series 16 Go (2 x 8 Go) 288-pinddr4–3200 MHz
Asus ATX LGA 1151 Motherboard - (Prime Z390-A)
Corsair TX Series TX750M 750W 80 PLUS
Corsair Carbide Series 275R Mid-Tower
Cooler Master Hyper 212 EVO
Seagate BarraCuda 2TB SATA 3.5'' 7200RPM Desktop Hard Drives (ST2000DM008)
Intel Core i5-9600K
GIGABYTE GeForce RTX 2060 OC 6G REV 2.0 GDDR6
Samsung 970 EVO 1TB NVMe M.2 SSD (MZ-V7E1T0BW)

Ram - memtest run?
storage - https://www.seagate.com/au/en/support/downloads/seatools/seatools-win-master/
CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool
GPU? well, you run bechmarks and see if you BSOD during them
don't run both at once
https://geeks3d.com/furmark/
https://benchmark.unigine.com/heaven

That just leaves PSU & MB which are less easy to test. No real tests for motherboard, you hope you find cause before this, as only real way to know is by swapping all your hardware onto another mb and not many of us have spares. At this stage I would get PC looked at by a shop that has spares they can swap in and test parts.

Could also be something you attach to PC so mice. keyboards, speakers, external hdd, vr gear, etc.

 

[The Good]

Thanks for you reply everyone. We only ran the standard microsoft RAM test tool but we need to run MEMTEST86 since it is much more thorough.

My only question about MEMTEST86 is do you only do it with 1 RAM stick at a time, or can you test both at the same time. I hear people saying you could do either, but I want to do it properly.

I will test back all the other hardware and update with the results.

 

[Colif]

1 stick at a time, as if you test with mutiple and get an error, you don't know which stick is at fault. Saves time in long run to do 1 at a time.

 

[The Good]

Perfect thank you. I really hope its not Motherboard, PSU or peripherals cause then its a PITA to diagnostic.

 

[Colif]

PSU only really reliable test is a multimeter,
other methods are
the paper clip method - https://forums.tomshardware.com/threads/what-is-the-paperclip-method-of-testing-a-psu.1336402/
or in the BIOS to check the +3.3V, +5V, and +12V. - https://www.lifewire.com/power-supply-voltage-tolerances-2624583

but neither of last 2 can check PSU under load.

any new dumps he gets might show us the way too.

 

[The Good]

PSU only really reliable test is a multimeter,
other methods are
the paper clip method - https://forums.tomshardware.com/threads/what-is-the-paperclip-method-of-testing-a-psu.1336402/
or in the BIOS to check the +3.3V, +5V, and +12V. - https://www.lifewire.com/power-supply-voltage-tolerances-2624583

but neither of last 2 can check PSU under load.

any new dumps he gets might show us the way too.

What would one do with the multimeter? Find the positive and ground pin on certain connect and probe them while the PSU is plugged?

 

[Colif]

good question

See part 2, number 4 here - https://www.wikihow.com/Check-a-Power-Supply

https://smallbusiness.chron.com/test-computer-power-supply-using-voltmeter-70580.html

It is always good practice to test a power supply before using it for the first time. The example below will show how to test a power supply with positive polarity. If you have a negative polarity power supply, then you will get a negative reading. You should then switch the position of the multimeter probes.

1. Plug your power supply into an AC outlet.
2. Red probe goes into the tip
   Black probe touches the barrel as shown in Figure 5.
3. Turn on your multimeter and set it to read DC voltage.
4. Take the red (positive) probe from your multimeter and stick it into the end of the power supply plug.
5. Take the black (negative) probe from your multimeter and carefully touch it against the barrel of the plug without touching the tip or your red probe. If you make a connection, you will be creating a short circuit.
6. On your multimeter you should see a reading of the voltage coming from your power supply. If you are checking a 12V power supply and your multimeter shows “12.56V” everything is fine and dandy as shown in Figure 6. If you get a reading of “-12.56V” then your probes are attached in reverse. If this happens and you are positive you connected your probes correctly, double check the polarity on your power supply’s label and make sure the circuit you will be powering with this unit is designed to handle this polarity.

If the voltage showing on your multimeter is more than half a volt or a volt off its rating, then you most likely have what is called an unregulated power supply. The 12V Jameco power supply we used in this example is a regulated one, so that is why the voltage we received was so close to the voltage it was rated for.

https://itp.nyu.edu/physcomp/lessons/electronics/understanding-dc-power-supplies/

How to Test a Power Supply Using a Multimeter (14 Steps) - FabatHome

If you have a multimeter at hand, testing a power supply is a rather easy job. We help you do that in a matter of minutes in a bunch of easy to follow steps.

www.fabathome.net