Random CTD, BSoD, Lockup

Greetings all,

First time here, found this site through Google. Since upgrading my sytem, I have been geting random crashes to desktop, BSoDs, and lockups. They happen most often when running games, but also while at desktop, running utils, tests, etc.

While running Prime95, I get random crashes or errors running various tests and am unable to pinpoint cause. PSU voltages seem stable. Temps are in acceptable range, although they are never below 62C even with good cooler.

My system:
AMD Athlon 64 X2 4400+ AM2 (new)
Abit KN9 NF4ULTRA Motherboard (new)
(2) 1GB Geil DDR2 800 (PC2 6400) Dual Channel Kit (new)
EVGA 320-P2-N815-AR 8800GTS 320 (new)
Zalman CNPS9500 LED CPU Cooler (new)
RaidMax RX-530SS 530W PSU (new)
Sony DVD RW DW-D22A
TSSTcorp CD/DVDW TS-H552U
Maxtor DiamondMax 21 STM3200820A 200GB Ultra ATA 100 7200RPM
Seagate Barracuda 7200.7 plus st3120026a 120GB
Western Digital WD12 00JB-00GVA0 120GB
WinXP SP2

All drivers and bios are up to date. Video drivers were uninstalled, cleaned, and reinstalled.

Windows dump logs are always different. Latest is posted below. Windows eror reporting says different things, such as: driver problem, hardware problem, unknown problem.

Please help! I have been building my own computers for many years, but this is bafling and frustrating me.



Dump file:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini050607-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun May 6 02:26:25.687 2007 (GMT-4)
System Uptime: 0 days 0:20:09.461
Loading Kernel Symbols
....................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {448da172, 2, 0, 89dae872}

Probably caused by : i8042prt.sys ( i8042prt!I8042MouseIsrDpc+120 )

Followup: MachineOwner
---------

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 448da172, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 89dae872, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 448da172

CURRENT_IRQL: 2

FAULTING_IP:
+ffffffff89dae872
89dae872 da893a8fb9ba fimul dword ptr mouclass!MouseClassServiceCallback (bab98f3a)[ecx]

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: CityOfHeroes.ex

LAST_CONTROL_TRANSFER: from baaa00fb to 89dae872

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacd7f64 baaa00fb 57000008 baa98459 bacd7fa0 0x89dae872
bacd7fcc 805450bf 89daee98 01daec88 00000000 i8042prt!I8042MouseIsrDpc+0x120
bacd7ff4 80544c2b b5c6dd44 00000000 00000000 nt!KiRetireDpcList+0x61
bacd7ff8 b5c6dd44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
80544c2b 00000000 00000009 0081850f bb830000 0xb5c6dd44


STACK_COMMAND: kb

FOLLOWUP_IP:
i8042prt!I8042MouseIsrDpc+120
baaa00fb 85ff test edi,edi

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: i8042prt!I8042MouseIsrDpc+120

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: i8042prt

IMAGE_NAME: i8042prt.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ecc

FAILURE_BUCKET_ID: 0xD1_i8042prt!I8042MouseIsrDpc+120

BUCKET_ID: 0xD1_i8042prt!I8042MouseIsrDpc+120

Followup: MachineOwner
---------

