as requested the graphics card is = ATI Radeon HD 5700 Series
the pc has been here for 3 months because i bought it on ebay, however the guy was legitimate and the system was fine when i got it. I have caused the problem somehow indirectly.
What is the make and model of the computer please if branded
Gigabyte Technology Co., Ltd. P55-US3L
Enclosure Type: Desktop
best i can come up with if this is not what you need please tell me.
What operating system
Windows 7 64 bit ultimate edition.
What motherboard please if not branded
GA-P55-US3L
http://uk.gigabyte.c...pid=3294#driver^^ that looks identical so i presume.
Have you always had this problem is it a new system
Its newish i have had it for about 3 months it was alright for a while. month or so
If not when did the problem first occur please
start with a boot to safe mode please and run a chkdsk /r
It said windows found no problems
and then a system file check on sfc /scannow from the cmd prompt
it said no problems yet again.
See if you can get me a who crashed report please
click the analyse tab and copy and paste the actual results please.
Download the free edition
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 17/06/2012 16:42:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x9C (0x0, 0xFFFFF880031DBB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 MACHINE_CHECK_EXCEPTION
On Fri 15/06/2012 16:25:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061512-17472-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA80C2B75EE0, 0x2, 0x0, 0xFFFFF800030DE2DB)
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 Fri 15/06/2012 02:33:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061512-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x100F66EB0, 0x2, 0x1, 0xFFFFF800030A5F93)
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 14/06/2012 03:29:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061412-21247-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF8800316BB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
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 machine check exception has occurred.
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 14/06/2012 00:57:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061412-19250-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5328A)
Bugcheck code: 0xA (0xFFFFFFFFBD8C6255, 0x2, 0x1, 0xFFFFF800030A2688)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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 which cannot be identified at this time.
On Thu 14/06/2012 00:17:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061412-38267-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5328A)
Bugcheck code: 0xA (0xFFFFFFFF85455E32, 0x2, 0x1, 0xFFFFF800030E2688)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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 which cannot be identified at this time.
On Wed 13/06/2012 22:40:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061312-22417-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.
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 12/06/2012 19:57:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061212-14523-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x9C)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F1B70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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`00000000.sys .
Google query: unknown_module_00000000`00000000.sys MACHINE_CHECK_EXCEPTION
On Mon 11/06/2012 21:39:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-14929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x1009ED2D0, 0x2, 0x1, 0xFFFFF800030E9FA3)
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 Mon 11/06/2012 01:16:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061112-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 08/06/2012 02:43:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060812-16645-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030B19A3, 0xFFFFF88009B88020, 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 06/06/2012 23:54:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-16458-01.dmp
This was probably caused by the following module: afd.sys (afd+0x538C0)
Bugcheck code: 0xC7 (0x5, 0xFFFFF8800408E8C0, 0x0, 0xFFFF)
Error: TIMER_OR_DPC_INVALID
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 06/06/2012 14:30:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060612-17643-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000022.sys (Unloaded_Unknown_Module_00000000`00000022+0x7A)
Bugcheck code: 0x9C (0x0, 0xFFFFF88002FDBB70, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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`00000022.sys .
Google query: unknown_module_00000000`00000022.sys MACHINE_CHECK_EXCEPTION
On Tue 05/06/2012 21:31:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060512-18283-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFFFFDBEE88FB, 0x2, 0x1, 0xFFFFF800030E5688)
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 Sun 03/06/2012 23:50:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060412-24523-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x5AEE)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF96000685AEE, 0xFFFFF88009383778, 0xFFFFF88009382FD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
16 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:
unknown_module_00000000`00000022.sys
unknown_module_00000000`00000000.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.
7. Check device manager please see if any warnings on any driver
I am checking now i am not too good here walking into the wilderness.
(I am posting now incomplete so i can edit it as i do them)
Edited by urgenthelp, 17 June 2012 - 05:16 PM.