Solved

What does this mean

Recently my PC crashed and I ran WhoCrashed, but I have no idea what this means.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 08-11-2013 10:01:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110813-25708-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005250060, 0xFFFFFA8005250340, 0xFFFFF80002B83260)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


On Fri 08-11-2013 10:01:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005250060, 0xFFFFFA8005250340, 0xFFFFF80002B83260)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Case - iBall Entizer
Motherboard - Intel DH87RL
Processor - Intel i5-4430 @ 3.0 GHz
RAM - Kingston 4 GB RAM @ 1333 MHz
Video Card - Nvidia GeForce 9400 GT
HDD - Seagate Barracuda 2 TB @ 7200 RPM
PSU - Cooler Master Elite 350W
OS - Windows 7 Ultimate 64-Bit
30 answers Last reply Best Answer
More about question
  1. It means something crashed in your OS

    Error reports like that I bet even Microsoft employees wouldn't be able to interpret, the reasons for a system crash are many and varied. If your PC isnt doing this consistently or showing other problems, I would put it down to a random occurrence.
  2. couple of things:

    "...This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue...."

    a) drivers: check if you have all the drivers updated, go to computer > properties > device manager, also check motherboard firmware version update
    b) thermals: check if your cpu thermals are good, does your motherboard bios report cpu temps? is your fan working properly, have you tinkered with its speed in the bios?
  3. Half Life said:
    couple of things:

    "...This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue...."

    a) drivers: check if you have all the drivers updated, go to computer > properties > device manager, also check motherboard firmware version update
    b) thermals: check if your cpu thermals are good, does your motherboard bios report cpu temps? is your fan working properly, have you tinkered with its speed in the bios?



    All drivers from CD that I got with Mobo

    CPU i5 4430 has stock cooler

    No tinkering .... except I set the cooling for processor from quiet to balanced.

    Coretemp reports 30-35 degrees Celsius on idle which jumps up to 40-45 on gaming.
  4. ok temps are good,actually great so that's ruled out

    drivers - what's your mobo model, stupid question, should have read your first post a little more carefully; how old is your pc and bios version; why i ask is because the ones that come with the board need not be the latest, call me superstitious but this haswell thingy generally needs a bios flashing; so just checking that side; also you do have to do what i mentioned in point (a) when you are connected to the internet just to make sure you rule that out
  5. Half Life said:
    ok temps are good,actually great so that's ruled out

    drivers - what's your mobo model, stupid question, should have read your first post a little more carefully; how old is your pc and bios version; why i ask is because the ones that come with the board need not be the latest, call me superstitious but this haswell thingy generally needs a bios flashing; so just checking that side; also you do have to do what i mentioned in point (a) when you are connected to the internet just to make sure you rule that out


    bought hdd, mobo and proc 1 month ago.... rest all is 4-5 yrs old... will get my gtx 760 delivered on 16th along with 600W PSU.

    so basically right now, case, gpu and psu are old (optical drive i disconnected as i didnt need)

    i updated BIOS from intel's site as the guy I bought it from recommended me to do it the first thing.

    Sorry for asking, but how can I check if all my drivers are up to date with the help of the internet?

    Do I have to do it manually 1 by 1?
  6. yep, manually. let me rephrase it just to be safe - i only know of doing it manually, there may be a better way but i do not know; it's not as bad as you think it will be, half an hour of patience and a bunch of right clicks and all your drivers are updated, this wont guarantee a resolution though

    here, this will help you
  7. Half Life said:
    yep, manually. let me rephrase it just to be safe - i only know of doing it manually, there may be a better way but i do not know; it's not as bad as you think it will be, half an hour of patience and a bunch of right clicks and all your drivers are updated, this wont guarantee a resolution though

    here, this will help you


    On intel's website under support for my mobo, there is a free download that says check and update all drivers so I will use that......

    Its late in the night here now so I will unfortunately have to communicate further tomorrow.
  8. Best answer
    Just be careful there are a lot of those driver check free-wares around the internet and most are scams. Only trust the manufacturers and well know companies programs in that regard. as far as the original problem it looks like there was a kernel error which is an error internal to the OS. You may need to repair your os using the install disk. or even in a worst case scenario you may need to reinstall. Sometimes its not worth the hassle to try and hunt down those internal errors. I usually just back up what I can and start over...
  9. tougas said:
    Just be careful there are a lot of those driver check free-wares around the internet and most are scams. Only trust the manufacturers and well know companies programs in that regard. as far as the original problem it looks like there was a kernel error which is an error internal to the OS. You may need to repair your os using the install disk. or even in a worst case scenario you may need to reinstall. Sometimes its not worth the hassle to try and hunt down those internal errors. I usually just back up what I can and start over...



    I just re-installed 4 days ago because Windows had gotten corrupt. I don't have an install disk, but I haven't seen any more BSOD's, so if I do see one again I will tell you.
  10. tougas said:
    Just be careful there are a lot of those driver check free-wares around the internet and most are scams. Only trust the manufacturers and well know companies programs in that regard. as far as the original problem it looks like there was a kernel error which is an error internal to the OS. You may need to repair your os using the install disk. or even in a worst case scenario you may need to reinstall. Sometimes its not worth the hassle to try and hunt down those internal errors. I usually just back up what I can and start over...



    Oh well I got a BSOD again.....

    Here is the report by Who Crashed, hope you have any idea what this means:-

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 09-11-2013 15:02:50 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110913-29671-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
    Bugcheck code: 0x7A (0xFFFFF6FC4001C8B0, 0xFFFFFFFFC000000E, 0x88FA3BE0, 0xFFFFF88003916000)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sat 09-11-2013 15:02:50 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x7A (0xFFFFF6FC4001C8B0, 0xFFFFFFFFC000000E, 0x88FA3BE0, 0xFFFFF88003916000)
    Error: KERNEL_DATA_INPAGE_ERROR
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  11. It happened again!


    Seriously, I don't want to reinstall Windows... What should I do??

    Please, if you want a list of all installed drivers, software or something like that I will send it.

    Meanwhile, here's the Who Crashed report :-

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 09-11-2013 18:19:49 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110913-34866-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
    Bugcheck code: 0x7A (0xFFFFF6FC500174E0, 0xFFFFFFFFC000000E, 0x293D5880, 0xFFFFF8A002E9CF40)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sat 09-11-2013 18:19:49 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x653A9)
    Bugcheck code: 0x7A (0xFFFFF6FC500174E0, 0xFFFFFFFFC000000E, 0x293D5880, 0xFFFFF8A002E9CF40)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  12. Might be worth checking your HDD health considering this is a fresh windows install. Go to you HDD brands site and they should have a diagnostic tool.
  13. FastGunna said:
    Might be worth checking your HDD health considering this is a fresh windows install. Go to you HDD brands site and they should have a diagnostic tool.


    I have a Seagate Barracuda 2 TB and I can't find any diagnostic tool on Seagate's website. Where is this diagnostic tool for Seagate HDD? Also, I don't think HDD is the problem as it is 1 month old.

    If it is, its still under warranty.
  14. FastGunna said:
    Might be worth checking your HDD health considering this is a fresh windows install. Go to you HDD brands site and they should have a diagnostic tool.


    Again :-

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 09-11-2013 19:48:18 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ataport.sys (ataport+0x1C4AC)
    Bugcheck code: 0x7A (0xFFFFF6FC40007BE8, 0xFFFFFFFFC000009D, 0x110C3D860, 0xFFFFF88000F7D4AC)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\ataport.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: ATAPI Driver Extension
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  15. This is frustrating.... again!!!!

    On Sat 09-11-2013 19:58:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111013-35677-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005A1E060, 0xFFFFFA8005A1E340, 0xFFFFF80002DD17B0)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sat 09-11-2013 19:58:23 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005A1E060, 0xFFFFFA8005A1E340, 0xFFFFF80002DD17B0)
    Error: CRITICAL_OBJECT_TERMINATION
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  16. Sorry I took so long.

    http://www.seagate.com/support/downloads/seatools/

    Just go to the downloads tab and select sea tools for windows.
  17. FastGunna said:
    Sorry I took so long.

    http://www.seagate.com/support/downloads/seatools/

    Just go to the downloads tab and select sea tools for windows.


    Thanks... I found this by myself just a minute ago.....

    I did the Fix All Fast, S.M.A.R.T Check, Short Generic and Short Drive Self Test and all passed without any errors.
  18. Well it was worth checking. At least you can rule hard drive failure out.

    What exactly are you doing when it crashes?
  19. FastGunna said:
    Well it was worth checking. At least you can rule hard drive failure out.

    What exactly are you doing when it crashes?


    Mostly just browsing the web using Google Chrome, with Kaspersky Anti-Virus and Xfire (not always) running in the background.

    The latest crash happened while I was taking a typing speed test on www.goodtyping.com

    Edit: Oh I also always have CoreTemp running in the background.
  20. My God it happened again......

    This time too browsing on net......

    I also forgot to mention (really sorry) that I ALWAYS hear a short beep from my motherboard before each and every one of those damn BSOD's

    Will have to communicate further tomorrow.

    Here's the report for this latest one:-

    On Sat 09-11-2013 20:42:16 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111013-26161-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0xEED18)
    Bugcheck code: 0x7A (0xFFFFF6FC4000DA20, 0xFFFFFFFFC000000E, 0x83972860, 0xFFFFF88001B44D18)
    Error: KERNEL_DATA_INPAGE_ERROR
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  21. Well I don't know enough to provide anymore help unfortunately.
  22. Look like a faulty stick of ram.
    Run Memtest
  23. lp231 said:
    Look like a faulty stick of ram.
    Run Memtest


    OK..... I had run MemTest86+ for about 20 mins... no errors. I'm sorry I forgot to mention this but I'm just too frustrated....... can't think properly.
  24. If a clean install still causes a bsod, then it's most likely your board.
    Remove the graphic card and use onboard and see if it still bsod.
    Update your USB 3.0 drivers
    https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Software+Products&ProductLine=Chipset+Software&ProductProduct=Intel%C2%AE+USB+3.0+eXtensible+Host+Controller+Driver
  25. It sounds more like a hardware failure. I hate to say it but you may be having a MOBO failure. I had a similar issue with my laptop a while back. I ended up having to get it replaced. I would go through and check and clean your hardware.
  26. Well if it is a mobo failure, then in that case the mobo is still under warranty.

    But how can I definitely pin down the problem as being the motherboard?

    I ran check disk on C which gave no errors as well as Windows' in-built memory test whose both passes passed.
  27. Another Blue Screen....

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 10-11-2013 15:48:55 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111013-16177-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005719B30, 0xFFFFFA8005719E10, 0xFFFFF80002DD97B0)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sun 10-11-2013 15:48:55 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005719B30, 0xFFFFFA8005719E10, 0xFFFFF80002DD97B0)
    Error: CRITICAL_OBJECT_TERMINATION
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  28. Another...

    On Sun 10-11-2013 16:31:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111013-39265-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA80056F0B30, 0xFFFFFA80056F0E10, 0xFFFFF80002DC77B0)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Sun 10-11-2013 16:31:15 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA80056F0B30, 0xFFFFFA80056F0E10, 0xFFFFF80002DC77B0)
    Error: CRITICAL_OBJECT_TERMINATION
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  29. If its still under warranty then bring it to where ever you purchased it. Its their problem to fix it. I think its just a bad board.
  30. Oh well I'll see what happens.
Ask a new question

Read More

Windows Crash Systems