Home > Bsod When > BSOD When System Is Idle

BSOD When System Is Idle


If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).If you can't get into Windows because it crashes After a weeks worth of testing my ram modules one by one, one of them happened to come up with 48 errors under 2 mins of testing. permalinkembedsaveparentgive gold[–][deleted] 0 points1 point2 points 11 months ago(9 children)Well, hopefully I'll notice something. http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS http://www.carrona.org/drivers/driver.php?id=mwac.sys http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys http://www.carrona.org/drivers/driver.php?id=EX64.SYS http://www.carrona.org/drivers/driver.php?id=ENG64.SYS http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys http://www.carrona.org/drivers/driver.php?id=mbam.sys http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys I have highlighted 3 drivers in RED which are very well known to cause issues. http://emec16.com/bsod-when/bsod-when-idle-for-extended-periods.php

While memtestx86 showed 1 error, it actually showed ONLY that one error and the test ran for 2 hours. But now I get frequent (daily) BSOD's, mostly when I walk away from the computer for more than 5 minutes (when the computer is idle). Will let you know My System Specs You need to have JavaScript enabled so that you can use this ... No BSOD when playing games for hours.Hi guys! his comment is here

Windows 8.1 Bsod When Idle

I started getting BSOD two weeks ago. Its not like one is more consistently the problem than the other. I did some disabling of power options (e.g. 'allow Windows to turn this peripheral off to save power') but eventually went around the issue and just unplugged a lot of unneeded

I have uninstalled the gigabyte software and am now running prime95. Stay logged inLog in with FacebookLog in with TwitterLog in with Google Menu Forums ForumsQuick LinksSearch ForumsHistoryRecent PostsLive StreamUnanswered Threads Media MediaQuick LinksSearch MediaNew Media Resources ResourcesQuick LinksSearch ResourcesMost Active AuthorsLatest This website is a free, open, and dedicated community of Windows enthusiasts. Try running with just one stick of ram in the main channel and run memtest, than swap them.

The BSOD's as shown by BlueScreenView almost always have to do with ntoskrnl.exe, and they'll do with really normal sounding operations, like SYSTEM_SERVICE_EXCEPTION, NTFS_FILE_SYSTEM, DRIVER_IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_NOT_HANDLED, BAD_POOL_HEADER - You name it. Memtest86 Best answer johnblJan 27, 2014, 5:37 PM edit: bugcheck only when a machine goes idle often indicates a power management link state bug.to find the issue, you use control panel power If you can't get into Windows because it crashes too soon, try it in Safe Mode. I don't have a System Restore point to return to.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. Windows 7: BSOD after computer is idle for 2 hours 28 Oct 2011 #1 candeehman Windows 7 x64 5 posts BSOD after computer is idle for 2 hours Do you recon, a clean install might fix it if i don't let windows install any drivers? I've worked with computers for the past 10 years and this is the first time I've had this problem of consistent BSODs which i'm unable to solve, which makes me feel


pinaklonkarJan 14, 2011, 1:58 AM I couldn't agree more. https://www.eightforums.com/bsod-crashes-debugging/55631-bsod-when-computer-idle.html aslong as keyboard & Mouse not touched. - OS reinstall - Latest drivers off Asus Support - Except NVIDIA, as Asus are about 6months out of date, but i have tested Windows 8.1 Bsod When Idle Thanks for all the help. Windows 10 Blue Screen Last time when this happened i couldn't even boot up as already described above.

Use common sense. this contact form Thanks BSOD Crashes and Debugging All times are GMT -5. Any who, one last question - do you know what would have caused this? The offending component can usually be identified with a stack trace.Arg2: 0000000000001e00, The watchdog period.Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDEDCUSTOMER_CRASH_COUNT: 27DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULTBUGCHECK_STR: 0x133PROCESS_NAME: SystemCURRENT_IRQL: dmachine info: Vendor Intel Corp. Bluescreenview

No soliciting of any kind. I would strongly suggest you to remove any MSI and GIGABYTE Software currently installed on the system. permalinkembedsaveparentgive goldcontinue this thread[–]Heofz 0 points1 point2 points 11 months ago(5 children)If you're still having this problem I think I know the fix as I had exactly the same problem on windows 10 have a peek here solved Blue screen of death after fresh Windows 7 Install solved External hard drive with windows 7 causes blue screen of death solved Help: Windows 7 Blue Screen of Death Caused

Should I tell him about my imposter syndrome? pinaklonkarFeb 3, 2011, 10:22 AM Best answer selected by pinaklonkar. My issue is very similar to http://www.tenforums.com/bsod-crashes-debugging/23435-bsod-when-idle-4-minutes-registry_error.html - I've basically read every other thread on this BSOD and his was the most similar.

Thank you so much for imparting some knowledge on troubleshooting hardware to me.

Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. If so, that might be worth trying (if I remember right, the Windows XP disk had repair options)--before you do that, though, do you have your important data backed-up? Disabling maintenance should get you through the short term but it sounds like you will likely need to reinstall. It seems like the newer the parts the less tollerance they have for stuff not working the way they want.

Eventually I did get generic 'driver_verifier' error messages and figured it was strange how all these different drivers suddenly had a problem. Would like to hear if anyone else started experiencing random BSODs when idle. joelmartinezJan 14, 2011, 5:09 AM Safari is slow try Opera instead it's fast and secure graemevermeulenJan 14, 2011, 5:23 AM To be honest, I think all your hardware is fine! Check This Out FAULTING_IP: +67322faf01a3d8e4 00000000`773457bd ?? ???

My System Specs OS Windows 7 x64 . permalinkembedsaveparentgive gold[–]A_Nice_Meat_Sauce 0 points1 point2 points 8 months ago*(3 children)Just stumbled upon this thread as I'm having the same issues. I reformatted the partition that has my OS and installed Win7. When I am actually USING the computer, it has thrown BSOD's before but only once in the past.

Computer is idle I'm not too sure what issues there are. Live Chat The live chat is transitioning to freenode and can be accessed here! share|improve this answer answered Feb 17 '11 at 14:52 bobobobo 2,43773155 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign BSOD Help and Support BSOD at random times...

I just came back from dinner, while my pc was still running, about an hour later, BSOD again with a 0x3A if im not wrong. Get the answer OllieOxenFreeJan 27, 2014, 5:55 PM To me it seems to be driver issues Ask a new question Read More Blue Screen Idle Systems Related Resources Bluescreen errors started Little edit... No Blue Screen of Death.

Computer is idle I'm not too sure what issues there are. I've attached all 7 blue screen dumpfiles as well as my full computer specs from dxDiag. Edit: I used this article by the way. Chalking it up to Windows just behaving strangely.

pinaklonkarJan 15, 2011, 9:46 AM Here is something interesting. I also ran a memory test for about 5 hours?