[SOLVED] Continuous blue screens out of nowhere

[Cesty]

Right, I've been getting blue screens for a while now and I've reinstalled Windows 3 times but it's still happening.
Link to 2 recent minidumps: https://drive.google.com/file/d/1XG99mXyam3JopNHeYIxnfZRXfn56rV2a/view?usp=sharing
Specs: Asus TUF B360-plus gaming motherboard, 16gb Kingston HyperX Fury, DDR4 3200MHz, CL18 ram, i5-9400f processor and asus rtx 2060 dual gpu.

 

[Cesty]

WHEA errors never tell me anything so I wasn't expecting anything

I have no idea what this is/does

Jan 30 2013

hswultpep.sys

Intel Processor Line Power Engine Plug-in driver

Intel Core 4xxxU and 4xxxY Processor Line Power Engine Plug-in driver
2013, thats more likely for my last CPU (4690K) than a CPU made in 2019
Only download sites I see it available aren't official Intel ones.

When you put windows back on, do you download drivers from Asus website? where do you get the drivers from?

First 2 times I just let windows do it's thing automatically so I didn't download any drivers apart from gpu drivers. I guess Logitech drivers for my mouse and headset came with Logitech g hub but I don't have that downloaded atm so no drivers there again downloaded by me. Mostly windows automatically doing its thing atm.

Right now on my 3rd reinstall I downloaded all drivers from the motherboard website also.

 

[Uncodable]

Hello Cesty,

I would like to make it clear that I will not be able to help you at times, as I have tons of school work to do always. Does not mean hesitate to ask me questions, as either I, or someone else, will answer them.

First 2 times I just let windows do it's thing automatically so I didn't download any drivers apart from gpu drivers. I guess Logitech drivers for my mouse and headset came with Logitech g hub but I don't have that downloaded atm so no drivers there again downloaded by me. Mostly windows automatically doing its thing atm.

Right now on my 3rd reinstall I downloaded all drivers from the motherboard website also.

First things first, you stated that you had Windows automatically install the drivers. A common, nearly cliché fix would be to update the device drivers. If they're up to date, downgrade to earlier versions.

Yeah, can't for some reason to do it. I'll just run memtest and wait for the minidumps to be scanned.

If all sticks pass the test, you can try re-running the test. I personally would re-run it to be sure.

From the dumps you posted, it does not really seem to be RAM. If it were to be RAM, the dumps would be far more sporadic (different bug checks all together), and the dumps would actually blame programs instead of the usual 'System'. I also do not want to consider RAM the problem, as that WHEA bug check you received earlier blamed an Intel driver. Let me provide you with a few solutions that have helped people in the past:

1) Check if the CPU's voltage is stock. Overvolting the CPU could cause overheating, which can in turn cause bug checks. Alongside overvolting, check to ensure your CPU fan is performing as it should. I do not know the exact details behind overheating causing bug checks, but this is something to consider. In addition, undervolting your CPU can actually cause single bit flips, which is enough to take down an entire system with a blue screen. Check the specifications for your CPU and ensure that the voltages are set properly.

2) Check if you are overclocking. Speeding up any hardware above their specifications can cause issues. The issues are dependent on the hardware being overclocked. If you are overclocking, reset the overclocked speeds.

As goes for overclocking, I should state that you should reset all overclocks that you performed on your PC.

 

[Uncodable]

WHEA errors never tell me anything so I wasn't expecting anything

I have no idea what this is/does

Jan 30 2013

hswultpep.sys

Intel Processor Line Power Engine Plug-in driver

Intel Core 4xxxU and 4xxxY Processor Line Power Engine Plug-in driver
2013, thats more likely for my last CPU (4690K) than a CPU made in 2019
Only download sites I see it available aren't official Intel ones.

When you put windows back on, do you download drivers from Asus website? where do you get the drivers from?

As a simple pro-tip, WHEA errors will almost always indicate a hardware problem, hence the abbreviation's expanded form, Windows Hardware Error Architecture.

 

