• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Does this sound like a memory issue?

Joined
Feb 6, 2006
Messages
60
A friend of mine has a Voodoo PC, 680i board, water cooled Q6600 quad core, dual 8800gtx's; unfortunately I'm not sure which RAM is inside. It was recently overclocked from 2.4ghz to a modest 2.8ghz, no changes to vcore or memory voltage.
Recently when he turned on his pc, he would get no screen, no bios beeps, nothing.
After a few tries it came up, it works until he gets random .dll errors. His device manager is also showing that his usb card reader is on the fritz. He is running Vista 32bit.

It was overclocked about 4 months ago and running stable. I'm assuming bringing up the memory voltage a bit would be a safe bet, and even the cpu voltage.

But, other than memtest is there anything else I can look for when I finally get in front of the machine, that you guys recommend? Turning off your PC, your RAM is cleared correct?

An example of a .dll error he keeps getting:

Log Name: Application
Source: Application Error
Date: 3/12/2008 10:46:05 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: GaryPC
Description:
Faulting application svchost.exe_EMDMgmt, version 6.0.6000.16386, time stamp 0x4549adc4, faulting module emdmgmt.dll, version 6.0.6000.16386, time stamp 0x4549bcfc, exception code 0xc0000005, fault offset 0x0000ac03, process id 0x1b04, application start time 0x01c884cd427587e0.


Thanks in advance fellow members :)
 
If you have PCI and/or PCI-Express frequency settings, make sure they're at 33MHz and 100MHz respectively. You can try running Memtest86+. Try upping the voltage of the RAM by .2 or .3 if necessary. Also make sure the RAM is running in sync with the FSB if it's currently running faster (yes, that's right, bring the speed DOWN to be in sync if need be)
 
Back
Top