Nomad of Norad

Extraordinary Member
Joined
Jan 9, 2009
Messages
209
One week ago, my machine spontaneously started misbehaving, after having no problems for more than a year and a half. I was using a MSI K9A2 Neo motherboard, AMD Phenom II X4 920 CPU, with a fairly beefy power supply and lots of ram. I am on Win7 Ultimate 64 bit. I have progressed through multiple betas, the RC, and eventually purchased the full release version. I started out using an ASUS EN6200LE PCI-E display card, but about 6 months ago replaced it with a GeForce GT240 1GB DDR3 PCI-E 2.0 display card, and it ran without a hitch for months. I switched because I spend a lot of time on places like Second Life, and someone I knew on there recommended this card. The SL viewer programs complain the card isn't good enough, but it runs great.

Well, last Wednesday, I logged into SL, and was there only a few moments when the viewer suddenly disappeared out from under me. Just, BOOM! Gone. I logged back in, was in there a few minutes, and the whole computer display suddenly went dark. I thought it was the screensaver inixplicably switching in.... but no amount of mouse waggling would bring it out. Unfortunately, the ones who put my machine together goofed up and failed to connect the drive-activity light, so I couldn't look to see if there was activity.... but after several moments of no response, I finally powered the machine off and back on.

Fairly soon I got errors at startup, before the OS had loaded, with the mobo claiming there was a failed overclock attempt. After multiple restarts, I could not get this error to go away. And no, I did not attempt any kind of adjustments to the CPU.

I also started getting more and more bluescreens, at startup, during operation, during windows repair at startup... sometimes the sort where it states it had detected a problem activity and shut the machine off to protect it.

I described the problem to an acquantance who used to teach computer repair and used to run a computer repair place. He suggested it was likely a problem with the mobo, perhaps the capacitors going bad. The next day, I bought the machine to him and... he couldn't find any sign of bad capacitors. On the other hand, he could not get it to display anything on the monitor there, and couldn't hear any POST beeps, but the machine was clearly turning on (the fans were coming on, and stuff).

Anyway, long story short, I rushed out and got a replacement mobo, there were only 2 makes on hand at CompUSA that would support the old AM2+ CPUs, so I grabbed the ASUS M2N68-AM PLUS mobo, brought it back, and we switched it out, transferred the CPU over.... and at powerup it popped up a warning that this CPU was not supported. He was like "That's nonsense, it should support all CPUs of this family or none of them. The CPU must be bad." He figured the CPU had gotten damaged enough that it was misreporting itself to the mobo. He HAD noticed that the CPU fan was all gummed up and wasn't turning very well, or at all (I'm not sure which it was), so it seemed likely the thing had overheated and croaked.

On the other hand, upon placing the new mobo in, he noticed there was NO speaker inside the machine.... so, nothing that would have produced the POST beeps. He grabbed one from another machine and installed it. Then we saw the error about the CPU not being supported, and he decided it was probably knackered. He also states that often, if the CPU is bad, it takes the mobo with it, so to be on the safe side he usually replaced both. oO

Anyway, I ordered another of the exact same CPU (AMD Phenom II X4 920, remember), but it didn't arrive until Monday. He has been out of town this week, so I haven't been able to get back to him... however, when I inserted the new CPU into the mobo, it gave the exact same this-CPU-is-not-supported message, telling me to go to their website and look up the list of supported CPUs. I finally did, and discovered that, in fact, this exact CPU was not supported.

I was trying to find out a source for another mobo that could take the place of this one and let me use all the existing componants (ram, display, CPU, etc)... but finally just said, "Oh screw it!" and grabbed a different CPU that WAS on the supported list for that mobo, because I was going totally stir crazy watching the time slip away from me without the machine to be back up and running, so I grabbed an AMD Athlon X2 7850 Black Edition Dual Core Processor AD785ZWCJ2BGH, brought it home and installed it.

First power up, it claimed failed overcloaking, even tho all I did was insert the CPU, my guess it was complaining because it saw the CPU response had changed... but I restarted it again, leting the BIOS go to default, and it didn't claim that again.

