1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Windows 7 - BSOD while playing games

Discussion in 'Windows 7' started by Benjamin92, Jan 26, 2013.

Thread Status:
Not open for further replies.
  1. Benjamin92

    Benjamin92 Thread Starter

    Joined:
    Jan 26, 2013
    Messages:
    1
    Hi there!

    I've been experiencing very frequent BSODs while playing my games. I rarely get the BSODs if I avoid playing my games altogether, hence I suspect it has to do with my video card, or updating its driver or something. Anyway, please see attached report from WhoCrashed.

    I've also attached the actual dump files for your perusal.

    Really appreciate the help, thanks!

    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 26/1/2013 11:35:12 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012613-17799-01.dmp
    This was probably caused by the following module: Unknown (0x00000000)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8D3D3BAC, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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.
    A third party driver was identified as the probable root cause of this system error.
    Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Sat 26/1/2013 11:35:12 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
    Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8D3D3BAC, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
    Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
    Google query: ntkrpamp.exe KERNEL_MODE_EXCEPTION_NOT_HANDLED



    On Sat 26/1/2013 11:31:42 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012613-12604-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x40CDB)
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF830EF869)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 26/1/2013 4:23:03 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012613-15069-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0xA06C0)
    Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0079CE0, 0x75C17867, 0xFFFFFFFFC0069CE0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    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 25/1/2013 3:17:47 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-30778-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x98BD0)
    Bugcheck code: 0xA (0x703C5C80, 0x2, 0x0, 0xFFFFFFFF82ED9D83)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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 25/1/2013 5:48:40 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-38579-01.dmp
    This was probably caused by the following module: symevent.sys (SYMEVENT+0x10353)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF92A47353, 0xFFFFFFFFB25752E4, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys .
    Google query: symevent.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Fri 25/1/2013 5:29:07 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-43836-01.dmp
    This was probably caused by the following module: srtsp.sys (SRTSP+0x608C0)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF928808C0, 0xFFFFFFFF8E192C88, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: srtsp.sys .
    Google query: srtsp.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



    On Fri 25/1/2013 5:26:41 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-41340-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x3C3159)
    Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFF999D5159)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Thu 24/1/2013 11:15:57 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012413-43898-01.dmp
    This was probably caused by the following module: symevent.sys (SYMEVENT+0x17289)
    Bugcheck code: 0x1A (0x41284, 0xF0E8001, 0x17CBF, 0xFFFFFFFFC0802000)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys .
    Google query: symevent.sys MEMORY_MANAGEMENT



    On Sun 20/1/2013 6:06:22 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012013-30420-01.dmp
    This was probably caused by the following module: unknown_module_00000001.sys (Unloaded_Unknown_Module_00000001+0x778596DF)
    Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFF9F7F5159)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000001.sys .
    Google query: unknown_module_00000001.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Tue 25/12/2012 12:12:30 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122512-28828-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x132159)
    Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFFA2954159)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Tue 25/12/2012 9:51:26 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122512-30030-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x132159)
    Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFFA055B159)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



    On Mon 24/12/2012 4:56:47 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010102-54506-01.dmp
    This was probably caused by the following module: symevent.sys (SYMEVENT+0x17289)
    Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC001B608, 0x4E8F9867, 0xFFFFFFFFC000B608)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symevent.sys .
    Google query: symevent.sys MEMORY_MANAGEMENT



    On Mon 24/12/2012 4:54:41 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122412-36909-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x7FA9F)
    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF82ED9CC2, 0xFFFFFFFF8E1C7BD0, 0xFFFFFFFF8E1C77B0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
    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 20/12/2012 10:53:39 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122012-29874-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1FF3F)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9E488F3F, 0xFFFFFFFF8FC379D4, 0xFFFFFFFF8FC375B0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    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 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.
    Google query: Microsoft Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



    Conclusion
    44 crash dumps have been found and analyzed. Only 15 are included in this report. 9 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:

    dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)
    tmevtmgr.sys (TrendMicro Event Management Module, Trend Micro Inc.)
    atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
    srtsp.sys
    unknown_module_00000001.sys
    unknown_module_5b1848a4.sys
    ntkrpamp.exe
    symevent.sys
    hal.sys

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


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
     

    Attached Files:

  2. dai

    dai

    Joined:
    Mar 6, 2003
    Messages:
    11,198
    what are you running
    video card brand and model
    cpu
    m/board
    ram
    power supply
    brand
    model
    wattage

    check the listings in the bios for 12v line voltages and cpu temperatures and post them


    in the device manager uninstall the video card
    reboot tapping f8 and choose low resolution mode
    when windows finishes rebooting
    disable a/virus
    install your drivers
    reboot the computer
     
As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1086915

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice