After solving the issue with frequent black outs caused by the graphic card (turns out, I had to buy a new, more powerful PSU), I started having new set of problem. Mainly I start to get frequent BSOD. I then installed a program called WhoCrashed, to figure out the cause. WhoCrashed always says that the driver is an issue, however the weird part is all of my drivers are up to date I think. One of my friend says it might be an issue of my hardware due to being different manufacturer, so here are my specs
AMD Radeon HD 7700 1GB
AMD Phenom(tm) 9500 Quad-Core Processor
3GB of RAM
I also have to note that ever since I bought my computer in 2008, I have changed every component except the motherboard, RAM and processor which if I'd upgrade that would require me to buy a completely new motherboard along with new RAM and processor, which would be way over my budget.
So these crashes occur in 2 cases: When I click something or when windows starts closing my programs before shut down
This is what WhoCrash reported
On Fri 3/21/2014 10:41:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032114-44163-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116483, 0xFFFFF88005DED070, 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 that cannot be identified at this time.
On Fri 3/21/2014 10:41:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116483, 0xFFFFF88005DED070, 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 that cannot be identified at this time.
On Thu 3/20/2014 11:56:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032114-47408-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000166483, 0xFFFFF8800614B070, 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 that cannot be identified at this time.
On Thu 3/6/2014 10:21:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030614-59592-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xBD88)
Bugcheck code: 0x116 (0xFFFFFA800310E010, 0xFFFFF880042F9D88, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
(This happened while I played an online game, after this crash I updated my graphic card to beta drivers, because there are no new drivers ever since december)
On Fri 2/28/2014 11:25:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030114-49935-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C865FE, 0xFFFFF8800798BE40, 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 that cannot be identified at this time.
On Mon 2/17/2014 8:35:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021714-43805-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000204A5FE, 0xFFFFF88008022E40, 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 that cannot be identified at this time.
On Mon 2/10/2014 8:48:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021014-37923-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F6483, 0xFFFFF880070FA070, 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 that cannot be identified at this time.
On Sun 2/9/2014 12:25:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020914-42354-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000726CF9, 0xFFFFF8800670B120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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 that cannot be identified at this time.
On Sat 2/8/2014 7:31:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-45879-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000176483, 0xFFFFF88006ED9070, 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 that cannot be identified at this time.
I try running Device Doctor, it gives me this message
Error executing SQL "select date,version, links filesize from drivers where hardid= "ACPI/ATK0110" and os=7 and vendor ATK"" : no such column: filesize.
The last resort is complete format, but there must be more simpler solution than this. Or is this hardware problem?
AMD Radeon HD 7700 1GB
AMD Phenom(tm) 9500 Quad-Core Processor
3GB of RAM
I also have to note that ever since I bought my computer in 2008, I have changed every component except the motherboard, RAM and processor which if I'd upgrade that would require me to buy a completely new motherboard along with new RAM and processor, which would be way over my budget.
So these crashes occur in 2 cases: When I click something or when windows starts closing my programs before shut down
This is what WhoCrash reported
On Fri 3/21/2014 10:41:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032114-44163-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116483, 0xFFFFF88005DED070, 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 that cannot be identified at this time.
On Fri 3/21/2014 10:41:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000116483, 0xFFFFF88005DED070, 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 that cannot be identified at this time.
On Thu 3/20/2014 11:56:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032114-47408-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000166483, 0xFFFFF8800614B070, 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 that cannot be identified at this time.
On Thu 3/6/2014 10:21:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030614-59592-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xBD88)
Bugcheck code: 0x116 (0xFFFFFA800310E010, 0xFFFFF880042F9D88, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
(This happened while I played an online game, after this crash I updated my graphic card to beta drivers, because there are no new drivers ever since december)
On Fri 2/28/2014 11:25:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030114-49935-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C865FE, 0xFFFFF8800798BE40, 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 that cannot be identified at this time.
On Mon 2/17/2014 8:35:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021714-43805-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000204A5FE, 0xFFFFF88008022E40, 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 that cannot be identified at this time.
On Mon 2/10/2014 8:48:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021014-37923-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F6483, 0xFFFFF880070FA070, 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 that cannot be identified at this time.
On Sun 2/9/2014 12:25:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020914-42354-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x6CF9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000726CF9, 0xFFFFF8800670B120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display 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 that cannot be identified at this time.
On Sat 2/8/2014 7:31:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020814-45879-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC6483)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000176483, 0xFFFFF88006ED9070, 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 that cannot be identified at this time.
I try running Device Doctor, it gives me this message
Error executing SQL "select date,version, links filesize from drivers where hardid= "ACPI/ATK0110" and os=7 and vendor ATK"" : no such column: filesize.
The last resort is complete format, but there must be more simpler solution than this. Or is this hardware problem?
Facebook
Twitter
Instagram