Logon screen problem

Topic

New Reply

This problem started some months back.  I would return to my desktop computer and the logon input screen would be locked.  Keyboard entry or moving mouse got no response.  The only solution was to hard reboot.

When I did that and returned to the logon screen, intermittently, it would refresh every few seconds, which was too fast for me to enter my Windows password that was 13 chars long.  Up until yesterday (12/15, the Ides of December) another reboot would fix this problem, until it didn’t.

As this began to happen more frequently, I looked through the event logs for some clues and discovered many instances of this entry:

Log Name: Application
Source: Application Error
Date: 12/16/2021 9:57:32 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: pc-03222015
Description:
Faulting application name: LogonUI.exe, version: 10.0.19041.1, time stamp: 0xc08a5452
Faulting module name: USBKeyCredentialProvider.dll_unloaded, version: 0.0.0.0, time stamp: 0x53d9fa55
Exception code: 0xc0000005
Fault offset: 0x000000000002b4a8
Faulting process id: 0xdd8
Faulting application start time: 0x01d7f26089892ecb
Faulting application path: C:\WINDOWS\system32\LogonUI.exe
Faulting module path: USBKeyCredentialProvider.dll
Report Id: 70fe25be-f782-410e-a70e-91bd79e9be0a
Faulting package full name:
Faulting package-relative application ID:

So I did some research on LogonUI.exe errors via Google , which of course produced all kinds of useless clickbait hits.

A couple of weeks back I updated to Win10 21H2 in the hopes that might fix the problem but it didn’t.

Back to Google and saw that some entries pointed to video card issues and given the input problems and the flashing logon screen, I decided to try some changes in that area.

I tried looking for video driver updates but MS says nothing was available.  I next decided to try and install the native Nvidia driver but that didn’t fix the issue.

After rebooting from the driver install, I again got the periodic flashing logon screen loop but this time, there was no way to get out of it, no matter how many times I pressed various  keys like ENTER.

Later when I managed to get back into the system, I discovered that each [frustrated] enter key push results in a new LogonUI event log error.  A possible helpful clue?

So next, I switched to the onboard Intel video.  Still couldn’t logon due to inability to enter my longish password before a screen refresh occurred.

Here’s a link to show what I was experiencing:

https://drive.google.com/file/d/1JxVn0gTFYe0tUaGw2q4fdg3Z8vxkTshU/view?usp=sharing

Next I logged into the Admin account with the brainstorm that I could eliminate the logon password for now, which should allow me to get back into the desktop and hopefully search/find a solution.

However, when I looked into this, I discovered that when I did this (or shorten the password, as I ultimately chose to do), I lose all EFS-Encrypted files (don’t have any), personal certs and passwords for websites and network resources!  Damn.  Is this really necessary Microsoft?

But with no other options that I could think of, I changed the account password to a single char, which should give me time to enter it before the logon screen flashes and was then able to logon to my main account of this desktop system, where I am typing this from now.

Does anyone have any ideas on what else I might try short of a system refresh?

————-
Running: Old ASRock z97 Extreme 6 mobo
16GB DDR3 RAM
Nvidia GTX750 video card
I7-4790K CPU
Win10 21H2 on an SSD
Plenty of free drive space

Reply | Quote

Replies

Are you doing any overclocking or anything like that?

Susan Bradley Patch Lady

Reply | Quote

https://www.nvidia.com/en-us/geforce/drivers/
Go there and do a manual search for GTX 750 drivers.
I see some dated in December? https://www.nvidia.com/en-us/drivers/results/184003/
Release Date:Wed Dec 01, 2021

Susan Bradley Patch Lady

Reply | Quote

Susan Bradley wrote:

Are you doing any overclocking or anything like that?

Nope.

Reply | Quote

Susan Bradley wrote:

https://www.nvidia.com/en-us/geforce/drivers/
Go there and do a manual search for GTX 750 drivers.
I see some dated in December? https://www.nvidia.com/en-us/drivers/results/184003/
Release Date:Wed Dec 01, 2021

Yes, I did put in the latest Nvidia driver but it didn’t make any difference.

Right now, I am running off of the onboard Intel video.  I have also removed the logon screen background image just in case that has anything to do with the issue.

Reply | Quote

