[Sandy Risher Lassman]

We recently purchased a new gaming computer for my son...updated the Radeon Graphics card immediately and installed AVG Free, then started experiencing intermittent BSoDs on a daily basis. Read on your forum about the nifty program to open and analyze the crashes, and am posting the results below. Wondering what you can recommend (short of returning it - less than a week old!) Thinking of doing a system restore, re-installing Windows 7 and/or re-installing AVG or finding another free virus program. Do you think any of those might help and, if so, which order should we try? I've researched the error messages and not found anything specifically helpful at this point.

I've used your site before for various info and programs to kill viruses, and you guys are awesome!!!

Thank you so much.

Sandy L

On Thu 12/8/2011 3:59:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120711-25911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EA8F00)
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 12/8/2011 3:59:49 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avgidsfilter.sys (AVGIDSFilter+0x34F4)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EA8F00)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\avgidsfilter.sys
product: AVG IDS
company: AVG Technologies CZ, s.r.o.
description: IDS Application Activity Monitor Filter 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.
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 (IDS Application Activity Monitor Filter Driver., AVG Technologies CZ, s.r.o. ).
Google query: avgidsfilter.sys AVG Technologies CZ, s.r.o. IRQL_NOT_LESS_OR_EQUAL




On Wed 12/7/2011 1:28:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120611-26707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EBBF00)
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 12/4/2011 9:58:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-26894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EACF00)
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 12/4/2011 8:55:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-22292-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EABF00)
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 12/4/2011 7:51:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120411-23649-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C020B9F0, 0x2, 0x1, 0xFFFFF80002EFAF00)
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.


Conclusion

6 crash dumps have been found and analyzed. A third party driver has 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:

avgidsfilter.sys (IDS Application Activity Monitor Filter Driver., AVG Technologies CZ, s.r.o. )

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Advertisements]

avgidsfilter.sys (IDS Application Activity Monitor Filter Driver., AVG Technologies CZ, s.r.o. )

Are you using AVG as your Anti Virus program?
Is it up to date?
Are you happy with it or are you willing to change it to stop the error?

[rshaffer61]

avgidsfilter.sys (IDS Application Activity Monitor Filter Driver., AVG Technologies CZ, s.r.o. )

Are you using AVG as your Anti Virus program?
Is it up to date?
Are you happy with it or are you willing to change it to stop the error?

[Sandy Risher Lassman]

Thanks for the super quick reply!!! Yes, we are using AVG as the antivirus program for my son's new computer - had it only a week, and downloaded AVG free directly from their website, should be up-to-date, plus we have automatic daily updates and scanning set. I have had minor problems with AVG in the past, but nothing like my son is experiencing with his new computer. If AVG is responsible for both errors we are receiving (also the ntoskrnl.exe crash error) we would happily switch from AVG to another antivirus program to stop the BSoD errors. If you think this is the problem, do you have any others (hopefully free!) you can recommend so we could check them out?

[rshaffer61]

I would suggest uninstalling AVG by going HERE for their Removal Tool, but not until you have another AV like MSE ready to go.
Once you have that all done then we can see if the BSOD's stop then.

Edited by rshaffer61, 08 December 2011 - 10:22 PM.
Added link for removal tool

[Sandy Risher Lassman]

We had already removed AVG via the control panel before you edited your post, but I will have my son run the removal tool program just in case. He installed MSE, only used his computer for about 30 minutes since removing AVG, no BSoDs, but too soon to tell. BTW...the computer crashed while we were uninstalling AVG!! I'll keep you posted, and thanks again so much for your help.

Sandy

[rshaffer61]

Great that MSE has resulted in no BSOD's. The removal of AVG using the program uninstall is usually not good enough and running the removal tool should get rid of everything from AVG. Please let me know after the removal tool has run and then with MSE running if there are any BSOD's or not.

[Sandy Risher Lassman]

That's what I was thinking, we needed to run the tool to get rid of everything. Hopefully, my next post will be a week from now, letting you know no more BSoD's...(fingers crossed!!!) Have a nice weekend, Sandy

[rshaffer61]

That's what I was thinking, we needed to run the tool to get rid of everything. Hopefully, my next post will be a week from now, letting you know no more BSoD's...(fingers crossed!!!) Have a nice weekend, Sandy

Sounds like a greta plan to me. I will monitor this topic for a response.

[Sandy Risher Lassman]

My son has ran the AVG tool to totally remove AVG, has been playing on his computer for over an hour and did get one BSoD...it's the same error, ntoskrnl.exe. Rats!!! The only other change we made from this was updating the driver for the video card...any suggestions where to go from here? Sandy

[rshaffer61]

That error is a OS issue.
Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.

[Sandy Risher Lassman]

Thanks...when I have some time this weekend, we'll attempt this. I'll keep you posted.

[Sandy Risher Lassman]

Hello again:

We are getting some different files now in the crashes...I did look at the link you sent us for SFC (not sure I understand how to do it, honestly), and I'm wondering if it wouldn't be easier (for us) to just re-install Windows 7 (computer came with a disk) or send this back to the mfgr since we have a great warranty and this problem is unacceptable. Haven't even had it two weeks yet.

These are the errors from today.
Sandy


System Information (local)

computer name: RANDALL-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8571392000 total
VM: 2147352576, free: 1955909632


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 12/10/2011 4:06:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120911-21684-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EA6F00)
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 Sat 12/10/2011 4:06:43 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x132C3)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EA6F00)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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 Sat 12/10/2011 3:34:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120911-19032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C5A79A18, 0x2, 0x1, 0xFFFFF80002F30711)
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 Sat 12/10/2011 1:24:41 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120911-19968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EB4F00)
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 12/9/2011 3:08:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-26598-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA80C03139F0, 0x2, 0x1, 0xFFFFF80002EAEF00)
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.

[rshaffer61]

Sending it back to the manufacturer is a option you can do but if this is truly a software or driver issue it may not be covered under your warranty.
Before deciding to do that can you please try the below.

If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate [b/memtest86+-4.20.iso[/b] file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[Sandy Risher Lassman]

You Wrote:

f you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

Regarding your NOTE section...when you refer to manual check listed above, do you mean SFC or is something not included here? Not sure what you mean by manual check Option A..

Here's where my ignorance will show...I don't know how to determine how many RAM sticks are installed, ergo I have no clue how to start one at a time.

Sorry...

I really appreciate everything you are trying to do to help us - not sure I have the knowledge base to follow thru!!!

Sandy

[rshaffer61]

Skip that part and just do the software testing. After that if needed I can instruct you on how to locate and test one module at a time. I still believe the issue is with the OS itself but I'm attempting to verify all hardware first before diving directly into the software part of everything.