3 Different BSODs

[Scorpion1031]

Hello all,

I am getting three different BSODs fairly regularly. The ones I am getting are:

MEMORY MANAGEMENT
IRQL_NOT_LESS_THAN_OR_EQUAL
PFN_LIST_CORRUPT

I think I have traced the cause to the Radeon HD5850 drivers that I am running, but I am not 100% sure and I may be (read: probably) wrong.

At first I checked the RAM with Memtest86: 8 loops 0 errors

So I figured it was the ATI CCC so I installed the drivers only and it ran fine for a day. Now today I am getting a ton of BSODs.

Here is my most recent dump showing 2 different error codes.

Please help. Thanks.

 

[ttran]

I'm thinking that AVG is causing your BSODs. All of your drivers looks up to date. One of the minidump pointed to memorry corruption, however, as you mentioned, u already did memtest.
In looking through your drivers, I see that you have AVG anti virus installed. AVG is known to cause BSOD, on some systems. I suggest that you uninstall it while trouble shooting using the uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also >Info > Tool[FONT=&quot]. I recommend that you install MSE and make sure Windows Firewall is turned on.

BugCheck A, {fffff68000154bd0, 0, 0, fffff800028d0ae2}

Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

Followup: MachineOwner
---------
PROCESS_NAME:  [COLOR=Red]avgwdsvc.exe[/COLOR]
BugCheck 1A, {41201, fffff683ff7ecae8, baf0000025da1025, fffffa8006067e30}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )

Followup: MachineOwner
---------
BugCheck 4E, {99, 3fd2b, 0, 3fe2b}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

~Tuan

[/FONT]

 

[Scorpion1031]

It took me 2 tries to uninstall it, both times it BSOD'd, but it looks like it is finally gone. Is there a way that I can confirm it is actually gone and not just deleted from the register of installed programs?

Also here is the minidump from the 2 BSODs while uninstalling.

EDIT: Also is there any virus scanner you can recommend?

 

[ttran]

One minidump file is corrupted, the other one still show the appearance of avg (Did u use the tool I provided), but I believe that you removed it. Have you experienced any BSODs since you uninstalled AVG??

avgtdia  avgtdia.sys  Wed Apr 14 04:12:20 2010 (4BC4DE34)

~Tuan

 

[Scorpion1031]

No I didn't use the tool you referenced. I thought that was adsense and decided not to mouse over it. I will use that as soon as I get home and let you know the results.


thanks for your help.

 

[Scorpion1031]

Used the tool you pointed to, it ran successfully and I restarted just for good measure. About 5 minutes in I get a BSOD when trying to run Internet Explorer.

I checked my Device Manager and it looks like my USB Controller is yellow flagged.


Here is my minidump.

 

[zigzag3143]

Used the tool you pointed to, it ran successfully and I restarted just for good measure. About 5 minutes in I get a BSOD when trying to run Internet Explorer.

I checked my Device Manager and it looks like my USB Controller is yellow flagged.


Here is my minidump.

While the USb controller may need a driver this crash was caused by memory corruption.

If you have not yet run memtestx86 not the built in Win 7 memory test you should. Download it, burn it to cd, and run it for at least 6 passes.

If you need help with that let us know

Ken

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 04:51:29.511 2010 (GMT-4)
System Uptime: 0 days 1:06:47.822
BugCheck A, {fffffa967486cde8, 2, 0, fffff80002915095}
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe

 

[Scorpion1031]

I actually dual boot with Ubuntu and Ubuntu installs Memtest86 that can be booted to from Grub.

I ran that 8 loops with no errors.

 

[Scorpion1031]

Do you think I should scrap x64 and pick up x86 instead? It seems a lot of people are having the same problem I have.

Also, I jumped on Win7 to get more BSODs and got another one pointing at win32k.sys.

 

[Scorpion1031]

Another set of dumps from the latest BSODs.

I am going to be running another round of Memtest86 tonight, just in case.

 

[ttran]

Hi Scorpion
I don't think the memtest86 that u use are the same as the memtest86 that we suggested you to burn to CD. I would suggest you again to burn memtestx86 to CD and let it run for at least 7 passess. The minidump you just posted still point to memorry corruption.
Memory Diagnostics

BugCheck A, {fffff680001b9ce8, 0, 0, fffff8000289b957}

Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )

Followup: MachineOwner
---------

Good Day,

Just 1 question, how can i make a new post? Im a newbie here, thanks

Crashes and Debugging - Windows 7 Forums --> click the orange box "New thread" at the top left coner of the forum

Regard
Tuan

 

[Scorpion1031]

Yea I started to get that sneaky suspicion as well. I really didn't want to have to return this RAM.

I just DL'd and burnt the Memtest86 you suggested and will be running it tonight.

 

[Scorpion1031]

So I try to run the Memtest86 with both sticks in and it crashes, just reboots after about 30 seconds.

Running each stick separately and so far the first one seems to be passing, will be running the next one soon.

Anyone know a reason it would crash like this?

 

[ttran]

Did you run each stick on different slots, slots on motherboard can be bad. If you run the stick on every slot with no error-->the slot is ok, then next time you just have to test the other stick on random slots

Tuan

 

[Scorpion1031]

I am currently running the second one, after 7 loops the first one passed in original slot. I am currently running the second one in a different slot and it looks like it is passing as well.

 

[ttran]

Do you overclocking anything?
As I mentioned, the slots can be bad too. You should run one stick on different slot to check if all the slots are working properly

~Tuan

 

[Scorpion1031]

Nope no overclocking, but I am reading on some other forums that the board may actually be having problems detecting Auto settings for the RAM. So I am going to finish testing all of the slots and then fiddle with the BIOS a bit.

 

[Scorpion1031]

So I think I found the solution. On another board I found this:
AMD Processors Forums - Phenom 2 x4 955 + Gigabyte 890GPA-UD3H

It turns out the BIOS for my mobo is sh1t. I have changed the settings in the BIOS to set C1E to Enabled instead of Auto. This seems to solve the problem now. I will update tomorrow night when I really push things and try to hit a BSOD.

I also set the RAM timing manually, I don't know if this helps, but I did it anyway.

Thanks for your help ttran, I will keep you posted so you can help other ppl with this problem if our solution works.

 

[ttran]

Thanks buddy, that's why I asked u before if u changed any settings
Good luck

 

[Scorpion1031]

I'll give you some more rep as I get more active in these forums. You have been fantastic and with someone with my need to fix things promptly (read: immediate gratification and lack of patience) you really hang in there and gave great solutions.

Even though I am a Linux guy I really am starting to like Windows again (first time in, well a long time) and really want to learn more about diagnosing the BSODs, which I had no idea they actually gave any useful information.

Lastly, any good suggestions on how to start learning about diagnosing these problems? Also how do you read those dump files?