Random BSODS when PC is idle


  1. Posts : 4
    Windows 7 64
       #1

    Random BSODS when PC is idle


    Hi, everyone.

    Recently I've started having random BSODs when PC is idle, didn't recall having BSOD while actually working. This has started pretty much when my UPS has died, and I've plugged the PC directly.



    This is the event viewer, with the Kernel-Power Critical errors.



    Question is, is this related to UPS in any way and can be fixed, or is it a fauly PSU I have to replace?

    Thanks,
    Denis.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Those event logs are always present when a system shuts down unexpectedly, making them almost useless.
    Without a dump we cannot say anything about a possible cause.

    Remove these programs to minimalize the risk of BSODs caused by the drivers they use.
    Code:
    Start Menu\Programs\DAEMON Tools Lite	Public:Start Menu\Programs\DAEMON Tools Lite	Public
    Start Menu\Programs\GIGABYTE\AutoGreen	Public:Start Menu\Programs\GIGABYTE\AutoGreen	Public
    Start Menu\Programs\GIGABYTE\EnergySaver2	Public:Start Menu\Programs\GIGABYTE\EnergySaver2	Public
    Start Menu\Programs\GIGABYTE\ET6	Public:Start Menu\Programs\GIGABYTE\ET6	Public
    Start Menu\Programs\GIGABYTE\Smart 6	Public:Start Menu\Programs\GIGABYTE\Smart 6	Public
      My Computer


  3. Posts : 4
    Windows 7 64
    Thread Starter
       #3

    Unfortunately nothing was created in c:/windows/minidump folder, otherwise I would just check them myself instead of posting here :)
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4

    I don't see software installed with which you could properly inspect a dump, how would you check it then?

    Is there also no C:\Windows\MEMORY.dmp?
      My Computer


  5. Posts : 4
    Windows 7 64
    Thread Starter
       #5

    I don't have WinDbg installed at home, because I never had a need for it at home. As part of my job at work I analyze dumps, so if need be I'll just download WinDbg and check the dumps at home, but there are none.

    Unfortunately C:\Windows\MEMORY.dmp does not exist as well, actually I've scanned entire C: drive for *.dmp and only found some old chrome and firefox dumps.

    I'll try to uninstall the programs you've suggested and let know if it helped.

    Thanks :)
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #6

    Ah, alright :)

    According to the event logs the last recorded dumps are from 4 months ago, all 0x7A. Could you tell me what your actions for resolving those BSODs were?

    What is your job? :)
      My Computer


  7. Posts : 4
    Windows 7 64
    Thread Starter
       #7

    Unfortunately, after uninstalling the programs you've suggested I still had the same BSOD Is there anything I can do to force Windows creating a dump for this?

    axe0 said:
    According to the event logs the last recorded dumps are from 4 months ago, all 0x7A. Could you tell me what your actions for resolving those BSODs were?
    Ah, those were because of a hard drive that was slowly dying on me and I was too lazy to replace it in timely manner :) Eventually I did buy a new one and BSODs stopped.

    axe0 said:
    What is your job? :)
    I'm a plain software engineer, but part of my job is analyzing stability issues for our software, dumps, logs, etc.
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #8

    To force a BSOD:



    Diagnostic Test

     DRIVER VERIFIER


       Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

       Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.





    Ah, those were because of a hard drive that was slowly dying on me and I was too lazy to replace it in timely manner Eventually I did buy a new one and BSODs stopped.
    Alright, I needed to know if the hard drive was or wasn't replaced to rule it out as a possibility why a dump hasn't been recorded :)


    I'm a plain software engineer, but part of my job is analyzing stability issues for our software, dumps, logs, etc.
    Nice, I would like to do something like that too after I finish school :)
      My Computer


 

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

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