Hello firstly.
I would like to ask for a few suggestions to solve my problem.
Lately I experience often the BSOD, it just comes up when playing a game for some amount of time.
I have tried to find a way to solve the problem on the internet but I still couldn't find it.
Here is some of the things that I have found out:
I would like to ask for a few suggestions to solve my problem.
Lately I experience often the BSOD, it just comes up when playing a game for some amount of time.
I have tried to find a way to solve the problem on the internet but I still couldn't find it.
Here is some of the things that I have found out:
Code:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 6/5/2012 5:06:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060512-22432-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88007DC6912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Tue 6/5/2012 5:06:09 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88007DC6912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Tue 6/5/2012 4:36:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060512-17440-01.dmp
This was probably caused by the following module: rtkvhd64.sys (RTKVHD64+0x3C545B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880087DE45B, 0xFFFFF8800B2244D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\rtkvhd64.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function 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.
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: rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: rtkvhd64.sys Realtek Semiconductor Corp. SYSTEM_SERVICE_EXCEPTION
On Tue 6/5/2012 2:25:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060512-18080-01.dmp
This was probably caused by the following module: rtkvhd64.sys (RTKVHD64+0x3C545B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800880F45B, 0xFFFFF8800AF5D4D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\rtkvhd64.sys
product: Realtek(r) High Definition Audio Function Driver
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function 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.
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: rtkvhd64.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: rtkvhd64.sys Realtek Semiconductor Corp. SYSTEM_SERVICE_EXCEPTION
On Tue 5/22/2012 2:38:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052212-22900-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004970038, 0xB269C000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sun 5/6/2012 8:35:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050612-18766-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004932038, 0xB269C000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 3/22/2012 1:22:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032212-19453-01.dmp
This was probably caused by the following module: rdbss.sys (rdbss+0x11782)
Bugcheck code: 0x27 (0xBAAD0073, 0xFFFFF880032A20A8, 0xFFFFF880032A1910, 0xFFFFF88006376126)
Error: RDR_FILE_SYSTEM
file path: C:\Windows\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
Bug check description: This indicates that a problem occurred in the SMB redirector file system.
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 Sat 3/17/2012 10:46:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-17269-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004927038, 0xB269C000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sat 3/17/2012 10:40:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-17409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x50 (0xFFFFE88007DD9470, 0x0, 0xFFFFF88007445F37, 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 Sat 3/17/2012 10:32:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-17238-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004CF5038, 0xB269C000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sat 3/17/2012 10:18:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-18298-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80046BE028, 0xB269C000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sat 3/17/2012 10:12:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031712-18345-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004936038, 0xB26CC000, 0x175)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Wed 2/8/2012 4:30:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020812-22432-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFE88009D47470, 0x0, 0xFFFFF880074BFF37, 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.