https://www.asrock.com/mb/Intel/Z97%20Extreme6/#BIOS
Disabled the spector/meltdown stuff?
https://www.grc.com/inspectre.htm

Susan Bradley Patch Lady

Reply | Quote

Susan Bradley wrote:

https://www.asrock.com/mb/Intel/Z97%20Extreme6/#BIOS
Disabled the spector/meltdown stuff?
https://www.grc.com/inspectre.htm

I’ve got the 2.80 BIOS, which is the last produced for this mobo.

I also recently did a scan for driver updates and applied any said to be downlevel using:
https://sdi-tool.org/

Ran the Spectre utility and see:

Spectre & Meltdown Vulnerability Status

System is Meltdown protected: YES
System is Spectre protected: YES
Microcode Update Available: YES
Performance: GOOD
CPUID: 306C3

I just took a look at the event log records and see that when I first logged on Thursday morning, I got the LogonUI error (above).  But subsequently throughout the day when I left and came back to the system and also had to log back on, there are no further such errors.  I wonder why I wouldn’t get a similar error record each logon attempt?  Let’s see what tomorrow brings.

Reply | Quote

I would disable the spectre/meltdown patches.

Susan Bradley Patch Lady

Reply | Quote

Could this be a side effect if Windows Hello became enabled inadvertently and perceived its settings as logging in with a  USB key containing the credentials as per the following?

https://support.microsoft.com/en-us/windows/sign-in-to-your-microsoft-account-with-windows-hello-or-a-security-key-800a8c01-6b61-49f5-0660-c2159bea4d84

If so (assuming the requisite bitlocker key is available) it might be possible to remove hello from the image from the recovery console to get around the problem, or remove the problem updates.. though sue to the way patching is done the list from dism /image:c: /get-packages is uselessly short where the program goes back months..

I found this: https://answers.microsoft.com/en-us/windows/forum/all/how-to-disable-windows-hello/05ab5492-19c7-4d44-b762-d93b44a9cf65

So basically something like

reg load HKLM\test c:\windows\system32\config\system

and changing the relevant entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\Settings\AllowSignInOptions

now mapped  by the above to

HKEY_LOCAL_MACHINE\test\Microsoft\PolicyManager\default\Settings\AllowSignInOptions

in the recovery console could help – remember you back up the registry by copying the (system) file elsewhere first, as the recovery console registry is NOT your installed OS registry..

and finally but probably most importantly..

reg unload HKLM\test

reboot and hope.. No promises..

I guess while you’re at it you could also dump in the insecure autologin registry settings using the same methodology so if it didn’t work the login might be bypassed..

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
“AutoAdminLogon”=”1”
“DefaultUserName”=”[account_name]”
“DefaultPassword”=”plain_text_password”

(so HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows would present at HKEY_LOCAL_MACHINE\test\Microsoft\Windows NT\CurrentVersion\Winlogon…)

Reply | Quote

I don’t use Bitlocker at all.  Never even set it up.

However, I have been focusing on the Winlogon part of the error, when perhaps the USB part is more germane.  This morning I ran this search:

Faulting module name: USBKeyCredentialProvider.dll_unloaded, version: 0.0.0.0, time stamp: 0x53d9fa55 Exception code: 0xc0000005

and got what look like some useful entries that I need to plow through later.

One guy had a similar problem, which he ID’d eventually as a bad slot on his ASRock mobo that the video card was in.

Something to do with USB seems possible because this board definitely has USB problems.  A couple of ports no longer work.

USB ports are occupied by:

• Two printers
• An old touchpad mouse from Cirque, which has been known to cause problems where now and then I have to unplug it and replug it to make it stop jumping all over the screen.  Cirque gave up the consumer touchpad business a few years back, so there is no support from them.
• Keyboard (I’ve tried others, didn’t have any effect on the issue)
• A set of headphones
• A USB cable used to connect portable backup drives on a weekly basis

There are also some USB settings in the BIOS that I have futzed with like enabling “legacy support” that I will set back to the defaults.

4.4.9 USB Configuration

USB Controller – Enable or disable all the USB ports.

