ideas re crashes please!

[geoffacox]

Hello

I keep having crashes!

WhoCrashed gives me the following - any ideas please? I have removed AVG and am using Microsoft Security Eessentials.

Cheers

Geoff

[FONT=Segoe UI, Arial]On Thu 14/07/2011 00:06:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071411-46281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x2A9C7)
Bugcheck code: 0x1A (0x411, 0xFFFFFFFFC0259A48, 0x1F600860, 0x40259A49)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
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 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.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 13/07/2011 06:11:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071311-32406-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x20DF4)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFAC22B800, 0xFFFFFFFFAC22BB28, 0xA65006D)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a pool header is corrupt.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 12/07/2011 08:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071211-35890-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]avgidsshim.sys[/FONT] (AVGIDSShim+0x1970)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8295D41B, 0xFFFFFFFFAA2A6AAC, 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: avgidsshim.sys .
Google query: [FONT=Segoe UI, Arial]avgidsshim.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Sat 02/07/2011 16:21:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-34515-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x82213)
Bugcheck code: 0x1A (0x3452, 0x1881000, 0xFFFFFFFFC0406DC4, 0x4915FC66)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 01/07/2011 19:13:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070111-31843-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1FC447)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A4B447, 0xFFFFFFFFA853FC60, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.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 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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 30/06/2011 20:23:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-34781-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x225CE)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0003018, 0x2, 0x1, 0xFFFFFFFF828CB136)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/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
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21/06/2011 10:15:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062111-60078-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x225CE)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0003010, 0x2, 0x1, 0xFFFFFFFF828B1136)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/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
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 17/06/2011 09:40:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061711-27906-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x225CE)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0003018, 0x2, 0x1, 0xFFFFFFFF8289C136)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/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
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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 16/06/2011 17:40:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061611-23687-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]avgidsfilter.sys[/FONT] (AVGIDSFilter+0x20BA)
Bugcheck code: 0xA (0xFFFFFFFFC0003000, 0x2, 0x1, 0xFFFFFFFF828A0136)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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: avgidsfilter.sys .
Google query: [FONT=Segoe UI, Arial]avgidsfilter.sys IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Thu 16/06/2011 17:40:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]avgidsfilter.sys[/FONT] (AVGIDSFilter+0x20BA)
Bugcheck code: 0xA (0xFFFFFFFFC0003000, 0x2, 0x1, 0xFFFFFFFF828A0136)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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: avgidsfilter.sys .
Google query: [FONT=Segoe UI, Arial]avgidsfilter.sys IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Tue 14/06/2011 03:58:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061411-22843-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x38C9B)
Bugcheck code: 0xA (0xFFFFFFFFC0003004, 0x2, 0x1, 0xFFFFFFFF828AE136)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 11/06/2011 19:39:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-20750-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0xCA4DE)
Bugcheck code: 0x50 (0xFFFFFFFFFE6DF5A0, 0x0, 0xFFFFFFFF8296752D, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Multi-User Win32 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.
[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]12 crash dumps have been found and analyzed. 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:

[FONT=Segoe UI, Arial]avgidsfilter.sys [/FONT]

[FONT=Segoe UI, Arial]avgidsshim.sys [/FONT]
[/FONT]

 

[zigzag3143]

Hello

I keep having crashes!

WhoCrashed gives me the following - any ideas please? I have removed AVG and am using Microsoft Security Eessentials.

Cheers

Geoff

[FONT=Segoe UI, Arial]On Thu 14/07/2011 00:06:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071411-46281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x2A9C7)
Bugcheck code: 0x1A (0x411, 0xFFFFFFFFC0259A48, 0x1F600860, 0x40259A49)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
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 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.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 13/07/2011 06:11:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071311-32406-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x20DF4)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFAC22B800, 0xFFFFFFFFAC22BB28, 0xA65006D)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a pool header is corrupt.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 12/07/2011 08:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071211-35890-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]avgidsshim.sys[/FONT] (AVGIDSShim+0x1970)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8295D41B, 0xFFFFFFFFAA2A6AAC, 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: avgidsshim.sys .
Google query: [FONT=Segoe UI, Arial]avgidsshim.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Sat 02/07/2011 16:21:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070211-34515-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x82213)
Bugcheck code: 0x1A (0x3452, 0x1881000, 0xFFFFFFFFC0406DC4, 0x4915FC66)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 01/07/2011 19:13:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070111-31843-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x1FC447)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A4B447, 0xFFFFFFFFA853FC60, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.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 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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 30/06/2011 20:23:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-34781-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x225CE)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0003018, 0x2, 0x1, 0xFFFFFFFF828CB136)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/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
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 21/06/2011 10:15:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062111-60078-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x225CE)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0003010, 0x2, 0x1, 0xFFFFFFFF828B1136)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/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
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 17/06/2011 09:40:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061711-27906-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (dxgmms1+0x225CE)
Bugcheck code: 0x1000000A (0xFFFFFFFFC0003018, 0x2, 0x1, 0xFFFFFFFF8289C136)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/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
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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 16/06/2011 17:40:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061611-23687-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]avgidsfilter.sys[/FONT] (AVGIDSFilter+0x20BA)
Bugcheck code: 0xA (0xFFFFFFFFC0003000, 0x2, 0x1, 0xFFFFFFFF828A0136)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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: avgidsfilter.sys .
Google query: [FONT=Segoe UI, Arial]avgidsfilter.sys IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Thu 16/06/2011 17:40:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]avgidsfilter.sys[/FONT] (AVGIDSFilter+0x20BA)
Bugcheck code: 0xA (0xFFFFFFFFC0003000, 0x2, 0x1, 0xFFFFFFFF828A0136)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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: avgidsfilter.sys .
Google query: [FONT=Segoe UI, Arial]avgidsfilter.sys IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Tue 14/06/2011 03:58:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061411-22843-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x38C9B)
Bugcheck code: 0xA (0xFFFFFFFFC0003004, 0x2, 0x1, 0xFFFFFFFF828AE136)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 11/06/2011 19:39:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061111-20750-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0xCA4DE)
Bugcheck code: 0x50 (0xFFFFFFFFFE6DF5A0, 0x0, 0xFFFFFFFF8296752D, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Multi-User Win32 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.
[/FONT]

[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]12 crash dumps have been found and analyzed. 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:

[FONT=Segoe UI, Arial]avgidsfilter.sys [/FONT]

[FONT=Segoe UI, Arial]avgidsshim.sys [/FONT]
[/FONT]

We need the actual DMP files for analysis




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[geoffacox]

Thanks for the reply. I have attached the dmp files.

By the way - I have a Nvidia GeForce 6200 video and card and updated the driver 13/7/11.

Cheers

Geoff

 

[geoffacox]

Hello

'just crashed again - so attach the new dmp file.

WhoCrashed indicates a problem with hal.sys - but apparently this not found in Windows 7 ... a suggested approach is to use Windows 7 setup disk to overwrite the master boot record?!

Cheers

Geoff

 

[geoffacox]

Hello

I have just realised that I ought to have used the bsod dump & system file software and perfmon /report.

Apologies for not doing that sooner.

I attached the results.

Cheers

Geoff

 

[zigzag3143]

Hello

I have just realised that I ought to have used the bsod dump & system file software and perfmon /report.

Apologies for not doing that sooner.

I attached the results.

Cheers

Geoff

Memory corruption caused by an unknown driver. Please run these two tests



Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[geoffacox]

will do as you suggest and get back with the results.

Thanks

Geoff

 

[geoffacox]

well - have done the RAM testing - 6 passes and no errors - so now to the Verrifier etc.

I am actually not getting a blue screen when the PC crashes - just a black one. Guess this means nothing? I do get a mini dump file each time this happens.

If I get a crash do I send just the new dmp file?

Cheers

Geoff

 

[zigzag3143]

well - have done the RAM testing - 6 passes and no errors - so now to the Verrifier etc.

I am actually not getting a blue screen when the PC crashes - just a black one. Guess this means nothing? I do get a mini dump file each time this happens.

If I get a crash do I send just the new dmp file?

Cheers

Geoff

Yes please do. they always contain some information.

 

[geoffacox]

OK - will do ..

Cheers

Geoff

 

[geoffacox]

Hello

A further development!

I had just tried to set up a Task event (which is not working yet!) - rebooted and got the blue screen with

A problem has been detected and windows has been shut down to prevent damage to your computer.

The IO manager has detected a violation by a driver that is being verified. The faulty driver that is being verified must be debugged and replaced with a working version.

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware of software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Diable BIOS memory optiosn such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and hten select Safe Mode.

Technical information:
*** STOP: 0x000000C9, (0x0000000C, 0x80E3B4D4, 0x90048F68, 0x00000000).

After several reboots the PC booted up normally and so have attached the dmp file.

Any clues? I have not installed any new h/w.

Cheers

Geoff

 

[zigzag3143]

Hello

A further development!

I had just tried to set up a Task event (which is not working yet!) - rebooted and got the blue screen with

A problem has been detected and windows has been shut down to prevent damage to your computer.

The IO manager has detected a violation by a driver that is being verified. The faulty driver that is being verified must be debugged and replaced with a working version.

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware of software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Diable BIOS memory optiosn such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and hten select Safe Mode.

Technical information:
*** STOP: 0x000000C9, (0x0000000C, 0x80E3B4D4, 0x90048F68, 0x00000000).

After several reboots the PC booted up normally and so have attached the dmp file.

Any clues? I have not installed any new h/w.

Cheers

Geoff

Sorry Geoff

Verifier was enabled but captured no driver we need to wait for the next one. This happens sometimes when the crash occurs so quickly verifier doesnt have time to write the information to the page file.

 

[geoffacox]

shame! will get back if/when get another event.

Cheers

Geoff

 

[geoffacox]

Hello

any idea what this means?

I have just turned the PC on and I see Starting Windows and the 4 piece logo. But the logo oscillates slightly and nothing further happens. After 5 mins I reboot the PC and have the 2 options, repair and normal. I go for normal and the PC does boot up correctly.

??!!

Geoff

 

[geoffacox]

Hello

3 more dmp files - refer to USBPORT. I have uninstalled the usb ports in device manager and they were re-installed using safe mode.

Any else I should do?

Cheers

Geoff