• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Conflicts/Sharing in Sys. Information

My computer runs fine and it has for the past 1+year since I built it, but then along comes "GUILD WARS" that makes it hard restart, freeze or just boot me from the game back to the desktop at misc. intervals..... 10min-4+hours of playing. I've had more crashes with this game in the past 2weeks then I have in the past 10years of all my other computers put together! It's not just me having the problems, nor is it just Nvidia or Intel components. Do a Google search for more info. None of the other top of the line games today give me any problems....... Zero, Ziltch, Nadda!

Up to date on drivers, patches & Win updates.
(No overclocks on anything....... All stock speeds)
I've also monitored temps and nothing is out of the ordinary.


Win 2000 Pro
Intel 865PERL
Intel 3.2/800 (retail hsf)
2x512 Mushkin pc3200 lvl1 black 2-3-2 (matched pair)
EVGA 6800GT
Antec 350w PSU (it's the only component that's on my list as the culprit at the moment)
Antec 835II w/4x case fans
Dial up@ 49.2k - 50.6k


Wondering if any of the below IRQ Sharing/Conflicts can do what I've described?

IRQ 16 Nvidia GeForce 6800GT
IRQ 16 Intel (R) 82801EB USB Universal Host Controller - 24D2
IRQ 16 Intel (R) 82801EB USB Universal Host Controller - 24DE
IRQ 17 Creative SB Audigy 2 (WDM)
IRQ 17 Intel (R) ICH5/ICH5-M SMBus Controller - 24D3 (Intel (R) SMBus 2.0 Driver)
IRQ 18 Intel (R) 82801EB USB Universal Host Controller - 24D7
IRQ 18 OHCI Compliant IEEE 1394 Host Controller
IRQ 18 Conexant SoftK56 TAM PCI Modem
IRQ 18 Intel (R) 82801EB Ultra ATA Storage Controllers



EDIT---- I did find this on Mushkins website. Any relation to my problem?

Why is my PC3200 or PC3500 unstable?
Check that your memory latency times are set properly for your product, you may have to manually configure these timings. Check our BIOS settings page for more info. Try increasing your DDR voltage. JEDEC Spec is 2.6V for PC3200 but Mushkin supports voltages up to 2.8V for our low latency high frequency memory. If you have an 865 or 875 based motherboard try disabling MAT and or PAT and disable "Legacy USB Support". On AMD based systems make sure you are using at least a 350watt, high-quality power supply. Also make sure that the DRAM ratio is set properly for your CPU. 266Mhz core CPUs should run at a 4:6 ratio, 333MHz core CPUs should run at a 5:6 ratio and only 400MHz core CPUs are guaranteed at 1:1. CPU modifications, unlocked multipliers and water cooling do not effect our guarantee. Try going to our support page and check out our troubleshooting tips and other support resources.
 
Are you using some extra cooling with those Mushkin memory modules
other than the active cooling (heat spreaders)?

Also, did you remove the Video card before installing the RAM?
(not doing so creates a problem with the memory retention mechanism on the MB)
 
It's around 23C-24C in this room at all times (73-75F) and the case is an Antec mid tower 835II w/2x intake fans & 2x exhaust. My whole pc runs rather cool. So, there's really no need for extra cooling for the ram.

As for the VC install, yes, it was installed after the ram. Very difficult to do it any other way. As you said.......because of the ram retention clips.

I did notice one thing the other night that I jumped on real quick! I went into the Bios and noticed that after all this time (over a year) I had the onboard sound "Enabled'. Well since I own an Audigy2, I disabled it of course. Played Guild Wars all day yesterday with only "ONE" boot back to the desktop/sending error report to Arenanet, etc. I can live with that as I was having 6+ restarts, freezes etc. a day before that.

Very strange that the onboard sound conflict did'nt cause me any other problems for that 1+ year though.
 
I would also check to see if hyperthreading is enabled, since you have win2k you should have hyperthreading disabled, as Win2k is not hyperthreading ready, and will see hyperthreading as 2 physical CPU's, which can cause problems.
 
Back
Top