Windows then wanted to do its restore, but after multiple attempts at it, it couldn't complete it. So I reinstalled Win7, and spent the next few hours reinstalling various software packages.... got back onto SL, and onto one of the OpenSim virtual worlds I spend a lot of time on, and was on there a number of hours without technical issues. I even got an account on another OpenSim world and hung out there awhile.

I then powered down and went to bed. Before it completed shutdown, it did some Windows updates and stuff.

Today, I turned the machine back on... walked away... came back to find that Windows had locked up on startup. It was stuck at the splash screen where it shows the colored dots coming together to form the Windows 7 logo. I powered it off and back on, and it locked up again at a different point in the startup. And then at one point it bluescreened.

And now it bluescreens frequently. Sometimes during repair, sometimes when I have been logged into SL for a few moments. Sometimes just went websurfing. Sometimes the sort where it states it saw something bad happening and shut the things off to protect it.

This is driving me bananas. It is now clear there was probably nothing wrong with the previous mobo or CPU. I have attached several minidumps in a zip file. Windows has done some more updates since these earlier today, but it is still giving some problems. I really hope someone can help me here.

Addendum: have added the info from msinfo32.
 


Attachments

Last edited:
Solution
Hey there. I didn't read everything, so apologies in advance.

Here's what's needed to be done:

1) Update your Hauppage TV Tuner driver from the manufacturer's website. This is tool old for Windows 7:

emOEM64 emOEM64.sys Fri Aug 03 22:01:09 2007

Hauppauge Computer Works : Support

2) Install from my link to update this old, problematic driver:

ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005

Link Removed - Invalid URL

3) Not talking video here. Talking NVIDIA nForce chipset drivers. Change the dropdown at the link for the suitable driver package for your board to update this old driver:

nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008
nvstor nvstor.sys Wed May 20 02:45:37 2009

Link Removed - Invalid URL

4)...
Doesn't seem to be an Rt64win7.sys in C:\Windows\System32\drivers that I can see. Would it be in one of the subdirs of that? I don't see Afc.sys in there, either.

And yeah, I've not seen any bluescreens lately. Knock wood.
 


Alright then, don't worry about anything else. Sit tight, use the machine all you see fit.

If/when new crashes happen, we shall handle anything else that needs it. Good luck.
 


Okay, going to attach the newest output from msinfo32 now, for good measure.

Could it, or the minidump files, be seeing stuff from the Windows.old and Windows.old.000 and Windows.old.001 folders, even though they're no longer functionally part of the OS?
 


Attachments

Could it, or the minidump files, be seeing stuff from the Windows.old and Windows.old.000 and Windows.old.001 folders, even though they're no longer functionally part of the OS?

No. You should copy anything out of those folders that you want to keep. Then use the built-in disk cleanup utility in Windows to get rid of those folders. You'll have to check the appropriate box to do so, while using. I think it will be called Previous Windows Installations.

Type disk cleanup in the start menu then press enter.

Link Removed
 


Last edited:
On the other hand, is there any way to revert back to one of the Windows.old folders? Say, if I went back to the old mobo and the old CPU?
 


If you did that, then a clean install of Windows while formatting, is as high of a recommendation that I could possibly ever make.

Still crash free now?
 


Well, everything continued working fine for the rest of the session, I also restarted once or twice to be sure everything was fine. After that I went into one of the VR worlds for awhile... then powered down and went to bed.

Today, I turn the machine on, it starts loading Windows, gets as far as the Starting Windows splash screen, where the colored dots coalesce into the Windows logo... and it hangs (if it helps, it's at the point when there's three little dots set diagonally). And all disk activity stops. What could this mean?

(Turns machine back off, restarts it...)

It recommended Startup Repair, so I let it do that. Seems to be taking awhile.

Okay, after maybe 15 minutes of that, it came back with the recommendation that if I'd added some new device to the computer, please uninstall it and start it again. Should I have let it go back to a previous storage point? Last time I did that, several programs I'd just installed all magically vanished... and I wasn't wanting to go through THAT again.

