Something that I always try first, [almost] regardless of the actual computer's failure symptoms, is a known-good power supply.

A power supply that is putting out incorrect voltages, or that has a lot of AC noise on the DC outputs, can appear as almost any problem under the sun. Even a brand-new power supply, from a reputable manufacturer, can be bad.

Power supplies today are so inexpensive, that I always have a selection of various sizes on-hand at all times (it helps that I am an OEM of custom-built computers).

Something else, that often fixes 'unstable' machines, is to [when the power is off and the computer's case is open] basically un-plug (disconnect) and re-plug (connect) all connectors, RAM (DIMM) modules, the CPU chip, etc. You should be sure to do this (un-plug and re-plug) on every connector that you can see, inside your computer.

It is surprising, how many 'weird' problems can be traced to a simple 'the connector was not fully plugged in' type of problem.

Art

 

Something that I always try first, [almost] regardless of the actual computer's failure symptoms, is a known-good power supply.

Beyond my Video Card, that was my second thought. I am investing in a power supply tester (this or this one) and I'll be checking the results. Do you think these could tell if there's strangeness on the line, or do most power supply testers just check the volts?

 

--> Blue Screen of Death (BSOD) Posting Instructions

jcgriff2

.

 

Thanks.

Here you go. RAR archive. Hope you don't mind.

Edit: I've wanted to do this kernel dump viewing stuff for a while, but everytime I try to in Windbg it says that my "Symbol search path is: *** Invalid ***"

What is the correct search path, and how do I set that up? The Microsoft Support site on the situation doesn't detail it for Windows 7.

 

Just got back from update/restart.

SIGNIFICANT speed improvements. It's like I just bought it all over again!

I love you this much. I'll come back in a week for a full debriefing.

 

Hi -

It is actually a good thing that you included all 50 dump files as the ATK0110 Asus AI Suite (you had it correct) driver was only mentioned in a few of the earliest dumps.

Apologies it took 48 hours to get them done. Hopefully asacpi.sys is the root cause of the corruption and the driver update ends the BSOD epidemic for you.

Last item - run the System File Checker/ repair utility - SFC -
START | type cmd.exe into the start search box | right-click on cmd.exe | select run as Administrator | type/ paste the following:

[font=lucida console]sfc /scannow[/font]

Upon completion re-boot to allow files in use to be repaired.

SFC general info - http://support.microsoft.com/kb/936212
SFC & the CBS log - http://support.microsoft.com/kb/928228

So, will the debriefing be done by CIA, NSA or other?

Regards. . .

jcgriff2

.

 

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

The debriefing will be done by me, right now. Couple days early, but what can I say? I don't like to make people wait!

So Windows is supposedly okay.

Did a MemTest86+ test with both RAM chips in; no problems. I'll do another one with them singular later.

With these memory errors and resulting logs, would we be able to approximate to what device this memory is being held at? Like video RAM, actual RAM, etc.

4 more crashes. Two of which were caused by something unrelated. So, two more crash logs.

Also, I'm installing the full complete AISuite now. We'll see what this does.

EDIT: I've noticed for a while now a lot of stuff under "Conflicts/Sharing" in System Information. Now, this train of thought might be 12 years old, but aren't Conflicts/Sharing bad things? Shouldn't I be playing with IRQ's and resources to stop these sharings?