BSOD when idle for 4 minutes, REGISTRY_ERROR

Page 1 of 3 123 LastLast

  1. Posts : 7
    Windows 10
       #1

    BSOD when idle for 4 minutes, REGISTRY_ERROR


    Starting on the 17th, which is how far back the dump files should go, my computer began receiving a BSOD with the error "REGISTRY_ERROR" whenever I would leave it idle for about 4 minutes. Previously I've never had any issues with this computer. Everything's at stock. I'm also in the Windows 10 preview build, and should be receiving early updates if I understand that portion of the program correctly.

    Previously, to try and remedy the issue myself, I recorded footage of my desktop and then left the computer idle, with task manager on the screen viewing what was using up most of the CPU, because I had previously discovered my computer would jump in CPU usage shortly before crashing. It was something being run in the background by Windows Defender, and conveniently Windows Defender has something that begins running in 4 minutes after idle, so I turned Windows Defender off, and that solved the issue for most of the day yesterday, until Windows Defender turned itself on again and crashed the computer with the same error.

    Turning off Windows Defender has not solved the issue since, and I've even tried permanently turning it off through Group Policy, but now even when off, the computer crashes the same way. Without turning it off through Group Policy, it turns itself on almost immediately after being turned off. It has also had about 5 updates throughout the day.

    My temporary solution is to move the mouse a bit every once in awhile if I'm away from my computer, otherwise I get the BSOD again.

    Thanks for the assistance in advance! I hope I've provided enough information.

    Edit: I just visited the "Security and Maintenance" tab, clicked "Start Maintenance", and that caused the BSOD almost immediately. It would seem that this automatic maintenance activates after the computer is left idle for a few minutes, and is the culprit. I have no idea why though. Before the BSOD happens, CPU, Memory, and Disk usage rise really quickly.

    This is just right now with Chrome open
    Attachment 38573

    This is the peak after starting "Start Maintenance", 10 seconds before the BSOD
    Attachment 38576

    This is the final second before the BSOD
    Attachment 38577
    Last edited by Conkerkid11; 21 Sep 2015 at 05:06.
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    Hi Conkerkid11,

    Welcome to the 10forums.

    The error 'registry_error' means that the registry is corrupted.
    Because the registry is an extremely important part of the OS it needs to be fixed a.s.a.p.

    Please do the following:

    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


  3. Posts : 7
    Windows 10
    Thread Starter
       #3

    Thank you for the quick response! I followed the steps you provided, and when I ran through that scan the first time, I received the "Windows Resource Protection did not find any integrity violations" message, but continued through the steps, and after a reboot, ran it again, and also received the "Windows Resource Protection did not find any integrity violations" message.
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4

    You only get the registry_error crash when leaving the pc idle?
      My Computers


  5. Posts : 7
    Windows 10
    Thread Starter
       #5

    axe0 said:
    You only get the registry_error crash when leaving the pc idle?
    Leaving the PC idle for roughly 4 minutes gives me the registry_error BSOD. And clicking "Start Maintenance" in the "Security and Maintenance" window gives me the registry_error BSOD. These are the only two things that I have found to give me the registry_error BSOD.

    I just tried running The Witcher 3, and it was running at the same speed with the same settings that it did before I began running into this issue, and my CPU, memory, and disk usage seemed to be fine after running that for quite some time as well. It was originally my worry that this would cause it to BSOD as well, considering I haven't done anything all that intensive since the issue came about, but that doesn't seem to be the case.
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6

    This is most likely a bug in the preview built. It could also be hardware damage which I doubt reading your post.
      My Computers


  7. Posts : 7
    Windows 10
    Thread Starter
       #7

    axe0 said:
    This is most likely a bug in the preview built. It could also be hardware damage which I doubt reading your post.
    I mentioned being part of the Insider Build just in case that might be the issue, should it come up, but it really doesn't seem to be that way unfortunately. I'm counting on it being a software issue, but it could just as easily be a hardware issue.

    While being in the Insider Build thing, it turns out I'm set to a "slow" setting, so I receive the Insider Builds more close to public release than other insiders. I checked, and I'm currently running the latest build of the public release of Windows 10. The last time I received an update for Windows 10 was on the 8th, whereas this issue began on the 17th. On that day, the only things I had recently installed were Unity 5 and the latest version of Visual Studio that it came with. Oh, and the latest build of Nvidia GeForce Experience. My version of Windows Defender is also currently on the latest public build.

    This issue would be fine if I could find other people running into it, but after waiting 4 days, nothing else popped up, so I decided to make this thread hoping somebody else might have run into it, or something else might be able to discover something within the batch files that I didn't, because this is unfamiliar territory for me.

    Edit Using BlueScreenView for example, all of the dump files say the "Caused By Driver" is "ntoskrnl.exe". I've tried looking up BSODs caused by that, and it doesn't seem like it's a single specific issue.
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #8

    The ntoskrnl.exe file is an extreme important file for windows. You won't be able to boot without this file, because it is used for the boot process.
    Windows files are usually blamed when 3rd party drivers are 'hiding'.
    But it could also mean that a component of the pc is damaged in this case.
    REGISTRY_ERROR (51)
    Something has gone badly wrong with the registry. If a kernel debuggeris available, get a stack trace. It can also indicate that the registry got
    an I/O error while trying to read one of its files, so it can be caused by
    hardware problems or filesystem corruption.
    It may occur due to a failure in a refresh operation, which is used only
    in by the security system, and then only when resource limits are encountered.
      My Computers


  9. Posts : 7
    Windows 10
    Thread Starter
       #9

    Checking back in, did fine with memtest, and passed on both of my SSDs and HDD.

    I'm going to try booting in safe mode, and if that doesn't work, using the reset feature of Windows 10.
      My Computer


  10. Posts : 14,901
    Windows 10 Pro
       #10

    Conkerkid11 said:
    Checking back in, did fine with memtest, and passed on both of my SSDs and HDD.

    I'm going to try booting in safe mode, and if that doesn't work, using the reset feature of Windows 10.
    You performed the built-in memtest or memtest86(+)?
    Ran chkdsk on the hard drives?

    I just want to keep up with what you're doing :)

    Below is a troubleshooting process you might want to try.



    Diagnostics Tests

    Read carefully before proceeding.



    warning   Warning
    If you're overclocking your system, revert back to stock clocks now.

    Note   Note
    Test the system once the overclock is removed before continuing with the steps outlined below.


    Part One: CPU Stress Test
    Part Two: MemTest86+ RAM Diagnostic
    Part Three: Hard Drive Diagnostics
    Part Four: GPU Stress Test




    ONE

     CPU TEST


    Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.





    TWO

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.





    THREE

     HDD TEST


    Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html




    FOUR

     GPU TEST


    Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

    Note   Note
    Run Furmark for around 30 minutes.

    warning   Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:20.
Find Us




Windows 10 Forums