eax=bacd09a0 ebx=89dae860 ecx=89d41238 edx=00000000 esi=bab88472 edi=00000001
eip=89dae872 esp=bacd7f68 ebp=bacd7fcc iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
89dae872 da893a8fb9ba fimul dword ptr mouclass!MouseClassServiceCallback (bab98f3a)[ecx] ds:0023:448da172=????????
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacd7f64 baaa00fb 57000008 baa98459 bacd7fa0 0x89dae872
bacd7fcc 805450bf 89daee98 01daec88 00000000 i8042prt!I8042MouseIsrDpc+0x120 (FPO: [Non-Fpo])
bacd7ff4 80544c2b b5c6dd44 00000000 00000000 nt!KiRetireDpcList+0x61 (FPO: [0,1,0])
bacd7ff8 b5c6dd44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b (FPO: [Uses EBP] [0,0,1])
80544c2b 00000000 00000009 0081850f bb830000 0xb5c6dd44
start end module name
804d7000 806e2000 nt ntkrpamp.exe Wed Feb 28 03:38:53 2007 (45E53F9D)
806e2000 80702d00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
b2df1000 b2e1b180 kmixer kmixer.sys Wed Jun 14 04:47:45 2006 (448FCD31)
b563f000 b567f280 HTTP HTTP.sys Thu Mar 16 20:33:09 2006 (441A03C5)
b5bd4000 b5c25480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
b5d3e000 b5d6a400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
b5f73000 b5f87400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
b61bc000 b61bf280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
b64d0000 b64e6d80 dump_nvata dump_nvata.sys Thu Aug 18 20:52:05 2005 (43052D35)
b64e7000 b64f7280 Udfs Udfs.SYS Wed Aug 04 02:00:27 2004 (41107B7B)
b6518000 b651a900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
b65c0000 b662ea00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
b662f000 b6659a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
b665a000 b667bd00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
b667c000 b669cf00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
b669d000 b66c4c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
b66c5000 b671cd80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
b671d000 b672f400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
b6778000 b678fe20 VETEBOOT VETEBOOT.SYS Mon Apr 16 02:24:47 2007 (462316AF)
b6790000 b68189c0 VETEFILE VETEFILE.SYS Mon Apr 16 02:24:48 2007 (462316B0)
b9951000 b9953280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
b9969000 b999c200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
b99bd000 b99cbd80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
b9a1d000 b9a25880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
b9a3d000 b9a4de00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
b9a4e000 b9a64680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
b9a65000 b9a78780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
b9a79000 ba0e64e0 nv4_mini nv4_mini.sys Fri Apr 20 09:37:06 2007 (4628C202)
ba0e7000 ba119d80 NVSNPU NVSNPU.SYS Wed Apr 06 06:22:01 2005 (4253B849)
ba11a000 ba159f00 NVNRM NVNRM.SYS Wed Apr 06 06:22:11 2005 (4253B853)
ba15a000 ba17c680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
ba17d000 ba1a0980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
ba1a1000 ba5785c0 ALCXWDM ALCXWDM.SYS Thu Mar 08 01:34:43 2007 (45EFAE83)
ba579000 ba59be80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
ba5b0000 ba5b3820 VETFDDNT VETFDDNT.SYS Wed Jan 26 19:26:02 2005 (41F8351A)
ba5e4000 ba5fe580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
ba5ff000 ba62ba80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
ba62c000 ba6b8480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
ba6b9000 ba6cf780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
ba6d0000 ba6e1f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
ba6e2000 ba701780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
ba702000 ba718d80 nvata nvata.sys Thu Aug 18 20:52:05 2005 (43052D35)
ba719000 ba730800 SCSIPORT SCSIPORT.SYS Wed Aug 04 01:59:39 2004 (41107B4B)
ba731000 ba748480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
ba749000 ba767880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
ba768000 ba778a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
ba779000 ba7a6d80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
ba8a8000 ba8b0c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
ba8b8000 ba8c6e80 ohci1394 ohci1394.sys Wed Aug 04 02:10:05 2004 (41107DBD)
ba8c8000 ba8d5000 1394BUS 1394BUS.SYS Wed Aug 04 02:10:03 2004 (41107DBB)
ba8d8000 ba8e2500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
ba8e8000 ba8f4c80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
ba8f8000 ba900f80 ultra ultra.sys Fri Aug 17 16:52:19 2001 (3B7D8403)
ba908000 ba910e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
ba918000 ba924200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
ba928000 ba930b80 PxHelp20 PxHelp20.sys Wed Oct 18 13:33:53 2006 (45366581)
ba968000 ba970300 NVENETFD NVENETFD.sys Wed Apr 06 06:22:26 2005 (4253B862)
ba9f8000 baa00700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
baa18000 baa20700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
baa28000 baa37900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
baa48000 baa50a00 processr processr.sys Wed Aug 04 01:59:14 2004 (41107B32)
baa58000 baa66b80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
baa68000 baa72380 Imapi Imapi.SYS Wed Aug 04 02:00:12 2004 (41107B6C)
baa78000 baa84180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
baa88000 baa96080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
baa98000 baaa4e00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
baaa8000 baab4880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
baab8000 baac2200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
baac8000 baad3d00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
baad8000 baae0900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
baae8000 baaf1f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
baaf8000 bab06000 AmdLLD AmdLLD.sys Wed Nov 01 16:42:12 2006 (454906A4)
bab08000 bab11480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
bab18000 bab26100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
bab30000 bab34900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
bab40000 bab44500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
bab68000 bab69000 fdc fdc.sys unavailable (00000000)
bab78000 bab7cce0 VET_FILT VET-FILT.SYS Wed Jan 26 19:26:02 2005 (41F8351A)
bab88000 bab8cf80 point32 point32.sys Tue Mar 15 05:40:15 2005 (4236AD7F)
bab98000 bab9da00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
baba0000 baba5f80 VETMONNT VETMONNT.SYS Tue Jun 20 01:58:52 2006 (44978E9C)
baba8000 babae000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
babf0000 babf4880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
bac18000 bac1c280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
bac20000 bac24580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
bac30000 bac34080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
bac38000 bac3d200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
bac48000 bac4e800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
bac60000 bac64a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
bac68000 bac6f880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
baca8000 bacad000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
bad48000 bad4b920 VET_REC VET-REC.SYS Wed Jan 26 19:26:02 2005 (41F8351A)
bad60000 bad63280 nvnetbus nvnetbus.sys Wed Apr 06 06:22:28 2005 (4253B864)
bad7c000 bad7e580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
bad98000 bad9bc80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
badac000 badad200 ABIT_IO ABIT-IO.sys Thu Dec 08 01:53:04 2005 (4397D850)
badb6000 badb7100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
badbc000 badbd280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
badc0000 badc1f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
badcc000 badcd080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
badd0000 badd1080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
badd4000 badd5080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
bade0000 bade1100 PfModNT PfModNT.sys Wed Dec 15 23:14:08 1999 (38586710)
bade4000 bade5b00 nvoclock nvoclock.sys Wed Apr 04 17:20:58 2007 (461416BA)
bae08000 bae09100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
bae70000 bae70d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
baf0c000 baf0cc00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
baf7e000 baf7eb80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
bafc9000 bafc9b80 mbmiodrvr mbmiodrvr.sys Sat Apr 10 10:42:35 2004 (407807DB)
baff7000 baff7d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 08:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf9d5000 bff03e00 nv4_disp nv4_disp.dll Fri Apr 20 09:33:39 2007 (4628C133)