BTW, this hang-at-startup thing is exactly what it did at this time yesterday.

(Lets machine shut off, starts it again...)

Hmmm, this time it started okay... Will simply leave it running for a little while without doing anything to see if it gets goofy.
 


Can you boot in safe mode and attach the fresh crash dumps (if any)?

From the startup repair options :

- Startup repair
- Memory diagnostic
- Command prompt -> chkdsk /r
- Command prompt -> sgc /scannow


Link Removed
 


Went to boot into safe mode... and it bluescreened. Several times. Both in Safe Mode with Network, and Safe Mode without. (Didn't try it with text-only mode.) Even bluescreened just letting it boot into regular Windows. I let it attempt recovery twice, and it bluescreened on returning from those. One of those recovery attempts, it complained about not being able to access a spot in memory (in ram? on the drive?), or something of the sort. That time it was when I'd decided to let it go to a recovery point. Next time on sending it to recovery, I said no on it going to a recovery point.

I will let it stay off a short while to see if letting it cool helps.

addendum: Dang, no matter what I do, it bluescreens at startup... so I can't get in and retrieve the new minidumps.

Why is it that the machine either seems to work fine for hours, even through multiple reboots, one day, and then bluescreens like nobody's business the next day?
 


Last edited:
Okay, finally got it to boot. Attaching the new minidumps.

addendum. Okay, burned a CD of that memtest thingy and am running it now. How long should I keep it running at a minimum?

addendum2: Okay, at about pass 48% I'm now getting Failing Address stuff in red. A bunch of Tst 7 (Test 7?), Count 32.
 


Attachments

Last edited:
So, I take it this means I need to replace my ram sticks? Or maybe only one of my ram sticks? If only one, which one?

I'm assuming this isn't checking the memory of my display card. Ergo, I'm not having to determine if the bad ram is in the display card instead of the mobo, right?

Should I post a picture of the Nemtest86 display?
 


Okay, I've had memtest86+ running for more than 5 hours now... it produced one little flurry of 32 "Failing Address" errors fairly early on, and none since.

So, what is the next step?
 


If errors were shown, replace the memory. You can test the sticks one at a time to find which may be the defective one or simply replace all the memory.

You really should update this driver though, from my link:

ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005

Link Removed - Invalid URL

--------

And update your nForce chipset drivers from NVIDIA for your motherboard:

nvmf6264 nvmf6264.sys Thu Jul 30 19:48:18 2009

Link Removed - Invalid URL
 


Is this the same MB_WIN7_ATK.ZIP you linked me to earlier? The URL has a slightly different string of numbers in it.

I still don't know how to install it because I don't know which device it goes to, and so can't go to that device and select to update drivers. Do you know what device, or what sort of device, it likely goes to?

Or do I just copy the files in ...\MB_WIN7_ATK\MB WIN7 ATK\64\WIN7 into a particular folder in my system like was done with some of those others?

As for the NVIDIA chipset stuff... I thought I'd already done that earlier...
 


Last edited:
Yes, it is for the ATK0110.

Easiest way to update it is to extract the download to a folder. Copy the ASACPI.sys file from the 64 bit Windows 7 folder and paste it over the one at C:\Windows\System32\drivers

Reboot.
 


Went to copy it over the original... instant BSOD. minidump attached.

Looks like the old one remained in place. :-L
 


Attachments

Yep, old still there. The crash is from faulty memory though.

You can replace the file in safe mode using the above technique.
 


Got another bluescreen when trying to open another tab from this forum on Firefox. minidump attached.

BTW, am I supposed to dload the video card drivers from that nvidia link, or something else. I.e. do I insert GeForce, GeForce 200 Series, GeForce GT 240, Win7 64 into the radio boxes?
 


Attachments

I didn't say anything about video drivers. nForce chipset drivers, instead.

It's the faulty memory causing crashes, though.
 


Back
Top