Intel USB 3.0 Mode – Select Intel® USB 3.0 controller mode. Set [Smart Auto] to keep the USB 3.0 driver enabled after rebooting (USB 3.0 is enabled in BIOS). Set [Auto] to automatically enable the USB 3.0 driver after entering the OS (USB 3.0 is disabled in BIOS). Set [Enabled] to keep the USB 3.0 driver enabled (Must install driver to use USB devices under Windows® 7). Set [Disabled] to disable the USB 3.0 ports.

Legacy USB Support – Enable or disable Legacy OS Support for USB 2.0 devices. If you encounter USB compatibility issues it is recommended to disable legacy USB support. Select UEFI Setup Only to support USB devices under the UEFI setup and Windows/Linux operating systems only.

Legacy USB 3.0 Support – Enable or disable Legacy OS Support for USB 3.0 devices. If you encounter USB compatibility issues it is recommended to disable legacy USB support. Select UEFI Setup Only to support USB devices under the UEFI setup and Windows/Linux operating systems only.

USB Compatibility Patch – If your USB devices (i.e. USB mouse or storage) encounter compatibility problems, please enable this option to ix it. Please note that after enabling this option, it is normal that the system will postpone booting up after pressing the power button.

Third Party USB 3.0 Controller – Enable or disable all of the USB 3.0 ports controlled by third Party chips.

Does anyone know if this “Exception code: 0xc0000005” tells us anything?  Is there a list of such codes relative to this module?

 

Reply | Quote

What if you unplug the mouse and leave it out?

Susan Bradley Patch Lady

Reply | Quote

sorry, forgot to note the example given in previous post  would be from recovery console command prompt..

If you get a password prompt to get to the recovery command prompt (unusual, but not impossible) then you’ll have to get someone to make you a PE disk and via that mount the bitlocker volume manually with manage-BDE at which point things get a bit complicated.. using another installation to do the same should work, but can leave a trail of registry permissions pain you won’t want (or maybe even can’t fix), though at least the regini in line documentation is now suitable..

Reply | Quote

Firstly, has a

SFC /verifyonly

been done from admin cmd prompt recently?
If it does display integrity violations then I would open a PS as admin and try the following:

DISM /online /cleanup-image /restorehealth

then reboot the system.
If the system still displays this erroneous/ weird behaviour, then try the above posted methods to rectify. OS Foundation work 1st IMO 😉

Keeping IT Lean, Clean and Mean!

Reply | Quote

Microfix wrote:

Firstly, has a

SFC /verifyonly

been done from admin cmd prompt recently?
If it does display integrity violations then I would open a PS as admin and try the following:

DISM /online /cleanup-image /restorehealth

then reboot the system.
If the system still displays this erroneous/ weird behaviour, then try the above posted methods to rectify. OS Foundation work 1st IMO 😉

Yes did both of those a few days aback.  Didn’t help.

Reply | Quote

It’s looking like you need to set the BIOS back as it was and give MDsched,exe and crystaldiskinfo a go to be sure the “foundations” are sound (as the machine was when it worked, anyway) and then collect the logs from a recovery command prompt if needs be c:\Windows\System32\winevt\Logs\Application.evtx, c:\Windows\System32\winevt\Logs\System.evtx

They should open on another machine.. in event viewer obvs. – they will show at the bottom of the tree after some delay. Right click and delete to remove them from the view when done.

My thoughts are

Protection product starting and killing a login process it considers infected.

Problem with the user profile or user profile service

Problem with the GINA system – linked to WiFi often – see

https://docs.microsoft.com/en-us/windows/win32/secauthn/winlogon-and-gina

All these things should leave evidence in the logs…

Also suggest you check the default hive (c:\users\default\NTUSER.DAT) and the equivalent hive in your account are both hidden and NOT read only as that can pretty mess things up and they sit protected only by their hidden and system attributes in their folders.

Versions back we found setting the former read only was in a way a subtle security measure, as it prevented the user profile service from initialising new accounts (local or domain) so you could limit the use of a machine to those who had already used it without any obvious scripts or policies to give a clue as to how it was done (oops..). I’m guessing Microsoft have fixed that but perhaps nobody noticed that as an effect? Haven’t tried this decade..

 

Reply | Quote

Exception code: 0xc0000005 points to process corruption which can be caused by many different things (i.e. defective device, corrupt S/W, defective memory, defective drive, incorrect device/hardware config, etc., etc.)

You indicated you already ran SFC and DISM with no problems found so that pretty much leaves either defective H/W or a driver for the H/W as the problem.