Unloaded modules:
b5f25000 b5f50000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b5fe8000 b5ff5000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b6008000 b6016000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae1e000 bae20000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bae8a000 bae8b000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b5f50000 b5f73000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
b6158000 b6168000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
b5d02000 b5d16000 Parport.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bab58000 bab5d000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
bad3c000 bad3f000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

I will also add that I have tried each memory stick individually in different slots with same results. The only bios modificaions were to up the DDRs voltage to 1.9V (required by mem manuf.) and disabling the cpu fan warning (necessitated by having to plug zalman cooler into sys fan header).

 

I understand the temp is high, that is why I mentioned it. It was a couple of degrees higher with the stock cooler and that is why I bought the Zalman. Unfortunately, it is still high and I am thinking that might possibly be a clue to my problem.

I also understand the log showed that the crash occured in the mouse driver while running City of Heroes. As I mentioned in my post, this changes with each crash. Sometimes it is reported as mouse driver, sometimes as sound driver, sometimes as just a driver, sometimes as an unmentioned hardware error, sometimes no report at all. The crashing sometimes happens in a game, in an application, or even just while idle at the desktop.

Like I also mentioned, I tried both memory sticks seperately and in different slots, so I am doubting it is the memory. However, i will run the windows memory test tonight, just in case.

I am beginning to suspect it may be the cheap motherboard I have, but I sure wish somebody could recognize these symptoms and suggest some more options.

Thank you for your help.

 

I'd agree with Pete, your CPU temperature is off the deep end and needs to be fixed. First thoughts would include improperly mounted HSF and bad thermal paste job but your Zahlman comment in general scares me - one can run a single wire on the 3 pin plug to your CPU fan header and invoke CPU fan failure warning but even better, CPU overheating temperature protection. You should have either a single wire or 3 wire lead on a 3 pin female connector whether or not you use that little black variable speed gizmo. Pete was kind, I'd call your CPU temperature dangerously indicative of a major problem.

