Solved

Blue screen of death errors

I'm having a problem with these errors, it's started to sicken me.. Where is any fix to fix it instead of buying new pc?
Pictures: http://prntscr.com/f7bexs , http://prntscr.com/f7bf4l (the most common) , http://prntscr.com/f7bfni (PC info) . Please help me
Reply to Toffy122
14 answers Last reply Best Answer
More about blue screen death errors
  1. Toffy122 said:
    I'm having a problem with these errors, it's started to sicken me.. Where is any fix to fix it instead of buying new pc?
    Pictures: http://prntscr.com/f7bexs , http://prntscr.com/f7bf4l (the most common) , http://prntscr.com/f7bfni (PC info) . Please help me


    Also, it's usually happening then I watching youtube or other flash videos on browser.
    Reply to Toffy122
  2. this is like blue screen view but formats the results different - Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

    Copy/paste summary in here and I see what I can do :)
    Reply to Colif
  3. Colif said:
    this is like blue screen view but formats the results different - Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

    Copy/paste summary in here and I see what I can do :)


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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 2017.05.13 13:32:29 your computer crashed
    crash dump file: C:\Windows\Minidump\051317-21171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7F376)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002ADD376, 0xFFFFF88002FC07D8, 0xFFFFF88002FC0030)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    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 system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    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 2017.05.13 12:53:49 your computer crashed
    crash dump file: C:\Windows\Minidump\051317-20125-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
    Bugcheck code: 0x50 (0xFFFFF683FFFFFFF8, 0x0, 0xFFFFF80002AFE8DF, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    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 2017.05.12 22:02:54 your computer crashed
    crash dump file: C:\Windows\Minidump\051217-20500-01.dmp
    This was probably caused by the following module: tcpip.sys (tcpip+0x1A1DC0)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Operacine sistema Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP tvarkykle
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    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.


    On Fri 2017.05.12 19:50:01 your computer crashed
    crash dump file: C:\Windows\Minidump\051217-23968-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
    Bugcheck code: 0x50 (0xFFFFFCF9013AEAEB, 0x0, 0xFFFFF80002A6A5EF, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Thu 2017.05.11 16:57:53 your computer crashed
    crash dump file: C:\Windows\Minidump\051117-21109-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A4174A, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    29 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    aswsnx.sys (Avast Virtualization Driver, AVAST Software)
    igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

    Maybe it's because I cant run windows 7 ? I cant find here https://downloadcenter.intel.com/product/81527/Graphics-Drivers-for-Intel-82915G-82910GL-Express-Chipset-Family right driver for windows 7 only xp and others.
    Reply to Toffy122
  4. One is caused by Avast, check you have latest version

    other by Intel graphics drivers so once again, check you have latest for your CPU

    there may be more, can you upload copies of the minidumps and share links here and someone might go through them and see if any other problems.
    Reply to Colif
  5. Colif said:
    One is caused by Avast, check you have latest version

    other by Intel graphics drivers so once again, check you have latest for your CPU

    there may be more, can you upload copies of the minidumps and share links here and someone might go through them and see if any other problems.


    Yeah Avast version was old so I updating now.
    My graphics drivers are latest I think. I cant find newer than this http://prntscr.com/f7eax1 . Maybe it's because my video card not support 7 only xp?
    official drivers for my graphic https://downloadcenter.intel.com/product/81527/Graphics-Drivers-for-Intel-82915G-82910GL-Express-Chipset-Family i cant find one with windows 7.
    Reply to Toffy122
  6. Is this your board? only based on chipset - https://downloadcenter.intel.com/product/23503/Intel-Desktop-Board-D946GZIS

    cause it has Vista drivers and they would work on Windows 7, XP is a stretch yet they seem to have worked until now.
    Reply to Colif
  7. Colif said:
    Is this your board? only based on chipset - https://downloadcenter.intel.com/product/23503/Intel-Desktop-Board-D946GZIS

    cause it has Vista drivers and they would work on Windows 7, XP is a stretch yet they seem to have worked until now.


    Yes this is my board.
    I found these one https://downloadcenter.intel.com/download/18228/Intel-Graphics-Media-Accelerator-Driver-for-Windows-7-64-exe- I give it a try if no I think I will buy external video card maybe it will help..
    Reply to Toffy122
  8. looks like right board, if you running 64bit, go for it
    Reply to Colif
  9. Ok, I was watching youtube and like other times pc restarted but without bsod :D Just turned black and restarted...
    Reply to Toffy122
  10. since i can't read dumps, i may have missed something so wait and see if anyone reads them
    Reply to Colif
  11. I recently got after updating graphics new bsod...

    On Sun 2017.05.14 00:20:57 your computer crashed
    crash dump file: C:\Windows\Minidump\051417-13437-01.dmp
    This was probably caused by the following module: wdf01000.sys (Wdf01000+0x81CC)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000E171CC, 0xFFFFF8800594DFB0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\wdf01000.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Kernel Mode Driver Framework Runtime
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    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.
    Reply to Toffy122
  12. Best answer
    2 options.

    1. if no one reads the dump files, I would read instructions at top of this page and post on these forums as they should find an answer for you faster than waiting here - https://www.sevenforums.com/bsod-help-support/

    or 2. In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

    Once it bsod, run Who crashed and see what driver it reveals

    note: sometimes this will put you into a boot loop so it helps to have a win 7 installer handy to get out again


    The instructions to stop it are in the link above I will show u anyway
    change boot order in bios so USB/DVD is first, hdd second
    boot from installer
    on screen after languages, choose repair this pc, not install.
    press alt shift F10 to access command prompt
    type verifer /reset and press enter
    restart PC
    Reply to Colif
  13. Colif said:
    2 options.

    1. if no one reads the dump files, I would read instructions at top of this page and post on these forums as they should find an answer for you faster than waiting here - https://www.sevenforums.com/bsod-help-support/

    or 2. In case no one looks at this for a while, you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

    Once it bsod, run Who crashed and see what driver it reveals

    note: sometimes this will put you into a boot loop so it helps to have a win 7 installer handy to get out again


    The instructions to stop it are in the link above I will show u anyway
    change boot order in bios so USB/DVD is first, hdd second
    boot from installer
    on screen after languages, choose repair this pc, not install.
    press alt shift F10 to access command prompt
    type verifer /reset and press enter
    restart PC


    Thanks a lot for helping, I think I will use 1 option but till then I will test some thing like watching youtube on other broswer or play heavy game to stress pc see if it gives more bsod and will post them on that site. Thanks!
    Reply to Toffy122
Ask a new question Answer

Read More

Windows 7 Blue Screen