First off, since the problem “appears” to be related to the USB ports, unplug all your USB devices (except the mouse and keyboard), reboot, and see if the problem disappears.

If it does, plug each USB device back in “one-at-a-time“, reboot, and check whether the problem comes back.

Once you isolate the specific device that’s causing your problem, see changing the USB cord or updating the driver fixes things. If it doesn’t, then it’s time to replace whatever it is.

BTW, on my ASUS motherboard I had to set the “legacy USB support” in BIOS to enabled to get my older USB devices to work properly (of course, YMMV.)

If the problem persist with the other USB devices unplugged and isn’t your mouse (you indicated you already eliminated the keyboard), then it’s being caused by something else and I’d suggest a full memory test as the next step to eliminate that as a possible cause (I’d recommend the free MemTest86 tool.)

If the memory tests OK, then proceed to a checking your internal drives.

If the drive is an HDD, use Windows chkdsk.

If the drive is an SSD, download the specific test S/W for whomever made your SSD (i.e. Samsung magician, Crucial Storage Executive, SanDisk SSD Dashboard, etc., etc.) and run it.

Note: DO NOT use chkdsk on an SSD (I can personally attest to the fact running chkdsk on an SSD WILL corrupt the data stored on it and necessitate reinstalling everything from a backup!)

Good luck!

Reply | Quote

Exception code: 0xc0000005 points to process corruption which can be caused by many different things (i.e. defective device, corrupt S/W, defective memory, defective drive, incorrect device/hardware config, etc., etc.)

You indicated you already ran SFC and DISM with no problems found so that pretty much leaves either defective H/W or a driver for the H/W as the problem.

First off, since the problem “appears” to be related to the USB ports, unplug all your USB devices (except the mouse and keyboard), reboot, and see if the problem disappears.

Yes, I have thought that I would remove the USB devices and test that.  Not mentioned is that these are plugged into an add-on USB card.  So I might try pulling the whole card and see what happens.

I hate trial and error debugging.  It’s archaic and a huge time sink.  It’s like with some car mechanics where they keep wanting to replace parts until they stumble on the one that is causing the problem.

Anyway, I have been monitoring the event logs and see the LogonUI error comes up everytime I logon and no other time.

As an old mainframe systems programmer, I am curious as to WHAT is the tie-in between logging into Windows and getting an error that is somehow tied to USB ports or devices.

Win logon must be doing something that triggers this error, perhaps querying USB ports at logon?  Possibly to see if I am using a USB flash drive with a key on it?

Are there any Windows programmers here that would be able to explain what logic is occurring at the Win logon screen?

Reply | Quote

“Win logon must be doing something that triggers this error, perhaps querying USB ports at logon?  Possibly to see if I am using a USB flash drive with a key on it?”

That could be Windows Hello looking for credentials on a key.. or a protection product scanning for devices to scan.. or a lonely drivers scanning the ports for their accompanying hardware.. as they haven’t been removed but the hardware is no more (perhaps think printer drivers – “printmare” is as you term it “some months old” now, and printers plug in to USB ports..)

have you managed to jam in the autologin credentials yet?

if that worked in terms of bypassing the login before it can log out, then you should be able to enumerate problem devices with pnputil /enum-devices /problem /ids from a CMD prompt even if the rest of the GUI is messed due to a dodgy driver. If it didn’t work and Windows logs out or goes into a flat spin, the issue is potentially a protection product issue or a GINA driver problem. If Windows gets to a desktop and stalls try to run explorer from task manager – if it dies or just does nothing look to dodgy explorer context menus and plug ins.. DWM isn’t always wonderful if something elsewhere is out of whack…

Perhaps a brutal way of finding out if a problem driver started the issue is to take a CMD to C:\Windows\WinSxS and do a dir *driver*.* /s and see what if anything by way of drivers was changed or arrived at about the time the problem started (as this location is copies of past files, as well as current).. this relies on people using blatantly obvious names for their files, but as there is a whole installation worth of files to look through the output needs trimming down (seems to pull out Microsoft drivers, anyway).. problem is if you change anything file wise in Winsxs via  recovery options the installation is likely to become Unstable and servicing will definitely be impacted so change nothing!.. but if you can localise the problem driver you can work with it through more conventional means..

