BSOD Usually while playing GTA V, caused by ntoskrnl.exe


  1. brandonium10
    Posts : 5
    Windows 10 Pro
       New #1

    BSOD Usually while playing GTA V, caused by ntoskrnl.exe


    I keep getting repeated BSOD after fresh install of Windows 10. I originally reinstalled because my computer was running really slowly and nothing else was working, so I reinstalled my OS. Most of them have been SYSTEM_SERVICE_EXCEPTION or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, mostly caused by ntoskrnl.exe. I have tried updating most of my drivers and have posted to other threads, and a user on Tom's Hardware lead me here. Thanks for any help that anyone can give.
      My Computer
    Quote Quote

  3. axe0
    Posts : 14,903
    Windows 10 Pro
       New #2

    Hi brandonium10,

    Unfortunately, there are issues with symbols and we have to wait for Microsoft to fix them.

    However, the BSODs are all over the place + since you state that a reinstall doesn't help it is obvious that a hardware issue is present.

    Please run all below tests.
    Please note, if you have any question about any test below, many questions that are asked are answered in the tutorials, read them carefully and if you still have a question after reading please do not hesitate to ask :)





    STOP 0x124 Troubleshooting

    Read carefully before proceeding.



    warning   Warning
    If you're overclocking your system, revert back to stock clocks now.

    Note   Note
    Test the system once the overclock is removed before continuing with the steps outlined below.


    Part One: CPU Stress Test
    Part Two: MemTest86+ RAM Diagnostic
    Part Three: Hard Drive Diagnostics
    Part Four: GPU Stress Test




    ONE

     CPU TEST


    Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

    Make a photo of the result and post it.




    TWO

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Make a photo of the result and post it please.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.




    Diagnostics Test

     HDD TEST


    Note   Note
    Please run HDTune first, in the order posted!

    Run HDTune to
    • check the health,
    • scan for errors, no quick scan but full scan
    • run a benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the health,
    • the error scan,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.


    Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
    Note   Note
    Do not run SeaTools on an SSD as the results will be invalid.

    Make a photo of the result and post it.

    Run chkdsk
    Disk Check - Windows 7 Help Forums
    Use option TWO with parameter /r
    Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums




    FOUR

     GPU TEST


    Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

    Note   Note
    Run Furmark for around 30 minutes.

    warning   Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

    Make a photo of the result and post it.

    In Furmark you can find a tool called 'GPU-Z' (if you want to install GPU-Z is up to you), when GPU-Z is open click on the 'Sensors' tab, on this tab you can monitor
    • the frequency of the GPU,
    • the GPU memory clock,
    • the temperature,
    • the power,
    • the load on the GPU,
    • Etc.

    I would like you to make a screenshot of GPU-Z after you have either cancelled Furmark for any reason or Furmark is finished, post this screenshot in your next reply with the result of Furmark.
      My Computers
    Quote Quote

  4. brandonium10
    Posts : 5
    Windows 10 Pro
    Thread Starter
       New #3

    I ran prime95 for about an hour and then my computer blue screened resulting in a ntoskrnl.exe error. Here is the results.txt from the prime95 folder because I couldn't screenshot it:
    [Fri May 19 19:04:50 2017]FATAL ERROR: Rounding was 0.48046875, expected less than 0.4Hardware failure detected, consult stress.txt file.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTPossible hardware failure, consult readme.txt file, restarting test.ERROR: ILLEGAL SUMOUTMaximum number of warnings exceeded.Self-test 28K passed!Self-test 28K passed!Self-test 28K passed!Self-test 28K passed![Fri May 19 19:09:55 2017]Self-test 28K passed!Self-test 28K passed![Fri May 19 19:17:12 2017]Self-test 8K passed!Self-test 8K passed!Self-test 8K passed!FATAL ERROR: Rounding was 0.498046875, expected less than 0.4Hardware failure detected, consult stress.txt file.Self-test 8K passed!Self-test 8K passed![Fri May 19 19:22:46 2017]Self-test 40K passed!Self-test 40K passed!Self-test 40K passed!Self-test 40K passed!
      My Computer
    Quote Quote

  6. axe0
    Posts : 14,903
    Windows 10 Pro
       New #4

    If I'm reading correct, a ton of hardware errors reported by prime95? That means you'd need to replace the CPU.
      My Computers
    Quote Quote

  7. brandonium10
    Posts : 5
    Windows 10 Pro
    Thread Starter
       New #5

    I'll run the other tests as well to see if it is just that.
      My Computer
    Quote Quote

  8. brandonium10
    Posts : 5
    Windows 10 Pro
    Thread Starter
       New #6

    Here are the results from Furmark:
    Furmark Results - Google Drive
      My Computer
    Quote Quote

 

  Related Discussions
So when i was reinstalling league of legends, i got a BSOD.. When i restarted and reinstalled again, in a game i got a BSOD.. Now when i just had my pc in sleepmode because i had to eat i got a BSOD... RIP ME xD I actually got quite a list...
Various BSOD Caused by ntoskrnl.exe
in BSOD Crashes and Debugging

Hi, I'm facing various BSOD. After I open minidump files via Bluescreenview, it's caused by Ntoskrnl.exe. Here's the minidump files Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. Here's the screenshot of...
BSOD caused by ntoskrnl.exe please help
in BSOD Crashes and Debugging

Hey all, I've attached 4 minidumps. Can you please help troubleshoot this intermittent BSOD?
BSOD caused by ntoskrnl.exe
in BSOD Crashes and Debugging

Hello! I have recurring blue screens on my laptop and can't seem to figure out what's causing them. Sometimes, the computer also freezes completely without any forewarning and the only way to shut it down is to remoce the battery. I should...
BSOD caused by ntoskrnl.exe
in BSOD Crashes and Debugging

BSODs have been happening for a while but I'm not really sure what's the actual cause.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

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




Windows 10 Forums