Random BSOD on windows startup


  1. Posts : 6
    Windows 7 enterprise x64
       #1

    Random BSOD on windows startup


    Hello, My computer is getting BSOD random about once in 2 days, today twice when windows started, i attached the latest dump file. Thank you in advice!
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    ErcOac said:
    Hello, My computer is getting BSOD random about once in 2 days, today twice when windows started, i attached the latest dump file. Thank you in advice!
    We need more than one DMP to establish a pattern or trend. Please upload the rest
      My Computer


  3. Posts : 6
    Windows 7 enterprise x64
    Thread Starter
       #3

    Thank you so much for replying so soon, i have attached the rest of dmps.Thank you!

    I wanted to add, that the bsod comes after an image freeze, sometimes after the freeze the bsod doesn't come and i need to manual restart from the button, i guess that the dmp files aren't saved when it freezes without the bsod. Thank you again!
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    ErcOac said:
    Thank you so much for replying so soon, i have attached the rest of dmps.Thank you!

    I wanted to add, that the bsod comes after an image freeze, sometimes after the freeze the bsod doesn't come and i need to manual restart from the button, i guess that the dmp files aren't saved when it freezes without the bsod. Thank you again!
    Six possible causes, but all point to memory corruption

    These crashes were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. 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 too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable
      My Computer


  5. Posts : 6
    Windows 7 enterprise x64
    Thread Starter
       #5

    TY again for quick response, i did the memtest, it went ok, 0 errors, and i did the driver test too, but bow i get blue screen every time windows starts, i'm writing this from safe mode. It sais the file name : 'Hidclass.sys' ... I'm attaching the latest minidumps, tell me if is there anything i can do to help resolving this. Thank you!
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    ErcOac said:
    TY again for quick response, i did the memtest, it went ok, 0 errors, and i did the driver test too, but bow i get blue screen every time windows starts, i'm writing this from safe mode. It sais the file name : 'Hidclass.sys' ... I'm attaching the latest minidumps, tell me if is there anything i can do to help resolving this. Thank you!
    The only verified dmp was probably caused by hidclass.sys. Usually some external device like a fingerprint reader, game steering wheel, etc.

    May be USB or bT.

    Run a system file check to verify and repair your system files.
    To do this type cmd in search, then right click to run as administrator, then
    SFC /SCANNOW

    It may need to be run up to three times before sucessful

    Read here for more information SFC /SCANNOW Command - System File Checker

    Let us know the results from the report at the end.
      My Computer


  7. Posts : 6
    Windows 7 enterprise x64
    Thread Starter
       #7

    The only thing that are connected to the usb are my mouse and keyboard, and ocasionally my ipod...Done the sfc/scannow,3 times, and it said 'Windows resource protection did not find any integrity violations'.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    ErcOac said:
    The only thing that are connected to the usb are my mouse and keyboard, and ocasionally my ipod...Done the sfc/scannow,3 times, and it said 'Windows resource protection did not find any integrity violations'.

    So the OS is fine.


    Still waiting for driver verifier.


    There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Event viewer (local) and look for errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

    You want to look for all errors (they have red in the left column ).

    When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

    When you find them please note the event ID, and the source codes and tell us what they are.




      My Computer


  9. Posts : 6
    Windows 7 enterprise x64
    Thread Starter
       #9

    The only critical is event id: 41, source: kernel-power, log: system. 2, 10
    And error, Event ID: 0, Source: PostgreSQL, Log: Application, last 24h : 243, last 7days: 673
    : 3, Kernel-Event Tracing, 3, 9
    : 102, PNRPSvc , system, 15, 100
    :1012, DNS Client Events, System, 137, 1199
    :7001, Service Contol Manager, System, 34, 199
    :7023, Service Contol Manager, System, 15, 101
    :10005, DistributedCOM, , System, 5, 5
      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 07:19.
Find Us