Solved

BSOD on fx8300 ,a.g 970a ASROCK

Hello,
So i was using a Cooler Master HYPER 212 EVO ,ony my older motherboard and an older cpu ,to make my msi gtx960 2gb graphics card to work,aswell i used a 8gb ddr3 ram on that old cpu and motherboard!

Now i finally upgraded it to a amd fx8300 cpu and 970a ag3.1 motherboard!
I got the framerate upgrade in games that i hoped for,but i saw that my cpu is getting oc'd to 3.5ghz all the time ,while i havent even done anything in the bios.

And after playing games for a few hours,my pc suddenly crashes and gives me a blue screen!
I found out its caused by ntoskrnl.exe (irql not less or equal ), and ive tried running repairs,even i formated the drivers so i have a fresh pc with nothing on it but it still gives me the bluescreen whenever i play games!

I need help fast :(

i'll be trying to run memtest and ill update how it goes,but i still need some suggestions ! Me and my friend ran out of ideas for the cause!

Sorry if my grammar is bad!

Specs :
CPU : FX8300
MOBO : ASrock 970A-G/3.1
GPU : GTX960 2gb
RAM : 8GB, DDR3, 1866MHz HyperX fury
Cooler : Cooler Master HYPER 212
PSU : Chieftec ATX Force 650W
Reply to djexperia2
34 answers Last reply Best Answer
More about bsod fx8300 970a asrock
  1. Hi djexperia2,

    The fx-8300 has a max frequency of 4.2ghz.

    What kind of repairs do you mean?

    When ntoskrnl is blamed for a BSOD it is most definitely not the cause, it is the last resort for getting the blame when the system cannot find anything else to blame, this is because the ntoskrnl is the last process active as it calls the BSOD whenever something serious goes wrong in the kernel.
    Just a FYI, the system uses a structure called 'stack' which keeps track of the calls made to functions for executing something, if the stack is empty of 3rd party driver the system defaults to the Windows driver. Any driver that is not a kernel driver will then be blamed, else the kernel drivers will be blamed.


    Please follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, do NOT run the tests linked. Upload the zip to a 3rd party uploader and post a share link.
    Reply to axe0axe0
  2. axe0axe0 said:
    Hi djexperia2,

    The fx-8300 has a max frequency of 4.2ghz.

    What kind of repairs do you mean?

    When ntoskrnl is blamed for a BSOD it is most definitely not the cause, it is the last resort for getting the blame when the system cannot find anything else to blame, this is because the ntoskrnl is the last process active as it calls the BSOD whenever something serious goes wrong in the kernel.
    Just a FYI, the system uses a structure called 'stack' which keeps track of the calls made to functions for executing something, if the stack is empty of 3rd party driver the system defaults to the Windows driver. Any driver that is not a kernel driver will then be blamed, else the kernel drivers will be blamed.


    Please follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, do NOT run the tests linked. Upload the zip to a 3rd party uploader and post a share link.



    The page u sent me ,says error 404
    Reply to djexperia2
  3. Your speeds are normal , that 3500mhz its hitting will be the p1 multicore boost state.
    Reply to madmatt30
  4. axe0axe0 said:
    Hi djexperia2,

    The fx-8300 has a max frequency of 4.2ghz.

    What kind of repairs do you mean?

    When ntoskrnl is blamed for a BSOD it is most definitely not the cause, it is the last resort for getting the blame when the system cannot find anything else to blame, this is because the ntoskrnl is the last process active as it calls the BSOD whenever something serious goes wrong in the kernel.
    Just a FYI, the system uses a structure called 'stack' which keeps track of the calls made to functions for executing something, if the stack is empty of 3rd party driver the system defaults to the Windows driver. Any driver that is not a kernel driver will then be blamed, else the kernel drivers will be blamed.


    Please follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, do NOT run the tests linked. Upload the zip to a 3rd party uploader and post a share link.


    madmatt30 said:
    Your speeds are normal , that 3500mhz its hitting will be the p1 multicore boost state.



    what?
    Reply to djexperia2
  5. All fx chips have 2 native boost States
    On an fx 8300
    Boost state p0 - under heavy single threaded work 1 core can hit as high as 4.2ghz
    Boost state p1 - under multi threaded loads 4 cores can hit up to 3.7ghz while the remaining 4 cores drop speeds to 3000-3300mhz to keep the CPU within its stock power rating.


    This is normal behaviour not overclocking & should not cause any instability at all.

    If you don't want this behaviour then enter your bios & simply disable the 'turbocore' option
    Reply to madmatt30
  6. djexperia2 said:
    axe0axe0 said:
    Hi djexperia2,

    The fx-8300 has a max frequency of 4.2ghz.

    What kind of repairs do you mean?

    When ntoskrnl is blamed for a BSOD it is most definitely not the cause, it is the last resort for getting the blame when the system cannot find anything else to blame, this is because the ntoskrnl is the last process active as it calls the BSOD whenever something serious goes wrong in the kernel.
    Just a FYI, the system uses a structure called 'stack' which keeps track of the calls made to functions for executing something, if the stack is empty of 3rd party driver the system defaults to the Windows driver. Any driver that is not a kernel driver will then be blamed, else the kernel drivers will be blamed.


    Please follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, do NOT run the tests linked. Upload the zip to a 3rd party uploader and post a share link.



    The page u sent me ,says error 404



    Odd, I have no problem.

    Download this executable: https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/
    It will collect some files required for analyzing the BSODs.
    Run the app, the output is a new folder created in Documents + a zipped version -- SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.
    It may take some time before the app is finished, please be patient as it could take 15 minutes.
    Upload the zip to a 3rd party uploader and post a share link.

    Please answer following questions
    · Age of system (hardware)
    · Age of OS installation - have you re-installed the OS?

    Also don't forget my previous question: "What kind of repairs do you mean?"
    Reply to axe0axe0
  7. axe0axe0 said:
    djexperia2 said:
    axe0axe0 said:
    Hi djexperia2,

    The fx-8300 has a max frequency of 4.2ghz.

    What kind of repairs do you mean?

    When ntoskrnl is blamed for a BSOD it is most definitely not the cause, it is the last resort for getting the blame when the system cannot find anything else to blame, this is because the ntoskrnl is the last process active as it calls the BSOD whenever something serious goes wrong in the kernel.
    Just a FYI, the system uses a structure called 'stack' which keeps track of the calls made to functions for executing something, if the stack is empty of 3rd party driver the system defaults to the Windows driver. Any driver that is not a kernel driver will then be blamed, else the kernel drivers will be blamed.


    Please follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, do NOT run the tests linked. Upload the zip to a 3rd party uploader and post a share link.



    The page u sent me ,says error 404



    Odd, I have no problem.

    Download this executable: https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/
    It will collect some files required for analyzing the BSODs.
    Run the app, the output is a new folder created in Documents + a zipped version -- SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.
    It may take some time before the app is finished, please be patient as it could take 15 minutes.
    Upload the zip to a 3rd party uploader and post a share link.

    Please answer following questions
    · Age of system (hardware)
    · Age of OS installation - have you re-installed the OS?

    Also don't forget my previous question: "What kind of repairs do you mean?"


    Imma download the file later,a bit busy at the moment when im writing this,
    System age is like 1 year for my graphics card ,like 9months for my ddr 3 ram,
    I reinstalled 2 times OS ,and it still bluescreens,it must be the hardware or something in bios?

    What repairs?
    Reply to djexperia2
  8. In your first post you mentioned you tried running repairs, what repairs do you mean?
    Reply to axe0axe0
  9. axe0axe0 said:
    In your first post you mentioned you tried running repairs, what repairs do you mean?

    Windows repair ,repairs trough advanced options,tried some stuff on safe mode

    Can this tell u anything https://imgur.com/a/LHA24 ?
    Reply to djexperia2
  10. The files collected by the tool I ask you to run would provide much more information.

    What it tells me is that a page was being accessed, for some reason something that accessed that page from a different page made a pagefault by attempting to access it which is not allowed at the IRQL level 2 which is displayed in parameter 2 and as such a BSOD was called.
    Nothing more can be said about it.

    To clarify, IRQL is the order in which the processor processes things. The higher the IRQL the earlier something is being processed.
    IRQL = Interrupt ReQuest Level, if something from level 5 comes in and something from level 3 is waiting a few microseconds longer, level 5 is processed earlier.
    As of level 2, everything is done from the memory (nonpaged pool), everything below is from the pagefile. If a rule about accessing memory in the nonpaged pool is violated, like a part of the memory which is beyond the work space of a process but within the work space of another process that has put an access protection on it is accessed, a pagefault occurs, as a rule is broken the 0x50 crash occurs.
    Reply to axe0axe0
  11. axe0axe0 said:
    The files collected by the tool I ask you to run would provide much more information.

    What it tells me is that a page was being accessed, for some reason something that accessed that page from a different page made a pagefault by attempting to access it which is not allowed at the IRQL level 2 which is displayed in parameter 2 and as such a BSOD was called.
    Nothing more can be said about it.

    To clarify, IRQL is the order in which the processor processes things. The higher the IRQL the earlier something is being processed.
    IRQL = Interrupt ReQuest Level, if something from level 5 comes in and something from level 3 is waiting a few microseconds longer, level 5 is processed earlier.
    As of level 2, everything is done from the memory (nonpaged pool), everything below is from the pagefile. If a rule about accessing memory in the nonpaged pool is violated, like a part of the memory which is beyond the work space of a process but within the work space of another process that has put an access protection on it is accessed, a pagefault occurs, as a rule is broken the 0x50 crash occurs.


    ill test it,but yeah ,like ive said im not an expert on this kinda stuff ,but this makes me think it might be related to the cpu,cos i was testing a program that was almost like an benchmark but it made everything run on 100% on my cpu to like stress test it ,and it crashed after 20-30 of running instead of 20 that it should have!
    It just showed ERROR,
    then it started saying ERROR on the cpu core 1# ,#0 #3 ,each time was different.

    Now im thinking aswell about running memtest to check if my ram is okay,

    Some more information http://www.userbenchmark.com/UserRun/4988940
    Reply to djexperia2
  12. Would be nice if you could provide more information about the error messages you received whilst running the test.

    I don't find the userbenchmark results useful since they don't contain the error message you got.
    Reply to axe0axe0
  13. http://www.mediafire.com/file/lyxj99xal6u6pfl/SysnativeFileCollectionApp.zip

    Go ahead and check,respond soon as possible,i really have to fix this!
    Reply to djexperia2
  14. Remove driver booster and revert any driver installations it made. It does not matter when it was installed, it matters that it may affect stability negatively.

    Run memtest86+: https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html
    Reply to axe0axe0
  15. axe0axe0 said:
    Remove driver booster and revert any driver installations it made. It does not matter when it was installed, it matters that it may affect stability negatively.

    Run memtest86+: https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html


    I know that driver booster might screw some drivers up,but i installed it only to check what drivers i have to update,so i can manually do it myself....Does it show that installed something with driver booster?

    I ran memtest and there were no errors!
    Reply to djexperia2
  16. Memtest86+ was ran for at least 8+ passes?
    Reply to axe0axe0
  17. axe0axe0 said:
    Memtest86+ was ran for at least 8+ passes?


    What do you mean 8 passes? It showed COMPLETE no errors ,1 hour 20min ,u mean like re-do for 8 times?
    Reply to djexperia2
  18. Memtest86+ can run infinitely. Have a look at the tutorial I linked.
    Reply to axe0axe0
  19. axe0axe0 said:
    Memtest86+ can run infinitely. Have a look at the tutorial I linked.

    Oh yeah i remember,yes it showed 10 passes , im pretty sure,so what did u find out in the zip i sent?
    Reply to djexperia2
  20. Given your previous reply I'd say you try to avoid a memory test that may help determining the cause.
    Reply to axe0axe0
  21. axe0axe0 said:
    Given your previous reply I'd say you try to avoid a memory test that may help determining the cause.


    Ok ill run it again if u want,let me know what did u find in the zip file,ill talk to you in an hour or two.
    Reply to djexperia2
  22. I did not find much useful in the zip, hence my suggestion for a memory test.

    Be aware, 8GB of RAM takes roughly 10h to reach 8 passes. 16GB takes roughly a day.
    Reply to axe0axe0
  23. axe0axe0 said:
    I did not find much useful in the zip, hence my suggestion for a memory test.

    Be aware, 8GB of RAM takes roughly 10h to reach 8 passes. 16GB takes roughly a day.


    Okay i ran the memtest for 8passes ,it was 20hours long for some reason (half of yesterday ,for the night and while i was in school ,i let the memtest run nonstop)
    but no errors.........
    Reply to djexperia2
  24. Best answer
    I know you've run memtest strenuously.
    But just for the sake of it enter bios & drop that ram speed to 1600mhz.
    Reply to madmatt30
  25. Set the RAM settings to the default XMP profile 1333Mhz
    Reply to axe0axe0
  26. madmatt30 said:
    I know you've run memtest strenuously.
    But just for the sake of it enter bios & drop that ram speed to 1600mhz.

    why u think its the ram problem?
    Reply to djexperia2
  27. axe0axe0 said:
    Set the RAM settings to the default XMP profile 1333Mhz

    What is default XMP Profile ? and why to 1333 so low?
    Reply to djexperia2
  28. Its the default of your RAM
    Reply to axe0axe0
  29. axe0axe0 said:
    Its the default of your RAM


    i set it to 1600mhz ,cos im worried of something wrong happening about 1333mhz
    Reply to djexperia2
  30. madmatt30 said:
    I know you've run memtest strenuously.
    But just for the sake of it enter bios & drop that ram speed to 1600mhz.


    Ive set it to 1600mhz for like 3-4days i havent had a bsod,how could this helped? Any explenations?
    Reply to djexperia2
  31. Could be ram voltage , could be timings.
    More likely voltage.

    I have some hyper x blue 1866 here , it does not have a preset timing/voltage table for it full rated speed.
    It requires 1.65v to run at 1866 & also requires loosed timings

    At 1866 it was likely still running 1.5v & 1600 timings.

    It can pass a memtest but fail under normal use (which was happening to you IMO)
    Reply to madmatt30
  32. madmatt30 said:
    Could be ram voltage , could be timings.
    More likely voltage.

    I have some hyper x blue 1866 here , it does not have a preset timing/voltage table for it full rated speed.
    It requires 1.65v to run at 1866 & also requires loosed timings

    At 1866 it was likely still running 1.5v & 1600 timings.

    It can pass a memtest but fail under normal use (which was happening to you IMO)


    Well thanks a lot for now,ill update if it still bsods !
    Cheers!
    Reply to djexperia2
  33. madmatt30 said:
    Could be ram voltage , could be timings.
    More likely voltage.

    I have some hyper x blue 1866 here , it does not have a preset timing/voltage table for it full rated speed.
    It requires 1.65v to run at 1866 & also requires loosed timings

    At 1866 it was likely still running 1.5v & 1600 timings.

    It can pass a memtest but fail under normal use (which was happening to you IMO)


    Well just got a bsod DRIVER_IRQL_NOT_LESS_OR_EQUAL ,there goes my hope ....
    Reply to djexperia2
  34. axe0axe0 said:
    Its the default of your RAM


    I was running fine for a week ,now i got another bsod DRIVER_IRQL_NOT_LESS_OR_EQUAL .
    Im lost for words.
    Reply to djexperia2
Ask a new question Answer

Read More

ASrock RAM CPUs Motherboards Blue Screen