Not a problem - its not your ?cheap? motherboard, but instead, the cheap power supply you are using that is not able to hold steady voltages. Once you fix your HSF problem, replace your power supply. Yours is notorious and will continue to cause numerous memory errors because it can't maintain the steady voltage necessary for trouble free operation. I would anticipate you will have trouble running those memory tests but should you go to Geil, they will confirm my comments about your RAIDMAX PSU and its effect on their memory.

 

The HSF has been remounted and repasted a few times now (using arctic silver 5) always with the same results. The Zalman fan connector is a 3 pin connector and thus has to be connect on the sys fan (3 pin) header of the motherboard instead of the cpu fan header which is a 4 pin. I had virtually the same results with the stock HSF which is 4 pin, so I don't think that is the problem. I definitely want to get these temps down into a normal range, but I don't think it's the HSF mounting or connection at fault.

Like I mentioned before, the PSU readings from the motherboard monitoring program (Abit EQ) shows voltages about normal with very small variance. Am I missing something? None of my readings are ever below their set values. Could the PSU be under-supplying or over-supplying the system despite these readings?

Thank you for your help.


Edit: I forgot to mention that the memory tests (even the advanced tests) ran perfectly with no errors.

 

Sorry for the delayed response. Two things. First, there is a warning in your manual against using a PSU with a 20 pin ATX header. Your RAIDMAX is a 20 pin PSU. Secondly, you are correct re: the 4 pin header for CPU fan and there are instructions re: a 3 pin fan. "In the situation when connecting a 3-pin CPU fan assembly, and you still want the speed control function to take effect, you must:
1. Plug the 3-pin CPU fan assembly to "SYSFAN1" fan power connector.
2. In the "PC Health Status" of the BIOS Setup Menu, set the "SYS FanEQ Reference Temp." from the default "System" to "CPUâ€. "

You can tell me that your power shows little or no fluctuation and I will argue that this is a notoriously bad PSU re: variable power output. I'm not trying to give you a tough time, I have considerable experience with this particular PSU. This is an aluminum enclosure that is available in silver, gold and black and they are all bad news - be it the 400, 450 or 500. They look nice but thats all that can be said about them. I have purchased at least 50 of these during my lifetime but haven't bought one for at least three years. These are also available under the POWMAX name and a couple of others.

 

Rockster,

First, let me thank you for taking the time to help me. I also appreciate that you took the time to look up quotes from manuals. Sign of a very sincere and helpful person.

The Raidmax that I have actually has a 20+4 connector. However, I have already ordered a new PSU.... an OCZ700GXSSLI 700W RT (please tell me this is a decent one). Hopefully this will help with my issues. I really don't think it will help with my heat problem, tho.

I did see the instructions for connecting a cpu fan on the sysfan header, but I am running the fan wide open right now and wasn't really worried about that particular setting until I get my heat problem under control.

As a side note, I googled my PSU for reviews and comments but found little or no negatives. Same for the one I just ordered. It seems like most of the reviews of PSUs that come up are years old.

Thanks again for your help. If you have any other ideas on the cause of my heat problems, please don't hesitate to post them. I'll post the results of the PSU replacement after I receive it tomorrow (Friday).

 

Patch:

Thanks for the kind words. As you probably surmized, I used to like those RAIDMAX/POWMAX PSU's until I started encountering numerous problems. Ten years ago, a POWMAX 350 was a very fine component that could be purchased for a fraction of the price of anything similar. Unfortunately, when they shifted to the aluminum housing, they got away from some of their quality standards re: the guts.

Your OCZ selection is a great one. I haven't used any of their PSU's but they are very highly rated. I use a lot of OCZ memory and have been a loyal fan of theirs since their early days as a small Idaho based company that sold hand selected memory and modded OC'ed socket A CPU's among other things. You won't be disappointed.

As to the heat issue, I'm also a big fan (pun intended) of Zahlman. There are instructions and a video on applying Artic Silver at the Artic Silver website. The key here is to apply a very very thin even layer of paste. One wants to wind up with uniform coverage and no air pockets using the philosophy that less is best. I use a credit card shaped piece of thin plastic (pocket calendars from my insurance agent) to achieve this.

