M
mosfetsforabrain
I hate headscratchers, but it looks like this is one.
I built my new PC a few days ago now, and for the first day it's been working fine, however yesterday it started throwing BSOD errors, and they have continued into today.
The newest bug check code is 0x00000101, for which I attached the minidump file. However, the first two were both 0x00000133, followed by a 0x00000050 and then for good measure a 0x0000001e. All of these pointed to the windows kernel ntoskrnl.exe, and the first and last also referenced hal.dll.
It should be noted that the first two occurred on a mild overclock of my 9900k using the overclocking tool provided by my motherboard manufacturer, easytune (it's a gigabyte board). This software provided what looked like a mild overclock of 5.2 ghz all cores, but with no voltage increase. I initially assumed the BSOD were caused by the CPU not having enough voltage to sustain the clock, but after I disabled the overclock and set the processor back to factory defaults the BSOD's continued, now throwing different codes. Temp on all cores never exceeded 42 degrees Celsius on the overclock. Memory was and still is running to xmp profile rated spec.
To compound onto this, the first BSOD was thrown while windows was newly formatting my HDD secondary drive. I have also noticed a weird behavior with my USB drive as well. When I plug it into my computer, it is identified as a local disk, and windows doesn't give an option to eject it in file explorer or on the taskbar. When I plug the same drive into my laptop, it is also identified as a local disk, doesn't give the ability to eject in file explorer, but does give the ability to eject on the taskbar. I only noticed this behavior after the first BSOD and the failure of the HDD to be formatted.
The only other concurrent thing to these first errors being through was the installation of Logitech gaming software, which is running concurrent with corsair iCUE and Malwarebytes. These initial errors were thrown when the above mentioned USB drive was plugged in and being accessed, but the newer erros, including the 0x00000101 were thrown without it plugged in.
As for the diagnostics I've done up to now, I have completed both a windows memtest and a chkdsk with no errors or issues detected. I've also checked a good portion of problematic drivers in device manager, and all of them are up to date according to windows (I crosschecked this with my motherboard manufacturers website, and found newer dated drivers there however, let me know if this would be the next logical troubleshooting step). After seeing the first few BSODs I updated my graphics card driver as well, but this has seemingly not changed anything as evidenced by the further BSODs. Finally, the motherboard BIOS is up to date, as I updated it to the latest revision before installing windows. After posting this I'm going to run memtest86+ for a few hours to see if that finds anything.
As this is a new PC, I have no issues with doing a clean reinstall of windows. However, I figured I should troubleshoot as much as possible before doing that in case there is another underlying problem/incompatibility.
Here is the most recent minidump file: 020519-5578-01.7z
Other BSOD's are gone from minidump, nut please let me know if you'd like to see the memory.dmp file capturing them all as well.
Continue reading...
I built my new PC a few days ago now, and for the first day it's been working fine, however yesterday it started throwing BSOD errors, and they have continued into today.
The newest bug check code is 0x00000101, for which I attached the minidump file. However, the first two were both 0x00000133, followed by a 0x00000050 and then for good measure a 0x0000001e. All of these pointed to the windows kernel ntoskrnl.exe, and the first and last also referenced hal.dll.
It should be noted that the first two occurred on a mild overclock of my 9900k using the overclocking tool provided by my motherboard manufacturer, easytune (it's a gigabyte board). This software provided what looked like a mild overclock of 5.2 ghz all cores, but with no voltage increase. I initially assumed the BSOD were caused by the CPU not having enough voltage to sustain the clock, but after I disabled the overclock and set the processor back to factory defaults the BSOD's continued, now throwing different codes. Temp on all cores never exceeded 42 degrees Celsius on the overclock. Memory was and still is running to xmp profile rated spec.
To compound onto this, the first BSOD was thrown while windows was newly formatting my HDD secondary drive. I have also noticed a weird behavior with my USB drive as well. When I plug it into my computer, it is identified as a local disk, and windows doesn't give an option to eject it in file explorer or on the taskbar. When I plug the same drive into my laptop, it is also identified as a local disk, doesn't give the ability to eject in file explorer, but does give the ability to eject on the taskbar. I only noticed this behavior after the first BSOD and the failure of the HDD to be formatted.
The only other concurrent thing to these first errors being through was the installation of Logitech gaming software, which is running concurrent with corsair iCUE and Malwarebytes. These initial errors were thrown when the above mentioned USB drive was plugged in and being accessed, but the newer erros, including the 0x00000101 were thrown without it plugged in.
As for the diagnostics I've done up to now, I have completed both a windows memtest and a chkdsk with no errors or issues detected. I've also checked a good portion of problematic drivers in device manager, and all of them are up to date according to windows (I crosschecked this with my motherboard manufacturers website, and found newer dated drivers there however, let me know if this would be the next logical troubleshooting step). After seeing the first few BSODs I updated my graphics card driver as well, but this has seemingly not changed anything as evidenced by the further BSODs. Finally, the motherboard BIOS is up to date, as I updated it to the latest revision before installing windows. After posting this I'm going to run memtest86+ for a few hours to see if that finds anything.
As this is a new PC, I have no issues with doing a clean reinstall of windows. However, I figured I should troubleshoot as much as possible before doing that in case there is another underlying problem/incompatibility.
Here is the most recent minidump file: 020519-5578-01.7z
Other BSOD's are gone from minidump, nut please let me know if you'd like to see the memory.dmp file capturing them all as well.
Continue reading...