[Cesty]

I'll check the voltages for sure, I haven't overclocked any component after the first reinstall to make sure it's not about those.

And I've upgraded my drivers as best as I can, but don't really have the experience nor the knowledge to downgrade earlier versions

 

[Colif]

I know what WHEA is, and what can cause them, what I mean is the dump text is almost always the same. it is very rare for it to mention a driver name.
they are often like his

STACK_TEXT:
ffff848122e9b8e8 fffff807760b39aa : 0000000000000124 0000000000000000 ffffa88506ee8028 00000000f6000080 : nt!KeBugCheckEx
ffff848122e9b8f0 fffff807727315b0 : 0000000000000000 ffffa88506ee8028 ffffa8850299d7f0 ffffa88506ee8028 : nt!HalBugCheckSystem+0xca
ffff848122e9b930 fffff807761b552e : 0000000000000000 ffff848122e9b9d9 ffffa88506ee8028 ffffa8850299d7f0 : PSHED!PshedBugCheckSystem+0x10
ffff848122e9b960 fffff807760b52d1 : ffffa88506ee64c0 ffffa88506ee64c0 ffffa8850299d840 ffffa8850299d7f0 : nt!WheaReportHwError+0x46e
ffff848122e9ba40 fffff807760b5643 : 0000000000000005 ffffa8850299d840 ffffa8850299d7f0 0000000000000005 : nt!HalpMcaReportError+0xb1
ffff848122e9bbb0 fffff807760b5520 : ffffa885026e7d28 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandlerCore+0xef
ffff848122e9bc00 fffff807760b5771 : 0000000000000006 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffff848122e9bc40 fffff807760b49db : 0000000000000000 0000000000000000 ffff848122e9bed0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff848122e9bc70 fffff807760b7225 : ffffa885026e7d28 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x5f
ffff848122e9bca0 fffff8077610c959 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
ffff848122e9bcd0 fffff80776004bfa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffff848122e9bd00 fffff807760048b7 : ffffa88500000000 fffff807760047ec ffffa885029b6000 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff848122e9be40 fffff80775e08197 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
ffff848122e7fdd0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!EtwpReserveTraceBuffer+0x137

not a lot of helpful info in it.

WHEA also doesn't mean its an auto hardware problem, it can be device drivers.
his other 4 BSOD could be drivers or hardware too.

but after 3 recent installs of Win 10 I won't argue that this looks like hardware.

 

[Uncodable]

I know what WHEA is, and what can cause them, what I mean is the dump text is almost always the same. it is very rare for it to mention a driver name.
they are often like his

STACK_TEXT:
ffff848122e9b8e8 fffff807760b39aa : 0000000000000124 0000000000000000 ffffa88506ee8028 00000000f6000080 : nt!KeBugCheckEx
ffff848122e9b8f0 fffff807727315b0 : 0000000000000000 ffffa88506ee8028 ffffa8850299d7f0 ffffa88506ee8028 : nt!HalBugCheckSystem+0xca
ffff848122e9b930 fffff807761b552e : 0000000000000000 ffff848122e9b9d9 ffffa88506ee8028 ffffa8850299d7f0 : PSHED!PshedBugCheckSystem+0x10
ffff848122e9b960 fffff807760b52d1 : ffffa88506ee64c0 ffffa88506ee64c0 ffffa8850299d840 ffffa8850299d7f0 : nt!WheaReportHwError+0x46e
ffff848122e9ba40 fffff807760b5643 : 0000000000000005 ffffa8850299d840 ffffa8850299d7f0 0000000000000005 : nt!HalpMcaReportError+0xb1
ffff848122e9bbb0 fffff807760b5520 : ffffa885026e7d28 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandlerCore+0xef
ffff848122e9bc00 fffff807760b5771 : 0000000000000006 0000000000000001 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffff848122e9bc40 fffff807760b49db : 0000000000000000 0000000000000000 ffff848122e9bed0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff848122e9bc70 fffff807760b7225 : ffffa885026e7d28 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0x5f
ffff848122e9bca0 fffff8077610c959 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
ffff848122e9bcd0 fffff80776004bfa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffff848122e9bd00 fffff807760048b7 : ffffa88500000000 fffff807760047ec ffffa885029b6000 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff848122e9be40 fffff80775e08197 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
ffff848122e7fdd0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!EtwpReserveTraceBuffer+0x137

