having problems with my son's system

dogwalker

n00b
Joined
Aug 20, 2010
Messages
11
I have two systems based on the GA-P35-DS3L. Mine has a quad core, and my son's has the E6500 cpu. We have Windows 7 x64 Professional on both.

My son's computer is now acting up badly, and I'm concerned about the hardware. The main two symptoms are on the CMOS Setup screen.
(1) if I leave the CPU Host Clock Control on disabled, the CPU Frequency is now incorrect. It shows "700 MHz (100x7)" whereas it used to correctly show "1.87 GHz (266x7)"
(2) the CPU Host Frequency is shown as 100, which is wrong.
and the boot screen shows a FSB of 533, which is correct.

The other major problem is that some Windows files (manifest files, it appears) have been corrupted, preventing me from doing three of the most recent Windows updates.

Now, if I overclock it, which worked great for a while (see below), the speed in Windows doesn't reflect the OC, and Prime95 fails immediately. I don't care whether I can OC it so much as just giving him a stable system.

For background, his computer ran great for a while, then a friend suggested I overclock it. We did (just changed the FSB to 400 and fixed the multiplier to keep the memory at 800), and it ran flawlessly for months.

Then my son decided to do a science project on overclocking for school, so we ran benchmarks and then restored the defaults and ran the benchmarks again, and then re-overclocked it. I think I left the PCI-E speed on "Auto" - can't remember whether I forced it to 100 or Auto.

I set System Voltage Control to manual, but left all the settings in place, at my friend's suggestion, since it had been stable. I've also tried setting it to Auto. I didn't change the DDR2 voltage in the past or now.

I'm concerned that the CPU might be damaged, because of that "100x7" reading in BIOS, and the fact that I cannot overclock at all now. Frankly, I just want to get it running reliably. Yeah, I'd love to OC it again, but my son just wants to be able to play his games.

I tried resetting CMOS (jumpered the CMOS pins, also removed the battery for one minute), no change.

IF I can get the BIOS correct, I figure I'll next do a Repair Installation of Windows 7. Anyone have any other advice?

Thanks!
 
Ok, I've done that now.

Funny thing is, even if the bios shows the 700 MHz, CPUZ still shows it as 1.87GHz once I'm in windows. On the other hand, if I try to set the FSB to 400, as before, the BIOS boot shows the memory running at 534, and CPUZ shows the cpu as 1.87. So, apparently, whatever's happened now prevents me from overclocking this system at all. That's ok, though, it's still fast enough for him.

I just hope nothing's damaged, and I guess time will tell.

Next I'll try the Repair install of Windows 7.
 
Well, I spoke too soon. I just booted into Windows and clicked on Computer Properties, and was greeted by a blue screen. The main thing I noticed on the blue screen had to do with "MEMORY_MANAGEMENT." I notice that "Performance Enhance" is set to "Turbo" so I lowered that to "Standard."

This particular ram never caused a problem before, if it's the ram. I could try other ram in there, I guess.

Or could the "MEMORY_MANAGEMENT" blue screen still result from corrupt Windows files, rather than hardware?
 
crap - sorry to spam, but Prime95 just failed too. Sheesh. :-/

The ram is 2 sticks of Crucial 6400.
 
Last edited:
Turn it off.
Unplug the PSU from the wall or flip the PSU switch.
Take out the battery and wait ten minutes.
Reverse, and put everything back the way you had it....ie psu and battery.

Now, your BIOS will be at default, you'll need to update the date and time on the standard BIOS screen.
You may need to change your VDimm to what your memory requires.
Leave everything else alone, except USB keyboard and those typrs of BIOS adjustments.

F10>enter(= OK or accept)

The computer should boot into total stock settings and you can then do what-ever you want as far as OC is concerned.....but never just pick a random FSB and hope it's OK.....you need to OC in increments of 15-20 MHz on the FSB at a time running Orthos or Prime after each adjustment....adjusting voltages as need be as well as memory ratio.

Read BillParrish's GA-965P-DS3 thread, it is one of the most simple and comprehensive OC guides ever seen, it will help alot. Oh yeah....Once stable virus and malware scan the OS, this is afterall a kid's computer....trust me I live it every day.
 
Magoo, thanks! My BIOS settings are now finally correct! I had removed the CMOS battery before, but didn't think to unplug the psu or to keep the battery out so long.

Unfortunately, Prime95 fails immediately. I didn't overclock anything.

HPET is set to 32-bit mode, but the mobo manual says to change that, so I did. Would that affect Prime95?

Would you now try to repair Windows 7, hoping that would fix the Prime95 problem? I'd think there's a problem with the ram, but I'm still a novice with hardware.

The ram is supposed to run at 1.8v. Here are the voltages in the BIOS Health screen:
Vcore: 1.298 (should be higher, I thought)
DDR: 1.856
+3.3: 3.23
+12v: 11.858
 
HPET stands for High Precision Event Timers. If you have a 64 bit operating system running but 32bit HPET, then it could cause issues. Some people just disable this and let the RTC (real time clock) handle the events.