Another area to investigate and pursue is the bigger picture of air flow through your case. If you are using ribbon cables, some improvement may come by converting to round IDE and floppy cables. The best place I know of to purchase these is at SVC.com. Some relief can also be achieved by cleaning up your wiring in general - if it looks like spaghetti, tidy things up. Additionally, one wants to have at least one intake fan in the front of the case and one exhaust fan in the back of the case. There are a lot of little tricks one can use depending on the specific case and the guts of any given machine. If you want some assistance in this regard, we can get into specifics but there has to be a reason why you are running so hot. I also hope your case is not crammed into a piece of furniture or enclosure that is restricting ventilation.

Good Luck and give yourself a lot of atta-boys on the OCZ PSU purchase.

 

Unfortunately the OCZ was DOA. However, contacting Newegg has got me another on the way. They seem committed to get the upgrades I bought from them up and running properly. I don't think I will ever buy from anybody else again. They were very accomodating and helpful. I'll report back once I have the new PSU.

 

I had a look at the Abit website. Their most recent BIOS update has a "temperature recalibration ". This might not be very significant, the temperature readouts probably won't change dramatically. It may let you see more accurate readings though, and if the fan/s are controlled by these readouts, they should work correctly. Don't get excited that this will fix the temperatures, it will just fix the readouts.

If other temperatures, like the System temperature are high, look at the air flow system through the case like Rockster mentioned. The air flow should be in at the bottom/front and out at the top/back. Could any fans be blowing in the wrong direction?

Just something to check if you haven't already...Task Manager -> Performance, is the CPU idling OK?

Matt

 

Mattman,

Thanks for the help. The latest bios update for my MB (KN9) says nothing about temperatures. In any event, I have the latest updates and drivers for every component in my system. I'm convinced my heat problem is not an external issue. I've had the cover off with an external fan blowing in and it made little difference. My case is well ventilated. Sys temps are normal.

CPU was idling just fine. If the new power supply doesn't help, the MB will be replaced next, then CPU, if needed. I'll get to the bottom of it. It's just frustrating when you get the money together for a decent system upgrade and end up with intermittent problems. Thankfully, I bought from Newegg. I can't say enough about their customer support.

 

New PSU arrived today. No difference in temps or crashing problems.

I'm beginning to get a complex.

 

It sounds like you are doing the right things.

Is your motherboard a KN9 Ultra?

The only other thing I can think of is that there are one or more bent pins on the processor.

Matt

 

I'd concur with Matt re: trying the new BIOS and I'd certainly reseat the CPU and remount the HSF with a fresh dose of Artic Silver. Something is just not right here - that temperature is way out of whack.

As to your crashing BSOD - I recall you had your memory voltage set at 1.9V and according to the mfg, this is the low end of the recommended range. I think it was something like 1.9 - 2.2 but check this to confirm it and if correct, increase this voltage incrementally. Also check your current memory voltage reading in the BIOS to get the "most accurate" present value. Just because you have it set at 1.9 doesn't mean thats the actual value.

 

My motherboard is NOT a KN9 Ultra. It is a plain KN9 that has the NForce4 Ultra chipset. Sorry for the confusion.

Setting the memory voltage to 1.90V is netting me a voltage reading of 1.95. I didn't encounter any problems running advanced memory tests multiple times.

The CPU has been reseated and re-gooped with no difference.

I am now suspecting a faulty video card as the cause of the crashing. Just a hunch, but I am returning it to Newegg for replacement.

That will leave the motherboard and processor. Sigh.

Again, thanks for your help.

 

My mistake, I am not up on different nVidia chipsets, but I should have suspected.

If Rockster is not around, you should increase the RAM voltage stepwise. This will reduce the load on the RAM (higher voltages slow things down). So edge your way towards 2.2 as he suggested and see if the system becomes stable. Rockster will probably elaborate.

Matt

 

I'm pretty much fresh out of ideas. I don't like those temperatures but you've redone just about all that should be required to bring them back in line with something closer to "acceptable ". I'll assume you are using the correct mounting brackets for Zahlman HSF (they come with several) and that you put on a very thin layer of Artic Silver after checking your CPU for bent pins and re-seating it.

Perhaps a fresh set of eyes will see something that we are missing. This is sounding very much like "bad caps" behavior but that might be a cop out. I'm at a loss.

 

If it might be important...

I have an Abit KN9-SLI. I was investigating if it could take an Opteron processor, but Abit specifies only Windsor cores for the KN9 series, so I just installed an standard AM2. Is it definitely a Windsor core? AMD have updated some of the cores in the AM2 range (one I know is the Brisbane).

Matt