As to the hardware if you want an independent test, get a trash PVR you can salvage a suitable drive from, erase it, and throw Windows on – the drive in a PVR isn’t a desktop model (Tortoise not hare – slower but a consistent data rate, less error checking and data corruption negation though as the PVR video software does that) but it should be fine to do a test install to get a fresh evaluation of the hardware. You could the drivers on line them use PNPUTIL to pull the drivers from that install and add them to the old install with DISM if the test install works. Of course if it fails that will confirm some sort of hardware fault.

Next wide of the mark suggestion from the old days – try turning off the sound card in the BIOS (assuming its not plugged into a slot of course). Windows could be trying to play a start-up sound as it logs in, and the data could be going elsewhere due to a problem,  confusing the hardware and leaving the sound driver running but unable to interact with its hardware correctly, which might well cause an exception in that driver or the driver for the hardware being incorrectly addressed with sound data. That along shouldn’t account for the logging out but it’s a quick thing to try to narrow the field.

Reply | Quote

ibe98765 wrote:

Up until yesterday (12/15, the Ides of December)

Sorry, the Ides was only the 15th day of the month in March, May, July and October; in all other months, it was the 13th.

As ever, life’s a bitch!  Why couldn’t these Romans be consistent?

Dell E5570 Latitude, Intel Core i5 6440@2.60 GHz, 8.00 GB - Win 10 Pro

Reply | Quote

Update – This problem is still occuring.  I kept the event log viewer open for weeks, looking at events whenever the logon screen lock occurs.

For example, I returned to the desktop this AM and found 9As usual when this problem happens) that I could see the logon screen but the mouse and keyboard would not work, so I could not enter the system password.  I tried unplugging both the mouse and keyboard from the USB ports and replugging but this never (didn’t] help.  I had also tried plugging in a PS2 connection keyboard but that did not make any difference.

My only solution was to hard boot the system, as usual.

I again looked in the event log for any new/useful entries between the time I went to bed last night, when everything seemed to be working fine and this morning, when I returned to the system to experience the logon screen lockout.

The only entry of note in event log is this one, which is consistent each time this happens and shows:

“The previous system shutdown at 8:36:40 AM on ?2/?14/?2022 was unexpected.”

I don’t know WHY there was a system shutdown , nor what initiated it.  I see nothing in the surrounding logs that indicated anything forcing a system shutdown.

Are there any other Windows logs to look at other than events?

————-

Log Name: System
Source: EventLog
Date: 2/14/2022 10:24:01 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: pc-03222015
Description:
The previous system shutdown at 8:36:40 AM on ?2/?14/?2022 was unexpected.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”EventLog” />
<EventID Qualifiers=”32768″>6008</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=”2022-02-14T18:24:01.7373587Z” />
<EventRecordID>52374</EventRecordID>
<Correlation />
<Execution ProcessID=”0″ ThreadID=”0″ />
<Channel>System</Channel>
<Computer>pc-03222015</Computer>
<Security />
</System>
<EventData>
<Data>8:36:40 AM</Data>
<Data>?2/?14/?2022</Data>
<Data>
</Data>
<Data>
</Data>
<Data>134415</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E607020001000E00080024002800B401E607020001000E00100024002800B401600900003C000000010000006009000001000000B00400000000000000000000</Binary>
</EventData>
</Event>

———-

Reply | Quote

The unexpected system shutdown is you hard booting the PC.

Do you have another machine you can use? Install a remote control program and try to connect to the locked up PC. If that works it may be the USB hardware / drivers.

cheers, Paul

Reply | Quote

This is a sticky one. I’m thinking it’s a weird hardware fault (mainly as you have to hard reboot, which I take to mean the power button doesn’t start Windows shutting down) but the fault is just too repeatable (unless you have intermittently sticking left Windows key and your password is llllll!).

I wonder if the abrupt reappearance of the log in screen is rooted in a forced log off (expired password?) of another user account which is set to “log on as a service”? it’ll likely be a program updater of some sort but Nvidia stopped using that method (XP) years ago. Maybe check the operational log in event viewer (at the bottom) under Application Services and Logs\Microsoft\Windows\User Profile Service, and see if any recent entries just post failure relate to an account which isn’t one you use?

