BSOD Apps randomly crash?

coban · 30 Jan 2010

After a doing a fresh install of Windows 7 64 bit, I've been getting some programs to crash after a couple seconds. For example, after opening up Mozilla Firefox, the browser just crashes almost immediately. A few minutes later while my computer is idle, it crashes and restarts my computer. I then get this Blue Screen message upon startup:

BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002BC3000
BCP3: FFFFF88007811D60
BCP4: 0000000000000000

OS_Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

I'm unsure of what to do. I'll attach the minidump.

Thank you

ManOwar2 · 30 Jan 2010

Hi this really looks the symptoms I had on my new system for the last 3 weeks. I think I have fixed the issue by changing ram.

Since it was painfull to get throught all this, I think you might be interested in finding some informations provided by great people on this forums. Since there's been many replies to the thread, you might find some answers. Take a look at the pro giving advices to me.

https://www.sevenforums.com/crashes-d...sh-system.html

coban · 30 Jan 2010

Thanks for responding! I read through the thread you gave me and I have a feeling it could be RAM for me as well. I will have to thoroughly test my memory with memtest86+.

I have 3 sticks of 2GB G.Skill. Do I test just one at a time?

ManOwar2 · 30 Jan 2010

coban said:

Thanks for responding! I read through the thread you gave me and I have a feeling it could be RAM for me as well. I will have to thoroughly test my memory with memtest86+.

I have 3 sticks of 2GB G.Skill. Do I test just one at a time?

Well give a try with all the sticks and try to aim something between 5 and 10 passes. but with 3 sticks I think 10 pass would not be a luxe, just to have a clear mind.

Also, you may have to run memtest 2-3 times at different times.

If you have only one of your 3 modules thats is faulty, you could also give a try removing one, removing two, switichings side. Try differents combinations until you identify the ram module. I did not go that way cause I had to RMA both my modules anyway. I know it's time consumming and painful...good luck.

Of course, there is always a chance it's not the ram, but excluding this possiblity in the first place will render the debugging easier. If memtest finds errors, it usually means that your ram is faulty. The mobo could also be, but I've read and been told that this is rare and unlikely. ( I was afraid mine was, but for now (let's hope it continue) it looks like it was my ram fault.

coban · 31 Jan 2010

I just finished going through at least 5 passes for each 2Gb stick of ram. I tested them one at a time and no errors came up. I guess I could test again.

Can someone please take a look at the minidump and point me in the right direction?

usasma · 31 Jan 2010

The minidump points at pool corruption - so I'd suggest running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 30 11:24:36.175 2010 (GMT-5)
System Uptime: 0 days 0:05:12.845
BugCheck 3B, {c0000005, fffff80002bc3000, fffff88007811d60, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+174 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe

coban · 31 Jan 2010

Right before you posted, I did a fresh install of Windows 7

. Update: I tested two 2GB sticks with memtest86+ again, and about 95,000 errors came up. Is it safe to say that memory was the issue? Should I RMA at this point?

ManOwar2 · 01 Feb 2010

Considering the numbers of errors...yes. RMA. :/ When it find that much errors, it cant be anything else than the ram I think. Wait for usama reponse to be sure I guess. But if you are short to RMA. Then RMA.

usasma · 01 Feb 2010

ManOwar2 is correct - with that many errors it's either the RAM or the motherboard. Start with step 7 in this post to test the slots and the sticks: Memory Diagnostics

No sense in uploading any further BSOD's until the RAM is RMA'd
Good luck!

coban · 06 Feb 2010

Thanks guys. I already shipped the bad ram to G.Skill. Hopefully the replacements will fix the issue. Cheers