If Prime is failing, it could be the CPU, but it could also be memory. You can use the windows memory diagnostic tool to test it, or Memtest86+. What are the temps of the cores running idle in Windows? HWMonitor will tell us what we need to know. Also, are all the clocks displayed properly in CPUZ? What about memory timings? I know that some manufacturers have the SPD set higher than the RAM is capable of running, my 7-7-7-20's SPD is 9-9-9-30, and I had to manually set it correctly.

I also just looked it up, the vcore should be 1.3625 for the E6500. Low voltage could also be the culprit of instability.
 
Oops, I mistyped above. I have the E6300, not E6500, but even there, the voltage is supposed to be 1.325, I think?

I'm running Prime95 with small-fft, and no problems. But if I run it blend, it fails immediately on one of the workers. I'll manually bump the vcore and see if that helps. Thank goodness I have my computer! My son's biting at the bit, though, on his. I had to chase him out of the room with "I don't know when it'll be fixed, but I think I'm making progress."

Oh, to answer your question, I ran CoreTemp, and it shows the temps at 48/48 for the cores while running Prime95. It also shows VID at 1.325. Can't run CPUZ now, strangely, nor launch IE8. I'll try your suggestions.
 
Last edited:
I decided to swap the ram between his computer and my other son's (we have four computers in our game room), and lo and behold, no problems. I ran Prime95 on the other son's computer (which now has the ram in question), and sure enough, it fails immediately.

If I can get by with simply buying new ram, I'm a happy camper! And I could even try running the ram at 533 and/or bumping up its voltage to 1.9 or 2.0, but that's not a big deal, if everything else is ok.

However, I still have the problem of some corrupt files on my first son's computer, most likely from the problem ram.

I think my only option, if I don't want to do a complete reinstall, is to do a Repair Install of Windows 7, would you agree? I could try to do a System Restore back maybe a month (we were gone to Philmont for two of those weeks), too.

What do you think? Repair installation? If I do that, I'll need to install the video drivers, but I don't think I have to install any motherboard drivers when installing Windows 7, it's been a while.
 
can you restore to a previous date?

System and Security\Action Center\Restore Computer to Earlier Time
 
You could just do a clean install, but that would kill any files.

here's what I'd do.....order a new set of RAM, that seems to be the problem. Don't mess with any other BIOS options until you get new RAM. The CPU will be fine at whatever VCore the BIOS decides to give it right now.

You could try to RMA the RAM but in the sake of time I'd buy a new set and get the box up and running.

Once you do that you COULD transfer essential files to an external drive and then install W7 fresh rather than do a repair.
 
Maybe you should run MEMTEST on the working system before doing anything with the RAM. Sounds like it's the board more than anything else.
 
Maybe you should run MEMTEST on the working system before doing anything with the RAM. Sounds like it's the board more than anything else.

Huh??:eek:

I decided to swap the ram between his computer and my other son's (we have four computers in our game room), and lo and behold, no problems. I ran Prime95 on the other son's computer (which now has the ram in question), and sure enough, it fails immediately.
 
I ran the Windows 7 memory diagnostic on both sets of ram, and no problems showed up. However, the same ram, used in two machines, causes Prime95 to fail, so I have to assume it's the ram.

Right now, the machine is tied up with a repair installation of Windows 7 (crossing fingers!), but I'm going to try running Prime95 on both machines again to ensure the results are repeatable, and then swap ram back temporarily to test again.

If Prime95 fails only on whichever machine has those two sticks of ram, I have to think it's the ram, don't you? Nothing else makes sense. I was concerned it might be the processor, but given the results so far, I have to lean toward the ram.

Thanks, I'll run memtest just to be sure.
 
Thanks, everyone who responded. His computer seems good to go, although I'll now do lots of tests. I need to do something about the ram - I'm not about to leave it in my other son's computer now.

But that can wait. I'll let this son test his computer extensively tomorrow.

Thanks again, have a great night!
 
Maybe you should run MEMTEST on the working system before doing anything with the RAM. Sounds like it's the board more than anything else.

And this is why you're labeled a noob. There were no indications to it being the board, and the suggestion was placed before about it being RAM, the OP also confirmed it by testing with known-good. Thank you for your contributions, but I think that the situation is under control.
 
Thanks, everyone who responded. His computer seems good to go, although I'll now do lots of tests. I need to do something about the ram - I'm not about to leave it in my other son's computer now.

But that can wait. I'll let this son test his computer extensively tomorrow.

Thanks again, have a great night!

Maybe test the sticks individually to see if it's a single stick or a pair of sticks? If it is just one stick you could still have two working systems, one would just be on crutches for a bit till the dual-channel was restored with the replacement RAM.

Either way, I'm glad you got it nailed. Cheers! ... And welcome to the forums :)
 
Thanks! Yes, I'll try one stick at a time tomorrow. I'd like to know, too. :)

Don't forget, if you have quality RAM, it will generally be warrantied for life.
You can set up an RMA and get those sticks replaced....takes about a week.

In the meantime I'd suggest buying some new RAM so your son doesn't come unglued.:eek:
 
LOL! Well, thankfully, I have a "guest" computer, too (four in the room, total), and I'm going to use its ram for now and see if Crucial will replace the problem ram. Worse case, I have to buy 4GB of ram. That's a whole lot better than where I was two days ago!

Great site here, and great folks!
 
Back
Top