ntoskrnl.exe BSOD crashes


  1. Posts : 18
    Windows 7 64 bit
       #1

    ntoskrnl.exe BSOD crashes


    I've had this blue screen error for over 2 years ever since I first got my PC built. The guy who built it kept telling me to run memtests and update all my drivers and I did all that but it still happens and I'm to the breaking point finally. It seems completely random when I BSOD, could be once every week or up to 8 times in 1 day. I had 16GB but i ran memtest for over a week and weeded out 2 bad sticks, the current 2 give me no errors when i run it overnight.

    I used bluescreeneventviewer to see why I was crashing and it always says caused by the driver "ntoskrnl.exe".

    My system specs:

    • i7-2600k not overclocked
    • nvidia gtx 660ti
    • 8GB corsair vengeance
    • Mushkin Enhanced Chronos Deluxe 240GB SSD
    • 2TB Caviar Black
    • windows 7 64bit

    Any other information needed or some steps I could take to help troubleshoot why I've been getting these errors would be very much appreciated.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi sean088.

    You are overclocked; and stop 0x124 BSODs are most frequent in overclocked machines.
    Code:
    CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3502
    As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    If you cannot do it yourself, ask the guy how made it.

    Let us know how the computer is running with the stock hardware settings. If there is any more BSOD after disabling overclock, post them as per the instructions.
    _______________________________________
    Code:
    BugCheck 124, {0, fffffa800944e028, be200000, 5110a}
    
    Probably caused by : GenuineIntel
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 18
    Windows 7 64 bit
    Thread Starter
       #3

    Wow that's weird lol. The guy who built it advised against it so idk why it was overclocked at all. I set it back to 3.4

    I'll post again in the next day or two if its happened again or if everything is good!
      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 09:42.
Find Us