BSOD caused by driver (ntoskrnl.exe) /adress (ntoskrnl.exe+72a40)

Page 1 of 3 123 LastLast

  1. Posts : 107
    windows 7 pro 64bit
       #1

    BSOD caused by driver (ntoskrnl.exe) /adress (ntoskrnl.exe+72a40)


    Got my first blue screen of death tonight, had 2 firefox opened one watching youtube video another browsing internet. After bsod it restarted i login but just black screen with cursor, ctrl alt delete worked so i shut my computer down. Boot up normally after, check my minidump file, bsod cause by ntoskrnl.exe. Did little search on google find has to do with ram and hard drive.

    Downloaded wd data life guard diagnostic for my mechanic drive which is healthy but my ssd on shows failed end to end error rate(value/threshold/worst is all 0) in SMART statue. Im not sure if i can trust this wd diagnostic on my crucial ssd, there are alot of unknown in SMART statue too. Theres no ssd diagnotic for crucial, there is a firmware not sure if it helps. So i downloaded and ran crystaldiskinfo on my ssd, health statues says good, it doesnt say end to end error rate like wd. Instead same ID B4 line says "unused reserve nand blocks" instead. Is my ssd good? i havent ran a test on my ram yet.
    This is almost 3 month old build
    Asrock x99x killer
    i7 5820k
    gtx 970
    850w
    crucial 2x4gb
    crucial 256gb ssd
    wd blue 1tb

    Heres info of bsod with bluescreenview
    Bug Check String- IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    Bug Check Code - 0x0000004a
    Parameter 1- 00000000`7709dc4a
    Parameter 2- 00000000`00000002
    Parameter 3- 00000000`00000000
    Parameter 4- fffff880`08167b60
    Caused By Driver- ntoskrnl.exe
    Caused By Address- ntoskrnl.exe+72a40
    File Description- NT Kernel & System
      My Computer


  2. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #2
      My Computer


  3. Posts : 107
    windows 7 pro 64bit
    Thread Starter
       #3

    Sry, here it is.
      My Computer


  4. Posts : 107
    windows 7 pro 64bit
    Thread Starter
       #4

    bump, plz help
      My Computer


  5. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #5

    Right, firstly you can't be bothered to read the instructions emblazoned across the top of the forum to post your issue correctly. Secondly, I had been at work for four hours when you posted your dumps so obviously I couldn't look at them, I still hadn't finished work when you bumped your thread.
    There are plenty of people needing help who have the patience to wait for the free help offered here. If you don't have the patience to wait then I won't have the patience to help you.

    With that said, there are no dump files in your logs to analyse.


    1. Open Advanced System Settings
    2. Click on Settings in Startup & Recovery
    3. Make sure both boxes indicated below are checked
    4. In the dropdown box ensure you're set to record Small Memory Dumps

      My Computer


  6. Posts : 107
    windows 7 pro 64bit
    Thread Starter
       #6

    winkawak said:
    Sry, here it is.
    ==================================================
    Dump File : 042215-9297-01.dmp
    Crash Time : 4/22/2015 2:43:36 AM
    Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
    Bug Check Code : 0x0000004a
    Parameter 1 : 00000000`7709dc4a
    Parameter 2 : 00000000`00000002
    Parameter 3 : 00000000`00000000
    Parameter 4 : fffff880`08167b60
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+72a40
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+72a40
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Users\Jiakai\Desktop\042215-9297-01.dmp
    Processors Count : 12
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 358,568
    Dump File Time : 4/22/2015 2:44:14 AM
    ==================================================

    I also attached the dump file .log since it wont let me upload in .dmp. You have to change it to .dmp.
      My Computer


  7. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #7

    What am I meant do with that?
      My Computer


  8. Posts : 107
    windows 7 pro 64bit
    Thread Starter
       #8

    Im new to this, you say you wanted the dump file i attached it the post above.
      My Computer


  9. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #9

    That's not a dump file. I've shown you in post #5 how to set your computer up to record dump files. When you get a new BSOD, run the DM Log Collector Tool as explained in Blue Screen of Death (BSOD) Posting Instructions and upload the new logs.
      My Computer


  10. Posts : 107
    windows 7 pro 64bit
    Thread Starter
       #10

    Boozad said:
    That's not a dump file. I've shown you in post #5 how to set your computer up to record dump files. When you get a new BSOD, run the DM Log Collector Tool as explained Blue Screen of Death (BSOD) Posting Instructions and upload the new logs.
    So attached file in post #7 is not dump? I changed it to .log so i can upload but you have to change it to.dmp when you download it. I havent had a new bsod yet, is the logs and dmp file not enough?
      My Computer


 
Page 1 of 3 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 15:47.
Find Us