Random BSODs (while playing games and ETC)

ArcisDarkfire · 09 Oct 2012

I was suffering from random BSODs a few weeks ago and have been in the process of fixing it ever since. My friends and I are running out of ideas of causes. Originally we thought it was my new graphics card (specs listed below). Thankfully it was still under warranty. We replaced it, didn't help. Our next guess was that Windows was corrupted. So we reset it to factory settings using my D: drive. Helped for a while then went back. Then we figured it to be the RAM. Originally we replaced one stick, helped for a while then BSODs started again, so we replaced all three. It's now starting again, although not as often. My most recent have been when playing the online game Forsaken World, a crash with no BSOD or DMP (just a force shut down) while playing DC Universe Online, and the most recent while running a Windows Experience Index assessment of my computer to find out it's "rating".

I have an HP Pavilion p6520y
GEForce GTX 550 Ti and I have the updated drivers. The power supply is a Thermaltake also bought from Best Buy.
I've taken out the original 3 RAM cards (Elpida 2GB 2Rx8 PC3-10600U-9-10-B0) and replaced them with 3 new ones (Don't have the full specs from the card but have the original box. Kingston HyperX blu 4GB Latency 9-9-9 DDR3 1333MHz is the only info I can find on it. I bought it at Staples).

I have the updated BIOS for my computer, all of the updated drivers as far as I know of, have run Ccleaner and no longer have any listed registry problems (when originally I had around 140), and have run out of ideas of the possible cause. I have uploaded everything I hope can help. Any help given would be amazing.

ArcisDarkfire · 09 Oct 2012

UPDATE:
I come home from running errands to find my computer had apparently crashed on me again. Not only that, but it was making a constant beeping sound. I manually restarted my computer and found that windows would not start. Included is a picture of the screen I saw when trying to boot.

Arc · 10 Oct 2012

Welcome aboard to the forums with a bad news

First let us try to make the system boot again, then we are coming to the bugcheck analysis.

Make it sure that the 100 MB hidden System Reserved partition is marked as active.
Partition - Mark as Active

Then, run Startup Repair, for three separate times, with restarts in between every single run. It will hopefully repair the BCD error.

If it failed even after three repeated trials, follow Troubleshooting Windows 7 Failure to Boot.

Is it booting normally now? let us know.

===================================================================
===================================================================

When your computer will boot again normally:

► Uninstall Avast, the direct cause of your crash, and install http://windows.microsoft.com/en-US/w...ity-essentials

Code:

fffff880`0a775818  fffff880`04809cf5Unable to load image aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
 aswSP+0x9cf5

► Update AMD AHCI Compatible RAID Controller. Another direct cause of your Crash.

Code:

fffff880`031c44d8  fffff880`018686beUnable to load image ahcix64s.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
 ahcix64s+0x2c6be

It is too old.Of Sept 2009.

Code:

lmvm ahcix64s
start             end                 module name
fffff880`0183c000 fffff880`0188b000   ahcix64s T (no symbols)           
    Loaded symbol image file: ahcix64s.sys
    Image path: ahcix64s.sys
    Image name: ahcix64s.sys
    Timestamp:        Wed Sep 23 18:22:47 2009 (4ABA1A1F)
    CheckSum:         00045C70
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from http://support.amd.com/us/psearch/Pa...ords=&items=20.

► Update your network driver:Realtek PCIe GBE Family Controller

Code:

lmvm rt64win7
start             end                 module name
fffff880`04f52000 fffff880`04fa9000   Rt64win7   (deferred)             
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Mar 04 19:12:52 2010 (4B8FB8DC)
    CheckSum:         000611C5
    ImageSize:        00057000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from http://www.realtek.com.tw/downloads/...&GetDown=false

► Free up the startup.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept the restart.

ArcisDarkfire · 10 Oct 2012

I was unable to find my drivers on the AMD site. I'm not exactly the most tech savvy and I got kinda overwhelmed with the choices and not entirely knowing what I have or what will screw over my computer and what is the real component. Rather I downloaded the original driver from the HP website for my computer brand and model.
I just got another blue screen, once again while playing Forsaken World (I've learned that it is when it happens most frequently, so it's the best way to test if what I've done has worked or not). Here is all the information. Hope to hear back! Thank you for the help so far.

Arc · 11 Oct 2012

Arcis, Can you boot into windows normally now?

Here is your crash's report:

Code:

!analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000002f4ae4, page frame number
Arg3: 0000000000000003, current page state
Arg4: 00000000002f922b, 0

But there is no trace of any driver in the stack, other than filtmgr.sys, which is a microsoft driver, and cannot be a real cause of the crashes. It may be caused by two things possible, either for a Ntfc corruption, or for an antivirus program.

For Ntfs corruption, check your storage system thoroughly.

Reseat the sata and power.
Run chkdsk /f/r, following the option two of the tutorial Disk Check
Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
If you are using SSD, update the firmware.

For Antivirus issue, Uninstall Avira, replace it with Microsoft Security Essentials - Free Antivirus for Windows.

If still it crashes after doing those two, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

ArcisDarkfire · 13 Oct 2012

I had another crash. I'm running the driver verifier now and will alert to any further crashes or blue screens. Just wanted to upload the crash dumps from these because it seemed to be a particularly nasty one. Had problems booting up my computer afterwards and was faced with several crashes in a small amount of time.

ArcisDarkfire · 13 Oct 2012

Many crashes later, here is the new info. I disabled the driver verifier. I kept crashing while booting or during login, so I had to end it in safe mode. Let me know if I should start it back up again.

Arc · 13 Oct 2012

RAM - Test with Memtest86+

Run it for at least 8 passes, preferably overnight.

ArcisDarkfire · 14 Oct 2012

Problem hopefully solved.

So I started the test, and during test # 4 it freaked out and gave a bunch of errors. Not long after it crashed. So I tested each stick individually and had no problem. While switching out sticks though, I noticed something. Slots # 1 and 2 were both blue, while # 3 and 4 were both black. 2 of my Ram sticks I bought are paired, sold together. The other isn't. When I first put them in, I had non-paired in 1, and the paired in 2 and 3. I was then informed about how paired ram usually has to be in certain slots. I was told the usual case is pairs go in 1 and 3 or 2 and 4. So I switched the non-paired to 3 and put the paired in 2 and 4. I'm thinking the colors on the slots indicate where paired ram is supposed to go. I ran the tests with the paired ram in slots 1 and 2 and the unpaired in 3 and the test passed. I'm going to try playing Forsaken World to see if it runs without problem.

ArcisDarkfire · 14 Oct 2012

Spoke too soon. Gonna run the ram test for the full 8 passes then ill upload the new crash dump in the morning.