not a lot of helpful info in it.

WHEA also doesn't mean its an auto hardware problem, it can be device drivers.
his other 4 BSOD could be drivers or hardware too.

but after 3 recent installs of Win 10 I won't argue that this looks like hardware.

I've only ever encountered WHEA errors when there was a hardware problem. I do agree though, that the stack traces are rarely ever helpful.

 

[Colif]

sometimes you see a driver name, its why I ask for them. And it helps to see what drivers are running as WHEA could be caused by his

Aug 22 2012

AsIO.sys

ASUS Input Output driver http://www.asus.com/

driver as its part of AI Suite which can be used to software overclock PC. If you have AI suite installed, I would remove it
it helps to see what is on PC.
Problem is windows update will install that driver on any Asus mb so I had it on my last PC even without looking for Asus drivers.

I don't know what that old Intel driver does I showed before, it seems out of place

I don't see anything out of place. and the other 4 dumps don't show any clues I recognise.

 

[Uncodable]

I'll check the voltages for sure, I haven't overclocked any component after the first reinstall to make sure it's not about those.

And I've upgraded my drivers as best as I can, but don't really have the experience nor the knowledge to downgrade earlier versions

Quick note, I will be heading to bed here shortly. I can possibly help you tomorrow, though.

Anyway, to downgrade to earlier versions of device drivers, you can usually search the hardware vendor's website (you can find this by simply searching the vendor name) and find the drivers on there. On some websites, they usually have a tab that says something along the lines of "Software and Drivers," otherwise you may have to browse around a bit. There will be times where you do have to download device drivers from other sources. Just ensure that they are the correct drivers, and that they are not malicious. You can usually, easily tell if a driver is legitimate by the digital signature alone.

So fulle specs:
MB: AsusTUF B360-PLUS GAMING
RAM: Kingston 16GB (2 x 8GB) HyperX Fury, DDR4 3200MHz, CL18
Processor: Intel Coffee Lake Core i5-9400F
GPU: AsusGeForce RTX 2060 DUAL OC EVO
SSD1 (boot drive): Intel 512GB 660p series M.2 NVMe
SSD2: Intel1TB 660p series M.2 NVMe
PSU: Seasonic 620W M12II-620 Evolution
OS: Windows 10 Home Build: 19042.804

No Wifi cards, and I've had this gpu before the blue screens appeared, but I can test with my old RX 580 to see if it is the gpu

EDIT: Yeah, I have installed the latest BIOS, didn't do much though.

Though, I'm not going to just leave you here to find the links yourself, that would quite frankly be rude of me.
NVidia's website: https://www.nvidia.com/Download/Find.aspx?lang=en-us (shows all driver versions)
Intel's website: https://downloadcenter.intel.com/pr...0p-Series-512GB-M-2-80mm-PCIe-3-0-x4-3D2-QLC- (couldn't really find a link that shows all the driver versions)

I wasn't able to find drivers for the CPU, but I will update you if I do find them.

 

[Uncodable]

WHEA errors never tell me anything so I wasn't expecting anything

I have no idea what this is/does

Jan 30 2013

hswultpep.sys

Intel Processor Line Power Engine Plug-in driver

Intel Core 4xxxU and 4xxxY Processor Line Power Engine Plug-in driver
2013, thats more likely for my last CPU (4690K) than a CPU made in 2019
Only download sites I see it available aren't official Intel ones.

When you put windows back on, do you download drivers from Asus website? where do you get the drivers from?

