Windows 10: BSOD when idle for 4 minutes, REGISTRY_ERROR Solved

Page 3 of 3 FirstFirst 123
  1.    27 Jun 2016 #21

    I have had the same problem for weeks. Windows 10 went into BSOD crash after 4 minutes of idle time. I used this forum to try to track down the cause but nothing worked - until another website mentioned it might be Windows Defender at fault and to try switching it off.
    I found this site and followed the instructions to disable Windows 10 Defender permanently from the registry: -
    Hope this helps other poor sufferers.
      My ComputerSystem Spec

  2.    01 Nov 2016 #22

    Respected Sir/Ma'am
    I am experiencing bsod issues. - Similar to this. I am sorry to say but I m not using a genuine copy of windows 10. I am using my PC after a break of 4 weeks. Earlier I didn't experience any of these issues. I got my PC built on 23 rd March 2016. The same day , I got windows 10 installed in it from a renown shop for selling pirated products. The owner of the shop told me not to update windows, which I did. Immediately as I did , I experienced crash and data loss. But that happened 4 days after I built my rig. After that everything was fine. I think maybe its due to ram issue. on 30th oct , I cleaned my rig well. I was not getting display , it showed no signal on my monitor. For the same , I searched for the remedy and I came across an article that read , reinstall your RAM , which I did. I removed it and put in system back again. after that , It worked all well until I began experiencing bsod issue. The issue is same as the article link that I gave , except that I am not using a preview build. Its like 4 mins and the system reboots. I thought maybe it's associated with the ram cleaning which I did. Thus I reinstalled my ram once again. I checked in bios, everything is fine. I even loaded optimized defaults. For the information of my rig, kindly view my profile. As mentioned in article , I can't leave my Pc Idle. I ran sfc/scannow , it displayed : "windows resource protection found corrupt files but was unable to fix some of them . Details are include in cbs.log windir.... . Note that logging is currently not supported in offline servicing scenarios". Please I need your help.
      My ComputerSystem Spec

Page 3 of 3 FirstFirst 123

Related Threads
Solved BSOD - Any PC game, or even at idle in BSOD Crashes and Debugging
Recently I built a new computer, started using Windows 10 with it. Ever since, I've had at least 10+ BSOD. It seems to be most common during a video game. It's happened at low cpu usage also, though. I've attached two recent BSOD debugs. I wanted...
BSOD Usually While Idle (variety of BugChecks) in BSOD Crashes and Debugging
General Info About The Issue: -My system usually crashes while 1)idle or 2) under light usage (like web-browsing, etc.) -It does not crash while gaming which is my primary use for the machine. -There are a variety of Bugchecks (see attached)...
Why Windows 10 use 1gb of ram at idle (32bit)? Can I turn of something? Thats too much. Windows 8.1 used below 500mb. Also my part of the screen on the left is black. I have radeon 4650, windows found drivers but probably I will need drivers from...
Random BSOD whilst machine Idle in BSOD Crashes and Debugging
Hello All I am wondering if you can help I am currently running Windows 10 and suffered a BSOD whilst I was asleep so I apologise for not having more information than that , I have attached the required ZIP and am willing to provide more info as...
1013X PC freezes when idle in General Support
See my system description. One possibly critical thing that isn't listed: my boot drive is an Intel 750 NVME add-in device, with the most recent NVME drivers installed. (They don't officially support Win 10, I believe.) Under 10130 X64, the PC...
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 18:03.
Find Us