Computer - HP Laptop Pavillion Entertainment PC DV4, 2009
Windows 7, Version 6.1 (Build 7601: Service Pack 1) 64 bit
I have been getting this for a while and have been doing system restores to see if that would help, but it continues. I installed BlueScreenView and have already had the BSOD today. I also have problems with overheating. Here is what it reports, and any help is greatly appreciated. I'm attaching it because it won't paste correctly on here.
Please download WhoCrashed (scroll down to Crash Analysis Tool) to your desktop.
1) Click on the file you just downloaded and run it.
2) Put a tick in Accept then click on Next
3) Tick Don't create a start menu folder / click Next
4) Tick Create a Desktop Icon / click on Install / tick Launch Whocrashed / click Finish
5) Click Analyze
It will want to download the Debugger and install it / Yes
WhoCrashed will create report /.scroll down to see it
Copy and paste it into your next reply.
With regard to your Laptop overheating issue, make sure your air intake vents are clear and you are operating your laptop on a flat surface.
Overheating may have something to do with your PC crashing ..or maybe not.
To check your temps you can download Speedfan.
Let us know what they are.
Here are the results. Note that I also did a hardware check and no problems were found. I ran a driver check and none showed up that needed updating.
System Information (local)
——————————————————————————–
computer name: ADASHA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Turion™ II Dual-Core Mobile M520 AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4022542336 total
VM: 2147352576, free: 1982128128
——————————————————————————–
Crash Dump Analysis
——————————————————————————–
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 1/25/2012 7:04:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012512-15662-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034CCCD3, 0xFFFFF88007B93240, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 1/25/2012 7:04:05 PM 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: 0x3B (0xC0000005, 0xFFFFF800034CCCD3, 0xFFFFF88007B93240, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 1/25/2012 6:24:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012512-16068-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF88009164220, 0x0, 0xFFFFF8000348DDEC, 0x0)
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 which cannot be identified at this time.
On Wed 1/25/2012 3:42:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012512-18220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88000FC4D05)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 1/25/2012 2:53:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012512-17004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x8000101625, 0x2, 0x1, 0xFFFFF80002D153A2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 which cannot be identified at this time.
On Tue 1/17/2012 3:26:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-16504-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x259C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004E4759C, 0xFFFFF8800678D0E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 which cannot be identified at this time.
On Tue 1/17/2012 1:58:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-16161-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF00002CD6F93, 0x8, 0xFFFFF00002CD6F93, 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 which cannot be identified at this time.
On Mon 1/16/2012 2:14:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-13462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF84D4F432E55, 0x0, 0xFFFFF88004D909F8, 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 which cannot be identified at this time.
On Wed 1/4/2012 10:01:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010412-15132-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_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 power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Sun 12/25/2011 2:50:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122511-15756-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC3FEF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000193FEF, 0xFFFFF88002D310C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 which cannot be identified at this time.
On Fri 12/23/2011 7:05:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122311-15974-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD2BB6, 0xFFFFF88002C8CBA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 12/22/2011 11:00:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122211-29905-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x37F0FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004C6D0FD, 0xFFFFF88005CDF9E8, 0xFFFFF88005CDF240)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 12/20/2011 7:18:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-21512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_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 power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Sun 12/18/2011 3:49:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121711-28938-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFA80042C71A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFA80042C71A0, 0xFFFFF880037FBBA8, 0xFFFFF880037FB400)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
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 .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 12/6/2011 10:56:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120611-16161-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x37F0FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880049BA0FD, 0xFFFFF880062E39E8, 0xFFFFF880062E3240)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
——————————————————————————–
Conclusion
——————————————————————————–
51 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
unknown_module_00000000`00000001.sys
unknown
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.
It appears you have a third party video driver that may be the cause of the problems with two Windows drivers.
I think this atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.) is an integrated driver, not a video-card driver.
First thing to do is to uninstall the video driver, reboot and let W7 replace it.
To uninstall video driver go to start / right-click / Computer / manage / Device manager /expand display or video adapters / right-cllick what it shows and choose "uninstall". The system will need to re-start.
Now go to this page http://www8.hp.com/us/en/support-drivers.html which will take you to HP Driver and software support. Click on "automatically find your products and solutions" and update what is recommended. A small active-X will need to be installed so make sure you right-click IE and choose "run as administrator".
If you wish to do a manual update from the above HP page, be aware that "More than 300 products contain the term HP Laptop Pavillion Entertainment PC DV4" so you would need to supply you product and/or SKU number (if known).
See how that goes and if it fixes the crashing problem.
If not, run WhoCrashed again and post the new results
Ok, and thanks again for your help.
I did the above and it all went through. Then, crash again…
Here are the results of WhoCrashed:
System Information (local)
——————————————————————————–
computer name: ADASHA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Turion™ II Dual-Core Mobile M520 AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4022542336 total
VM: 2147352576, free: 1978748928
——————————————————————————–
Crash Dump Analysis
——————————————————————————–
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 1/27/2012 7:00:41 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x8FA17)
Bugcheck code: 0x50 (0xFFFFBA8003A81FBA, 0x0, 0xFFFFF80002D9202C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 1/26/2012 9:50:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012612-39811-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000001.sys (Unloaded_Unknown_Module_00000000`00000001+0x1)
Bugcheck code: 0xA (0x18, 0x2, 0x0, 0xFFFFF80002CD1F35)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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_00000000`00000001.sys .
Google query: unknown_module_00000000`00000001.sys IRQL_NOT_LESS_OR_EQUAL
On Thu 1/19/2012 4:09:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011912-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x88, 0x2, 0x1, 0xFFFFF80002C793A6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 which cannot be identified at this time.
On Thu 1/19/2012 12:34:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011812-17440-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0xCA72, 0xCA74000196E4)
Error: MEMORY_MANAGEMENT
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 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 which cannot be identified at this time.
On Tue 1/17/2012 3:26:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-16504-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x259C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004E4759C, 0xFFFFF8800678D0E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 which cannot be identified at this time.
On Tue 1/17/2012 1:58:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-16161-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF00002CD6F93, 0x8, 0xFFFFF00002CD6F93, 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 which cannot be identified at this time.
On Mon 1/16/2012 2:14:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-13462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF84D4F432E55, 0x0, 0xFFFFF88004D909F8, 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 which cannot be identified at this time.
On Wed 1/4/2012 10:01:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010412-15132-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_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 power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Sun 12/25/2011 2:50:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122511-15756-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC3FEF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000193FEF, 0xFFFFF88002D310C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 which cannot be identified at this time.
On Fri 12/23/2011 7:05:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122311-15974-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD2BB6, 0xFFFFF88002C8CBA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 12/22/2011 11:00:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122211-29905-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x37F0FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004C6D0FD, 0xFFFFF88005CDF9E8, 0xFFFFF88005CDF240)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 12/20/2011 7:18:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-21512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_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 power policy manager experienced a fatal error.
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 which cannot be identified at this time.
On Sun 12/18/2011 3:49:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121711-28938-01.dmp
This was probably caused by the following module: Unknown (0xFFFFFA80042C71A0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFA80042C71A0, 0xFFFFF880037FBBA8, 0xFFFFF880037FB400)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
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 .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 12/6/2011 10:56:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120611-16161-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x37F0FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880049BA0FD, 0xFFFFF880062E39E8, 0xFFFFF880062E3240)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
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.
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, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 11/29/2011 2:49:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-22152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA0 (0x9, 0xFFFFFFFFC0000001, 0x1, 0x0)
Error: INTERNAL_POWER_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 power policy manager experienced a fatal error.
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 which cannot be identified at this time.
——————————————————————————–
Conclusion
——————————————————————————–
51 crash dumps have been found and analyzed. Only 15 are included in this report. 3 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:
atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)
unknown
unknown_module_00000000`00000001.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.
