3 Different BSODs

[ttran]

Thank you for the rep, I truly appreciated it. If my advise can fix your issue, It will be my best award. I was like you, I got BSODs, I came to this forum, I got help, I like people here....and I started to learn how to analyze how to read the minidumps (no school or anything..Im pre-med major).
here is the link that you can find out how to start analyze BSODs, written by great expert Usasma (Basically you need to have WinDbg)
WinDbg Analysis Report

~Tuan

 

[Scorpion1031]

So I went through a full day of pushing my computer. Playing graphics intensive games, running resource intensive programs, and basically trying to make Win7 BSOD. All of yesterday I got nothing. So I thought, "Sweet no more BSODs". Then today, BAM! I get 3 of em.


Here is the dump.

 

[zigzag3143]

So I went through a full day of pushing my computer. Playing graphics intensive games, running resource intensive programs, and basically trying to make Win7 BSOD. All of yesterday I got nothing. So I thought, "Sweet no more BSODs". Then today, BAM! I get 3 of em.


Here is the dump.

These were similar in cause. They were caused by pool corruption (memory). In order to test it, download a 3rd party app called memtestx86, burn it to cd, and run it for at least 6 passes.

Let us know the results

Ken

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  1 17:08:23.127 2010 (GMT-4)
System Uptime: 0 days 0:13:09.454
BugCheck 19, {3, fffff900c1d810a0, 48e0000048d, fffff900c1d810a0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+c55 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  firefox.exe

 

[Scorpion1031]

Ken,

Are you a robot? No offense but you posted the same message on page 1 of this thread. And if you look at page 2 you will see I did a ton of testing on Memtest 86. Different slots, different BIOS settings.

I am rerunning it and I may just RMA these RAM sticks just to be on the safe side.

Maybe you could tell me. If I run each stick separately they are 100% fine after 8 passes each, but if I run them together Memtest86 reboots my computer.

 

[zigzag3143]

Ken,

Are you a robot? No offense but you posted the same message on page 1 of this thread. And if you look at page 2 you will see I did a ton of testing on Memtest 86. Different slots, different BIOS settings.

I am rerunning it and I may just RMA these RAM sticks just to be on the safe side.

Yep robot kitty cats do my work. The DMP files point where they point. You might also want to run memtest a single stick of ram at a time, and a single mobo slot at a time

I would also run a system file check to verify and repair win 7 system files
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results

Ken

 

[Scorpion1031]

LOL nice post, I just looked at your stats and you are probably too busy to look through all of your subscribed threads before posting.

I edited my post above:

Maybe you could tell me. If I run each stick separately they are 100% fine after 8 passes each, but if I run them together Memtest86 reboots my computer.

Do you have any idea why this could be happening?

 

[Scorpion1031]

I would also run a system file check to verify and repair win 7 system files
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results

Ken

Windows Resource Protection did not find any integrity violations.

 

[ttran]

Maybe you could tell me. If I run each stick separately they are 100% fine after 8 passes each, but if I run them together Memtest86 reboots my computer.

Sorry my friend, I just woke up. Here is the deal, if you run all of the sticks together and got error or got reboot, it's possible that compatibility issue is related. I'm not a hardware guy, I would leave this to great hardware experts here, who you can ask for help in more detail

Regard
Tuan

 

[zigzag3143]

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.

I am still not convinced the memtest in Ubuntu (and the fact it is being run from within an OS) is the same as booting from a cd with that version


The DMP was definitive

 

[Scorpion1031]

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

Its not run from within an OS, its booted to from GRUB. However, I did download the MemTest86 and boot to it from CD and if I run both sticks, memtest crashes, if I run each singly, no matter the memory slot, they run fine after 8+ loops.

So I updated to the most current BIOS and it seemed to work yesterday, but today I am getting crazy BSODs. I am starting to think it has to do with one of the Windows updates that was installed last night. I have rolled back a few times and each time it seems to work for a while then BSOD out of nowhere.

Here are some more dumps to look at.

 

[ttran]

STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x0000001A: MEMORY_MANAGEMENT http://www.carrona.org/bsodindx.html#top

Usual causes: Device driver, memory, kernel

You said that if you run memtestx86 with 2 ram together-->error, but run individual (no matter which slots)-->no error?, if that is the case, I guess this is compatibility issue with the 2 sticks of Ram

BugCheck 4E, {99, 8fd8b, 2, 8f18a}

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

Followup: MachineOwner
---------
BugCheck 50, {fffff680005fdc08, 0, fffff80002899957, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )

Followup: MachineOwner
---------
BugCheck 1A, {41282, fffffa8006572ec8, 3ffe0015, 1a}

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

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

 

[Scorpion1031]

I am thinking it is a compatibility thing with my motherboard and ram. I am going to trudge around the G. Skill forums to see if there is anything I can do.

 

[zigzag3143]

We keep analyzing and keep saying memory. Time after time the DMP's point to memory. Nothing more needs to be said.

Ken

 

[Scorpion1031]

Yes I know, we have narrowed it down to memory, but I run Memtest on each stick regardless of the mem slot in the mobo and it will run all night just fine, 0 errors, 8+ loops, but with both plugged in it resets memtest, so upon doing further research I think it is a compatibility issue between the mobo and the RAM.

I am going to do a bit of research and I will report back as soon as something comes up.

 

[Scorpion1031]

Ok so I have results.

So after I left on my own research adventure I went over to the G. Skill forum and did some reading over there. The G. Skill people said I should RMA the memory because of the Memtest86 results. Well I did some research into the current version of Memtest86 (3.5) and it explicitly says that it does not support 4 or more GB of RAM, so if you are testing on it with more than 4GB it could error and reset (which is what it was doing to me). So I ran v3.4 and it ran fine with both sticks.

After that I did a little bit more research and found that my mobo doesn't like to run G.Skill RAM dual channel with 2 sticks. So I decided to try to put them on the same channel (either slots 1&3 or 2&4 on my board). I did that, went into the BIOS, set the BIOS to "Load Optimal Defaults" and it has been running without a BSOD for 3 days.

I was thinking that I would get performance problems by running the 2 sticks on one channel, but I haven't noticed anything yet. Talking to the G.Skill Tech team they said that the only performance dip you will see is if you are running the RAM overclocked, even then it is almost negligible.

I will report back if there are any problems I come across, but so far things are looking good.

 

[ttran]

wow..that sounds like an adventure. I'm happy to hear that you haven't got BSOD so far with your try. I don't have much knowledge with hardware stuff so anything you said was very interesting.

Good Luck

Tuan