Solved Random BSODs (while playing games and ETC)

ArcisDarkfire · Oct 9, 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 · Oct 9, 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 · Oct 10, 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.
http://www.sevenforums.com/tutorials/71432-partition-mark-active.html

Then, run http://www.sevenforums.com/tutorials/681-startup-repair.html, 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 http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html.

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/windows/products/security-essentials

Code:

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

► 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
*** [COLOR=Red]WARNING: Unable to verify timestamp for ahcix64s.sys
*** ERROR: Module load completed but symbols could not be loaded for ahcix64s.sys
 ahcix64s+0x2c6be[/COLOR]

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
    [COLOR=Red]Image name: ahcix64s.sys
    Timestamp:        Wed Sep 23 18:22:47 2009[/COLOR] (4ABA1A1F)
    CheckSum:         00045C70
    ImageSize:        0004F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from http://support.amd.com/us/psearch/P...entType=KB+Article&ostype=&keywords=&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
    [COLOR=Red]Image name: Rt64win7.sys
    Timestamp:        Thu Mar 04 19:12:52 201[/COLOR]0 (4B8FB8DC)
    CheckSum:         000611C5
    ImageSize:        00057000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&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 · Oct 10, 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 · Oct 11, 2012

Arcis, Can you boot into windows normally now?

Here is your crash's report:

Code:

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

[COLOR=Red][B]PFN_LIST_CORRUPT (4e)[/B][/COLOR]
[COLOR=Red]Typically caused by drivers passing bad memory descriptor lists[/COLOR] (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 · Oct 13, 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 · Oct 13, 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 · Oct 14, 2012

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run it for at least 8 passes, preferably overnight.

ArcisDarkfire · Oct 14, 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 · Oct 14, 2012

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

ArcisDarkfire · Oct 15, 2012

Most recent dump

Arc · Oct 15, 2012

May be we are missing something here?
View attachment 236773

How the memtest went? According to your first post about memtest, you need to replace RAM modules, I think? As long as the failing memory is in use, the system cannot run stable.

ArcisDarkfire · Oct 15, 2012

Weird... It must not have created a dump file.
So here is the breakdown of EVERYTHING that happened with the Ram. Originally we thought it was the cause of the problem. My computer had the original ram in slots 2, 3, and 4. We removed the ram from slot 2 and replaced it with a new one. When we still had problems we removed the other 2 original ram, leaving only the new stick (4GB) and put it in slot 1. After being used to 6GB of ram, it was killing me running on 4, so I went back and bought 2 new sticks of the same model. They were in a package together though and both have K2 on them. I was told these are linked. I kept the first new stick in 1 and put the other two in 2 and 3. After it crashed I was informed that linked ram sticks have to be put in certain slots in order to work. I switched it so it was in 2 and 4 and the unlinked was in 3. After that you recommended to test my ram. It failed the test and crashed. So I tested each stick individually and had no problem. So instead I tried testing having the linked sticks in 1 and 2 and the unlinked in 3. It passed the test. I tried playing a game, and it crashed (bsod but didn't seem like it created a dump file. That is what I tried to upload). I decided to run the test again, and this time it came up with over 3 million errors, and it was still going up. I rebooted my computer and restarted the test and let it run overnight. It passed every single time, no problem and no errors. I'll try to collect the dumps again and see if maybe it just didn't find it for some reason. I know I just got one earlier today while DC Universe Online was updating.

ArcisDarkfire · Oct 15, 2012

Yeah, it didn't seem to create a dump file from when it crashed when I thought everything was fixed. Seemed like my computer froze up on the BSOD, so that might be why. I have the newest BSOD dump thought from today.

Arc · Oct 15, 2012

Have you changed the memory already?

ArcisDarkfire · Oct 15, 2012

I haven't changed it since I thought it was fixed, with the 2 paired ram in 1 and 2 and the unpaired in 3. I'd look up my motherboard manual to find out exactly how I have to place paired ram, but from what I've seen, foxconn no longer supports it.

Arc · Oct 16, 2012

Arcis mate, as you havent changed the faulty memory mosules yet, no debugging can make it stable.

I,d suggest you to consult a technician who will do it for you. ok?

dont worry, if there are problems even after that change, that will be easy to solve.

so go for it?

ArcisDarkfire · Oct 16, 2012

All of the ram in my computer is new. All bought just before posting on here in a period of a couple days.

Arc · Oct 16, 2012

Are those newer than this post?

ArcisDarkfire · Oct 16, 2012

No. I changed out all 3 sticks just before starting this thread. The most I've done with the ram is move around the new 3 sticks. I'm hoping they aren't corrupt and that placement is just the problem. I can't find the full specs of my motherboard though, so I don't know what to do.

Solved Random BSODs (while playing games and ETC)

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer