Windows 7 - BSOD while playing games

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

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!

[FONT=Segoe UI, Arial]Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]Unknown[/FONT] (0x00000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8D3D3BAC, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
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: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntkrpamp.exe[/FONT] (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8D3D3BAC, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED[/FONT]
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: [FONT=Segoe UI, Arial]ntkrpamp.exe KERNEL_MODE_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x40CDB)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF830EF869)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntkrnlpa.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0xA06C0)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC0079CE0, 0x75C17867, 0xFFFFFFFFC0069CE0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntkrnlpa.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0x98BD0)
Bugcheck code: 0xA (0x703C5C80, 0x2, 0x0, 0xFFFFFFFF82ED9D83)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]symevent.sys[/FONT] (SYMEVENT+0x10353)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF92A47353, 0xFFFFFFFFB25752E4, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
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: [FONT=Segoe UI, Arial]symevent.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]srtsp.sys[/FONT] (SRTSP+0x608C0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF928808C0, 0xFFFFFFFF8E192C88, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
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: [FONT=Segoe UI, Arial]srtsp.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]atikmdag.sys[/FONT] (atikmdag+0x3C3159)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFF999D5159)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\atikmdag.sys
product: [FONT=Segoe UI, Arial]ATI Radeon Family[/FONT]
company: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc.[/FONT]
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: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]symevent.sys[/FONT] (SYMEVENT+0x17289)
Bugcheck code: 0x1A (0x41284, 0xF0E8001, 0x17CBF, 0xFFFFFFFFC0802000)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
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: [FONT=Segoe UI, Arial]symevent.sys MEMORY_MANAGEMENT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]unknown_module_00000001.sys[/FONT] (Unloaded_Unknown_Module_00000001+0x778596DF)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFF9F7F5159)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
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: [FONT=Segoe UI, Arial]unknown_module_00000001.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]atikmdag.sys[/FONT] (atikmdag+0x132159)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFFA2954159)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\atikmdag.sys
product: [FONT=Segoe UI, Arial]ATI Radeon Family[/FONT]
company: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc.[/FONT]
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: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]atikmdag.sys[/FONT] (atikmdag+0x132159)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x1, 0xFFFFFFFFA055B159)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\atikmdag.sys
product: [FONT=Segoe UI, Arial]ATI Radeon Family[/FONT]
company: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc.[/FONT]
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: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]symevent.sys[/FONT] (SYMEVENT+0x17289)
Bugcheck code: 0x1A (0x403, 0xFFFFFFFFC001B608, 0x4E8F9867, 0xFFFFFFFFC000B608)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
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: [FONT=Segoe UI, Arial]symevent.sys MEMORY_MANAGEMENT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntkrnlpa.exe[/FONT] (nt+0x7FA9F)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF82ED9CC2, 0xFFFFFFFF8E1C7BD0, 0xFFFFFFFF8E1C77B0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntkrnlpa.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.


[/FONT]
[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x1FF3F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF9E488F3F, 0xFFFFFFFF8FC379D4, 0xFFFFFFFF8FC375B0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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: [FONT=Segoe UI, Arial]Microsoft Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]
[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]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:

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

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.
[/FONT]
 

Attachments

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
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

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 807,865 other people just like you!

Latest posts

Staff online

Members online

Top