Looks like a driver that Windows automatically installs. Couldn't find anything on it, besides the typical "Intel Core 4xxxU and 4xxxY Processor Line Power Engine Plug-in driver" like you said. Do you think he could remove the driver manually without problems?

 

[Colif]

try stopping it from running at startup, see if that makes any difference. I think you can also uninstall it using this but just stop it for now. If any application uses the driver, it can start it. This just stops it running at start up = https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

 

[Cesty]

try stopping it from running at startup, see if that makes any difference. I think you can also uninstall it using this but just stop it for now. If any application uses the driver, it can start it. This just stops it running at start up = https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

Can I somehow know if any application starts it?
I know how to make my pc blue screen lol. So I was just wondering it'd be helpful to know if that driver is the cause.

 

[Cesty]

As of now, I disabled it on boot in the application and shortly after I got into a game of apex legends. Sure enough, I got a bsod and when restarting, in the windows login screen all of my usb ports stop working. I can get into bios but when in the login screen, can't do anything.

Can't really do anything now, maybe reinstall windows for the 4th time

 

[white.a.drew]

I only have one 2060, the model of the 2060 is "Asus rtx 2060 dual evo oc"

And I got the psu same time as almost every part, at the beginning of summer of 2019.

Sorry i knew that when posting i didnt relize my device still had left over from previous reply i was working on.... It maybe be a faulty psu.... If you got it on amazon around the times i've been looking at... It looks like this psu has had a few bad batches.... Their good psu's from what im reading but there are the's random drops in reveiws where it's as though a bad batch keeps making it's way back onnthe shelf.

 

[Colif]

i did just say it stops it running at start up, and if any program needed it, it could load it. So the bsod isn't much proof that it isn't cause

Can I somehow know if any application starts it?

Yes
you can run this and set it up to track what uses the process - https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
it also may not be cause, I was just pointing out drivers I saw as unusual. I see a lot of dumps, you get to know the names of drivers, and it isn't one I have seen before/recently. Unknown drivers can often be the cause.

Forums have a terrible habit of remembering what you had typed but may not have hit enter on. you can wipe it using the draft button, the 2nd last button in the row with all the formatting choices.

 

[Cesty]

I think my pc is stable. What I did was disable the asus driver you found, with the app. I've got no idea what it did, but seems like everything is normal now.

 

[white.a.drew]

I think my pc is stable. What I did was disable the asus driver you found, with the app. I've got no idea what it did, but seems like everything is normal now.

Thats your issue... Omg imnso sorry i didnt catch this otherwise i would have told you right off the bat...... Like i tell everyone wanting help building pc's asus all the ASUS IS MY LOVE FOR ALL THINGS PC...... issue being though.... NEVER EVER EVER NEVER USE THERY'RE STUPID SELF HELP APPS THEY ARE THE BIGGEST BIGGEST BUGS IN ANY SYSTEM........ asus grid armoury all of it.... Never use they're **** apps.... You need a driver or any of that.... Goto the website and download it yourself.

 

[Colif]

ASio.sys is often installed by Windows as its part of a pack Asus give Microsoft for their motherboards, it used to be called AMD and I always wondered why Windows was installing that on my intel machine. It dawned on me at some stage that it stands for Asus Motherboard Drivers.
I had it on my last PC and I know I didn't install any Asus applications

To be fair, most motherboard maker apps are best being avoided. You don't need them.

 

[Cesty]

Really don't know what to mark as the best answer, maybe the post where you pointed out the asus driver?
Also, I did not install the asus ai suite, Windows installed it automatically if anything.

 

[Colif]

if that was the one that fixed it, I would. Its known to cause them as it can change hardware values. Its used to change fan and cpu speeds. also used to monitor temperatures.

 

[Uncodable]

if that was the one that fixed it, I would. Its known to cause them as it can change hardware values. Its used to change fan and cpu speeds. also used to monitor temperatures.

Also the fact that the driver is known to be prone to vulnerabilities. I discovered vulnerabilities in Asus' drivers before, in particular that same driver. For you Cesty, take this as another reason to remove the device driver from your machine.