I’d also be tempted to fire up \Windows\System32\powercfg.cpl, check under “Choose what the power buttons do” that the case button is set to shut down, and (back at the power dialog) in the active power plan advanced settings, turn off USB selective suspend just in case the ports are shutting off and the driver doesn’t detect devices in low power mode (so the ports stay in low power mode). I can’t see why that should affect the logon process but if it gets the keyboard / mouse working closer to normal.. I guess the other option is to get a USB port expansion card installed, boot to Windows and shut down (maybe using the power button?), then turn off the current ports in the BIOS settings and move the USB essentials to the card and see if 10 minutes after you turn it on the USB devices want to work- it might at least allow the USB ports to be ruled out as a cause, though its hard to determine how an issue there could affect the login process stability.

Reply | Quote

Thanks.  We’re just throwing crap at the walls here and seeing what sticks.  I have an add-on USB card and I have unplugged and replugged/configured all the USB devices at one point or another.

When I say hard boot, it means that I can often press the front panel power off button to restart although now and then, I have to turn the PSU switch off/on.

Other than this periodic but intermittent issue, the system runs fine.

I still think the key is that log entry that shows the system apparently shutting down for some unspecified reason as in the entry posted above:

“The previous system shutdown at 8:36:40 AM on ?2/?14/?2022 was unexpected.”

What caused this shutdown to happen???  As previously stated, there is nothing around the times when I see this event record that points to any condition that would be the cause of a sudden shutdown.

So assuming that the system did shutdown and then restarted itself, it would not be able to return back into Windows because it could not get past the password requirement at the logon screen.  Maybe some timeout is occuring when Windows can’t restore itself that locks the logon process?

This doesn’t seem to occur to me when I am doing the restart and I can enter the password.

It seems like I would need some sort of hardware log from the mobo that was outside of Windows but that is beyond my competency.

I’m lost and frustrated.

Reply | Quote

Do you have Fast Boot enabled? I would turn it off and also disable Hibernate and see what happens.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Nope, don’t use fast boot or hibernate.

Reply | Quote

Well, continuing the previous methodology, if it’s not a device present in the system, maybe it’s a device which is appearing and causing the problem – even if it’s something that really doesn’t exist and is the result of some sort of hardware glitch.

Perhaps in an elevated CMD prompt, try

pnputil /enum-devices >> %userprofile%\desktop\devices.txt

and open the devices.txt on your desktop and search for “disconnected” and if there is anything there you don’t recognise as ever being connected maybe we need to know the details of that device to try to guess what the issue might be (or at least which part might be at fault..). You can also remove drivers for devices which aren’t present, but I don’t think we’ll gain much by doing that at this point. I’m wondering if a new “generic” driver from Windows update has arrived which generally works fine, but doesn’t have the code to cope with a tweak to the usual hardware configuration used only on your board and only a problem in some pretty specific circumstances..

The only hardware thing I could find was a known issue with a batch of regulators in a sister board  (LDO=low drop out = drops 3V to 3V3 or whatever but will keep 3V3 good if 5V drops to 4) though that does indicated it could be your PSU which is at fault.. as if the 5V is at the low end of “good ” (4.75V) and the regulator say needs 4.5 most days as it’s not a particularly good one a power brown out could see the supply from the regulator go bad enough (due to noise on the voltage) to cause problems on the motherboard without necessarily firing a motherboard reset..

https://www.reddit.com/r/buildapc/comments/2jrt1b/psarequest_possible_reoccurring_problem_with_the/

 

 

Reply | Quote

I had this exact same issue with the same board on windows 10, same error in logs, and it has been fixed for 10 restarts so far. I think the thing that fixed it was uninstalling some asrock software related to the motherboard.

1. a tuning utility

2. xfast ram

If that doesn’t work then I reccomend opening up your computer and reseating your ram after checking for any debris that may affect the contacts

if you are still having issues then it’s possible you have a bent pin below your cpu, so you may want to try and look with a magnifying glass or phone camera zoom, correct, and reinstall your cpu.

Good luck

Reply | Quote

I wanted to update and close out this problem, which has finally cleared on its own.  Have had no instances of it in the last 4-5 months or so.  I changed nothing, so don’t know why it cleared.  Possibly something that has been fixed with Microsoft’s monthly updates?

Fingers remain crossed that it remains cleared.

Reply | Quote