New
#1
Random BSOD (IRQL_NOT_LESS_OR_EQUAL)
I've been getting random BSOD all the time, but it only happens every month or so, so I ignored it. But these few BSOD happened often and recently when I was gaming with Skype on. It doesn't happen when I don't have Skype on. But I don't think that's the case. I'm wondering how to fix this.
My Specs are:
Windows 7 Home Premium 64 BIT
Intel i5 2500K
4 GB PNY ram x2
EVGA 560Ti 1GB
750W Coolmaster
Recent mini dumps via WhoCrashed:
On Sun 11/4/2012 2:34:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-28922-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7D70)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800032E5468)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 that cannot be identified at this time.
On Sun 11/4/2012 12:57:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-29374-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC2 (0xB, 0xFFFFFA8008A20A40, 0x5480003, 0xFFFFFA8008A20E50)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sun 11/4/2012 12:57:16 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgidsdrivera.sys (avgidsdrivera+0x1567C)
Bugcheck code: 0xC2 (0xB, 0xFFFFFA8008A20A40, 0x5480003, 0xFFFFFA8008A20E50)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\avgidsdrivera.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Driver.
Bug check description: This indicates that the current thread is making a bad pool request.
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: avgidsdrivera.sys (IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o. ).
Google query: AVG Technologies CZ, s.r.o. BAD_POOL_CALLER
On Sun 11/4/2012 12:51:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-31839-01.dmp
This was probably caused by the following module: volsnap.sys (volsnap+0x176A2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFF8800377F8D8, 0xFFFFF8800377F130)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\volsnap.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Shadow Copy 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 that cannot be identified at this time.
On Sat 11/3/2012 8:43:33 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110312-30591-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800032D3242)
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 that cannot be identified at this time.
On Fri 11/2/2012 4:13:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110212-37502-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x4E (0x99, 0x1BD763, 0x0, 0x1BD7E3)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Any help is greatly appreciated.
Quote
Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.
► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA Reboot the system. Now delete remnants of its drivers using