BSOD 0x0000007a ntoskrnl.exe

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 15,026
    Windows 10 Home 64Bit
       #11

    Any BSoD? Freezes?
      My Computer


  2. Posts : 13
    7 x64
    Thread Starter
       #12

    Sorry missed the reply as it was on the next page. No nothing, I havent run the other test yet as i wasnt sure how high these values were. In fact i havent had a BSOD since that last one i mentioned in this thread. It did this last time I ran chkdsk though too, I had a period where everything seemed better, then after a while it happened again.
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #13

    Alright, use your computer the way you do and keep a check on the temps
    If the BSoDs/freezes/ happen again, let us know. It'll take a while till we find out what the problem actually is.
      My Computer


  4. Posts : 13
    7 x64
    Thread Starter
       #14

    Okay, thanks for the help so far.
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #15

    Sure, come back and update this thread when needed.
      My Computer


  6. Posts : 13
    7 x64
    Thread Starter
       #16

    Didn't last too long. Just got another BSOD, looked very much the same as the first 2. I can upload the dump if needed.
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #17

    Please upload them :)
      My Computer


  8. Posts : 13
    7 x64
    Thread Starter
       #18

    Here you go, put all 4 in.
      My Computer


  9. Posts : 15,026
    Windows 10 Home 64Bit
       #19

    Well yes, same error.

    Lets enable driver verifier to rule out buggy drivers.

    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/Windows 7 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 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
    Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

    Information
    Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

    Capt.Jack Sparrow said:
    Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

    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.
      My Computer


  10. Posts : 13
    7 x64
    Thread Starter
       #20

    I havent had a BSOD whilst running this yet. Should I just keep waiting?
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  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:32.
Find Us