Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: Spatula on August 23, 2007, 02:58:23 AM
-
Ok, my old mobo died, so i had to replace it, and get new RAM, new vid card, and new CPU.
This is what i got:
- Gigabyte 965GM-DS2
- Core 2 Duo 4500 (cheapy for now)
- 2x1gig DDR2 800 APacer RAM
- Powercolor Radeon X1950Pro 512M DDR3
I got it all updated, patched, etc. Done all the suggestions in:
http://forums.hitechcreations.com/forums/showthread.php?s=&threadid=199451
http://forums.hitechcreations.com/forums/showthread.php?s=&threadid=209066
I put it all in my old case which has a 400Watt power supply (or so it says).
But here's the rub. Im noticing some odd things:
- Random hard lock-ups. These seem to happen most when im browsing the web and/or doing many things at once. Never seen it happen playing games tho. These are total freezes - have to hard reset. Sometime it hard locks right at the end of the boot process - eg when all the task-tray apps are loading.
- AH2 Frame rates are lower than i would have expected. My old PC (AMD socket 754 Athlon 64 3200, 1.5 Gig RAM, Radeon X800pro AGP) ran better. Frame rates more stable, and generally higher (40-60 FPS). Now im getting 30-60 FPS and lots of annoying micro-pauses. I preload textures and skins. For both my old and new systems i was running 1280x1024 with 1024 textures (hi-res pack) with all sliders fully up, 6xAA, 4xAF. I would have thought i would get better perf with a dual core, DDR2-800 dual channel, and a 1950pro...
- It seems sometimes AH2 does not run anti-aliased even when its set in the catalyst control center to be always 4x. Sometimes it does, sometimes it doesnt. Very weird.
Im running the latest BIOS, latest MOBO drivers, and Cat 7.8 drivers.
Ok, heres my dxdiag:
------------------
System Information
------------------
Time of this report: 8/23/2007, 19:54:19
Machine name: ORAC
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: 965GM-DS2
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2 CPUs)
Memory: 2048MB RAM
Page File: 439MB used, 3502MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: Radeon X1950 Pro
Manufacturer: ATI Technologies Inc.
Chip type: ATI Radeon Graphics Processor (0x7280)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_7280&SUBSYS_2204148C&REV_00
Display Memory: 512.0 MB
Current Mode: 1152 x 864 (32 bit) (85Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6715 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 7/28/2007 15:30:45, 269312 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 7/28/2007 15:30:27, 2371584 bytes
Device Identifier: {D7B71EE2-31C0-11CF-076D-0E02A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x7280
SubSys ID: 0x2204148C
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV8_B ModeWMV8_A ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
-------------
Sound Devices
-------------
Description: SB Audigy Audio [B000]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_00511102&REV_03
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0441 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 10/8/2003 10:06:04, 366160 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 191999
Static/Strm HW Mix Bufs: 64, 62
Static/Strm HW 3D Bufs: 64, 62
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: SB Audigy Audio [B000]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0441 (English)
Driver Attributes: Final Retail
Date and Size: 10/8/2003 10:06:04, 366160 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB Audigy DirectMusic Synthesizer [B000], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB Audigy Audio [B000], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Synth A [B000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Sw Synth [B000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Synth B [B000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy MIDI IO [B000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy MIDI IO [B000] [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
Registry: OK
Test Result: Not run
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: 3 axis 4 button joystick with hat switch
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0583, 0x2030
FF Driver: n/a
Device Name: CH PRO THROTTLE USB
Attached: 1
Controller ID: 0x1
Vendor/Product ID: 0x068E, 0x00F1
FF Driver: n/a
Device Name: CH FIGHTERSTICK USB
Attached: 1
Controller ID: 0x2
Vendor/Product ID: 0x068E, 0x00F3
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x2830
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 8/3/2004 23:08:44, 57600 bytes
| Driver: usbd.sys, 8/5/2004 00:00:00, 4736 bytes
-
----------------
Gameport Devices
----------------
+ Intel(R) 82801 PCI Bridge - 244E
| Location: PCI bus 0, device 30, function 0
| Matching Device ID: pci\ven_8086&dev_244e
| Service: pci
| Driver: pci.sys, 8/3/2004 23:07:48, 68224 bytes
|
+-+ Creative Game Port
| | Location: PCI bus 5, device 1, function 1
| | Matching Device ID: pci\ven_1102&dev_7003&subsys_00401102
| | Service: gameenum
| | Driver: gameenum.sys, 8/3/2004 23:08:22, 10624 bytes
------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/5/2004 00:00:00, 52736 bytes
| Driver: kbdclass.sys, 8/5/2004 00:00:00, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 01:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/5/2004 00:00:00, 24576 bytes
|
+ PS/2 Compatible Mouse
| Matching Device ID: *pnp0f13
| Service: i8042prt
| Driver: i8042prt.sys, 8/5/2004 00:00:00, 52736 bytes
| Driver: mouclass.sys, 8/5/2004 00:00:00, 23040 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 01:01:08, 40840 bytes
| Driver: mouclass.sys, 8/5/2004 00:00:00, 23040 bytes
----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK
-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 Serial Service Provider: COM2
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -
-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
-------------------------
DirectPlay Lobbyable Apps
-------------------------
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 41.0 GB
Total Space: 50.0 GB
File System: NTFS
Model: Maxtor 6Y080M0
Drive: D:
Free Space: 0.2 GB
Total Space: 4.1 GB
File System: FAT32
Model: ST34312A SCSI Disk Device
Drive: E:
Free Space: 7.0 GB
Total Space: 26.3 GB
File System: NTFS
Model: Maxtor 6Y080M0
Drive: F:
Model: MAT****A DVD-ROM SR-8583 SCSI CdRom Device
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 49536 bytes
-
--------------
System Devices
--------------
Name: Intel(R) P965/G965/G35 PCI Express Root Port - 29A1
Device ID: PCI\VEN_8086&DEV_29A1&SUBSYS_00000000&REV_02\3&13C0B0C5&0&08
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) P965/G965/G35 Processor to I/O Controller - 29A0
Device ID: PCI\VEN_8086&DEV_29A0&SUBSYS_00000000&REV_02\3&13C0B0C5&0&00
Driver: n/a
Name: Microsoft UAA Bus Driver for High Definition Audio
Device ID: PCI\VEN_8086&DEV_284B&SUBSYS_A0021458&REV_02\3&13C0B0C5&0&D8
Driver: C:\WINDOWS\system32\DRIVERS\hdaudbus.sys, 5.10.0001.5013 (English), 1/7/2005 17:07:18, 138752 bytes
Name: Intel(R) ICH8 Family PCI Express Root Port 3 - 2843
Device ID: PCI\VEN_8086&DEV_2843&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E2
Driver: n/a
Name: Intel(R) ICH8 Family PCI Express Root Port 2 - 2841
Device ID: PCI\VEN_8086&DEV_2841&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E1
Driver: n/a
Name: Intel(R) ICH8 Family PCI Express Root Port 1 - 283F
Device ID: PCI\VEN_8086&DEV_283F&SUBSYS_00000000&REV_02\3&13C0B0C5&0&E0
Driver: n/a
Name: Intel(R) ICH8 Family SMBus Controller - 283E
Device ID: PCI\VEN_8086&DEV_283E&SUBSYS_50011458&REV_02\3&13C0B0C5&0&FB
Driver: n/a
Name: Intel(R) ICH8 Family USB2 Enhanced Host Controller - 283A
Device ID: PCI\VEN_8086&DEV_283A&SUBSYS_50061458&REV_02\3&13C0B0C5&0&D7
Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 26624 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 7168 bytes
Name: Intel(R) ICH8 Family USB2 Enhanced Host Controller - 2836
Device ID: PCI\VEN_8086&DEV_2836&SUBSYS_50061458&REV_02\3&13C0B0C5&0&EF
Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 26624 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 7168 bytes
Name: Intel(R) ICH8 Family USB Universal Host Controller - 2835
Device ID: PCI\VEN_8086&DEV_2835&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D1
Driver: n/a
Name: Intel(R) ICH8 Family USB Universal Host Controller - 2834
Device ID: PCI\VEN_8086&DEV_2834&SUBSYS_50041458&REV_02\3&13C0B0C5&0&D0
Driver: n/a
Name: Intel(R) ICH8 Family USB Universal Host Controller - 2832
Device ID: PCI\VEN_8086&DEV_2832&SUBSYS_50041458&REV_02\3&13C0B0C5&0&EA
Driver: n/a
Name: Intel(R) ICH8 Family USB Universal Host Controller - 2831
Device ID: PCI\VEN_8086&DEV_2831&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E9
Driver: n/a
Name: Intel(R) ICH8 Family USB Universal Host Controller - 2830
Device ID: PCI\VEN_8086&DEV_2830&SUBSYS_50041458&REV_02\3&13C0B0C5&0&E8
Driver: n/a
Name: Intel(R) ICH8 2 port Serial ATA Storage Controller - 2825
Device ID: PCI\VEN_8086&DEV_2825&SUBSYS_B0021458&REV_02\3&13C0B0C5&0&FD
Driver: n/a
Name: Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
Device ID: PCI\VEN_8086&DEV_2820&SUBSYS_B0021458&REV_02\3&13C0B0C5&0&FA
Driver: n/a
Name: Intel(R) ICH8/ICH8R Family LPC Interface Controller - 2810
Device ID: PCI\VEN_8086&DEV_2810&SUBSYS_00000000&REV_02\3&13C0B0C5&0&F8
Driver: n/a
Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&13C0B0C5&0&F0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: GIGABYTE GBB36X Controller
Device ID: PCI\VEN_197B&DEV_2363&SUBSYS_B0001458&REV_02\4&52FDD2B&0&00E2
Driver: C:\WINDOWS\system32\DRIVERS\jraid.sys, 1.17.0007.0005 (English), 11/22/2006 06:27:58, 43648 bytes
Driver: C:\WINDOWS\system32\DRIVERS\JGOGO.sys, 5.00.3790.0001 (English), 2/8/2006 15:52:58, 6912 bytes
Name: Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Device ID: PCI\VEN_11AB&DEV_4364&SUBSYS_E0001458&REV_13\4&38686460&0&00E1
Driver: n/a
Name: Creative Game Port
Device ID: PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_03\4&20E0FF6A&0&09F0
Driver: C:\WINDOWS\system32\drivers\gameenum.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:22, 10624 bytes
Name: OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_00\4&20E0FF6A&0&0AF0
Driver: C:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 61056 bytes
Driver: C:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 53248 bytes
Driver: C:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 61824 bytes
Driver: C:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 60800 bytes
Driver: C:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/18/2001 01:46:40, 6400 bytes
Name: Creative SB Audigy
Device ID: PCI\VEN_1102&DEV_0004&SUBSYS_00511102&REV_03\4&20E0FF6A&0&08F0
Driver: C:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (English), 8/4/2004 00:56:44, 4096 bytes
Driver: C:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (English), 8/4/2004 00:56:58, 130048 bytes
Driver: C:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (English), 8/3/2004 23:15:22, 140928 bytes
Driver: C:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:00, 60288 bytes
Driver: C:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.1364 (English), 3/16/2004 10:58:20, 136960 bytes
Driver: C:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (English), 8/3/2004 23:08:04, 48640 bytes
Driver: C:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 00:56:58, 23552 bytes
Driver: C:\WINDOWS\system32\drivers\ctac32k.sys, 5.12.0001.0442 (English), 10/21/2003 17:22:18, 645360 bytes
Driver: C:\WINDOWS\system32\drivers\ctaud2k.sys, 5.12.0001.0441 (English), 10/8/2003 10:06:04, 366160 bytes
Driver: C:\WINDOWS\system32\drivers\ctoss2k.sys, 5.12.0001.0441 (English), 10/8/2003 10:06:50, 178672 bytes
Driver: C:\WINDOWS\system32\drivers\ctprxy2k.sys, 5.12.0001.0441 (English), 10/8/2003 10:08:12, 6096 bytes
Driver: C:\WINDOWS\system32\drivers\ctsfm2k.sys, 5.12.0001.0441 (English), 10/8/2003 10:09:10, 130288 bytes
Driver: C:\WINDOWS\system32\drivers\emupia2k.sys, 5.12.0001.0442 (English), 10/13/2003 17:42:12, 145488 bytes
Driver: C:\WINDOWS\system32\drivers\ha10kx2k.sys, 5.12.0001.0444 (English), 10/21/2003 17:26:08, 904496 bytes
Driver: C:\WINDOWS\system32\drivers\haP16v2k.sys, 5.12.0001.0442 (English), 10/21/2003 17:23:44, 148432 bytes
Driver: C:\WINDOWS\system32\drivers\pfmodnt.sys, 3.00.0000.0003 (English), 3/5/2003 15:07:46, 15840 bytes
Driver: C:\WINDOWS\system32\ctdlang.dat, 10/21/2003 17:54:50, 217272 bytes
Driver: C:\WINDOWS\system32\ctstatic.dat, 10/21/2003 17:47:40, 298971 bytes
Driver: C:\WINDOWS\system32\ctdaught.dat, 10/21/2003 17:47:34, 53932 bytes
Driver: C:\WINDOWS\system32\a3d.dll, 80.00.0000.0003 (English), 10/6/2003 14:38:06, 65536 bytes
Driver: C:\WINDOWS\system32\commonfx.dll, 5.12.0001.0440 (English), 10/6/2003 14:44:28, 114688 bytes
Driver: C:\WINDOWS\system32\ctaudfx.dll, 5.12.0001.0440 (English), 10/6/2003 14:44:58, 581632 bytes
Driver: C:\WINDOWS\system32\ctsblfx.dll, 5.12.0001.0440 (English), 10/6/2003 14:46:14, 606208 bytes
Driver: C:\WINDOWS\system32\sfman32.dll, 5.12.0001.0130 (English), 8/17/2001 14:35:46, 36864 bytes
Driver: C:\WINDOWS\system32\ctbas2w.dat, 10/21/2003 17:54:48, 140643 bytes
Driver: C:\WINDOWS\system32\ctsbas2w.dat, 10/21/2003 17:54:42, 264466 bytes
Driver: C:\WINDOWS\system32\SBAudigy.ico, 8/17/2001 12:42:28, 7406 bytes
Driver: C:\WINDOWS\system32\Audigy.bmp, 11/13/2001 09:48:20, 1912 bytes
Driver: C:\WINDOWS\system32\ctcoinst.dll, 3.00.0000.0004 (English), 10/6/2003 14:48:30, 69632 bytes
Driver: C:\WINDOWS\system32\ctdvinst.dll, 0.00.0000.0008 (English), 10/6/2003 14:48:42, 143360 bytes
Driver: C:\WINDOWS\system32\drivers\ctdvda2k.sys, 5.13.0001.0413 (English), 10/14/2003 11:17:56, 332800 bytes
-
Name: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_104C&DEV_8024&SUBSYS_10001458&REV_00\4&20E0FF6A&0&38F0
Driver: C:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 61056 bytes
Driver: C:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 53248 bytes
Driver: C:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 61824 bytes
Driver: C:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/5/2004 00:00:00, 60800 bytes
Driver: C:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/18/2001 01:46:40, 6400 bytes
Name: Radeon X1950 Pro Secondary
Device ID: PCI\VEN_1002&DEV_72A0&SUBSYS_2205148C&REV_00\4&2CCDD017&0&0108
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6715 (English), 7/28/2007 15:30:27, 2371584 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ati2erec.dll, 1.00.0000.0012 (English), 7/28/2007 14:45:37, 49152 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativvpxx.vp, 7/28/2007 17:44:06, 45296 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativckxx.vp, 5/31/2007 04:43:05, 2096 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativcaxx.vp, 4/19/2007 00:19:24, 929 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativcaxx.cpa, 4/19/2007 00:19:24, 1311202 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativdkxx.vp, 4/19/2007 00:19:50, 2096 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6715 (English), 7/28/2007 15:30:45, 269312 bytes
Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0348 (English), 7/28/2007 14:40:25, 450560 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2495 (English), 7/28/2007 15:22:58, 26112 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0517 (English), 7/28/2007 15:12:20, 3067712 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0010.0163 (English), 7/28/2007 15:01:37, 1550208 bytes
Driver: C:\WINDOWS\system32\atiicdxx.dat, 6/13/2007 05:30:03, 151367 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dat, 11/22/2006 15:07:58, 3107788 bytes
Driver: C:\WINDOWS\system32\ativva5x.dat, 7/28/2007 15:01:18, 3107788 bytes
Driver: C:\WINDOWS\system32\ativva6x.dat, 7/28/2007 15:01:18, 972072 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0008 (English), 7/28/2007 15:20:27, 53248 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4200 (English), 7/28/2007 14:46:19, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/10/2001 04:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4174 (English), 7/28/2007 15:21:16, 483328 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4163 (English), 7/28/2007 15:22:38, 118784 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2522 (English), 7/28/2007 15:23:18, 143360 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0021 (English), 7/28/2007 15:23:06, 122880 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2512 (English), 7/28/2007 15:22:51, 43520 bytes
Driver: C:\WINDOWS\system32\atikvmag.dll, 6.14.0010.0062 (English), 7/28/2007 14:47:54, 266240 bytes
Driver: C:\WINDOWS\system32\atifglpf.xml, 4/12/2007 13:33:47, 7069 bytes
Driver: C:\WINDOWS\system32\ATIDEMGX.dll, 2.00.2764.40555 (English), 7/28/2007 15:31:51, 344064 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.6747 (English), 7/28/2007 14:50:53, 5435392 bytes
Driver: C:\WINDOWS\system32\atiok3x2.dll, 6.14.0010.0001 (English), 7/28/2007 15:06:32, 176128 bytes
Driver: C:\WINDOWS\system32\atioglx2.dll, 6.14.0010.6747 (English), 7/28/2007 15:37:07, 8237056 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4005 (English), 7/28/2007 15:24:50, 307200 bytes
Driver: C:\WINDOWS\atiogl.xml, 5/4/2007 05:52:52, 11557 bytes
Name: Radeon X1950 Pro
Device ID: PCI\VEN_1002&DEV_7280&SUBSYS_2204148C&REV_00\4&2CCDD017&0&0008
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6715 (English), 7/28/2007 15:30:27, 2371584 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ati2erec.dll, 1.00.0000.0012 (English), 7/28/2007 14:45:37, 49152 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativvpxx.vp, 7/28/2007 17:44:06, 45296 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativckxx.vp, 5/31/2007 04:43:05, 2096 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativcaxx.vp, 4/19/2007 00:19:24, 929 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativcaxx.cpa, 4/19/2007 00:19:24, 1311202 bytes
Driver: C:\WINDOWS\system32\DRIVERS\ativdkxx.vp, 4/19/2007 00:19:50, 2096 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6715 (English), 7/28/2007 15:30:45, 269312 bytes
Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0348 (English), 7/28/2007 14:40:25, 450560 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2495 (English), 7/28/2007 15:22:58, 26112 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0517 (English), 7/28/2007 15:12:20, 3067712 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0010.0163 (English), 7/28/2007 15:01:37, 1550208 bytes
Driver: C:\WINDOWS\system32\atiicdxx.dat, 6/13/2007 05:30:03, 151367 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dat, 11/22/2006 15:07:58, 3107788 bytes
Driver: C:\WINDOWS\system32\ativva5x.dat, 7/28/2007 15:01:18, 3107788 bytes
Driver: C:\WINDOWS\system32\ativva6x.dat, 7/28/2007 15:01:18, 972072 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0008 (English), 7/28/2007 15:20:27, 53248 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4200 (English), 7/28/2007 14:46:19, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/10/2001 04:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4174 (English), 7/28/2007 15:21:16, 483328 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4163 (English), 7/28/2007 15:22:38, 118784 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2522 (English), 7/28/2007 15:23:18, 143360 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0021 (English), 7/28/2007 15:23:06, 122880 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2512 (English), 7/28/2007 15:22:51, 43520 bytes
Driver: C:\WINDOWS\system32\atikvmag.dll, 6.14.0010.0062 (English), 7/28/2007 14:47:54, 266240 bytes
Driver: C:\WINDOWS\system32\atifglpf.xml, 4/12/2007 13:33:47, 7069 bytes
Driver: C:\WINDOWS\system32\ATIDEMGX.dll, 2.00.2764.40555 (English), 7/28/2007 15:31:51, 344064 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.6747 (English), 7/28/2007 14:50:53, 5435392 bytes
Driver: C:\WINDOWS\system32\atiok3x2.dll, 6.14.0010.0001 (English), 7/28/2007 15:06:32, 176128 bytes
Driver: C:\WINDOWS\system32\atioglx2.dll, 6.14.0010.6747 (English), 7/28/2007 15:37:07, 8237056 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4005 (English), 7/28/2007 15:24:50, 307200 bytes
Driver: C:\WINDOWS\atiogl.xml, 5/4/2007 05:52:52, 11557 bytes
-
RAM timings are:
400Mhz:
CAS latency 5.0
RAS to CAS 5
RAS prcharge 5
tRAS 18
2x1 Gig sticks in Dual Channel.
Im starting to think my power supply doesn't cut it. It says 400, but i know its a cheapy power supply and that is an optimistic 400...
-
Originally posted by Spatula
RAM timings are:
400Mhz:
CAS latency 5.0
RAS to CAS 5
RAS prcharge 5
tRAS 18
2x1 Gig sticks in Dual Channel.
Im starting to think my power supply doesn't cut it. It says 400, but i know its a cheapy power supply and that is an optimistic 400...
I thought a 1950 needed 450+?
-
guy at the shop said 400 should be ok. Perhaps a really good qaulity 400.
-
Just for grins check the system log in Event Viewer in Administrative Tools.
-
In DXDiag, when you hit the "DRIVER" lines you can skip those.
Out of curiousity, what is the brand of the PSU?
I'd be wary of a poor brand. If your mobo came with a hardware monitor, run it. Check the voltages periodically. Look for low voltages or eratic graphs (if it has a graph output).
I'm curious where those cheap-o allendale chips (E4000's) rank vs Conroes (E6000's) and AMD chips. Anybody know if we're talking Celerons here, or what?
-
I had a similar freeze problem when I installed my GS7800 in my AMD opteron system. I had to uncheck 'optimize objects' just to get Aces to run. Once that was fixed, I started noticing 2-3 system freezes, mostly while I was browsing online. I'd take a look at your video drivers for the freezing problem
Mine turned out to be a compatability problem between the vid card and the AMD cpu/mtb. Card worked fine on my intel system. If you still have your old vid card, you might try runing with it for a time to see if the freezing goes away. Trying a different driver might help also... You might consider trying an older vid driver too.
On the power supply, what is the max amps available on the 12V legs. Many new vid cards require a power supply to have at least 20amps available. Depending on what else you're running in your system, a 400W P/S might work ok, as long as it can supply the needed amps. Find out what amps the P/S supplies and check with the vid card company to see what is required for their card to work properly. Not having enough amps can cause weird problems... like freezing.
Wabbit
Morals & Manners Officer
Whitey's Buccaneers
5th Army Air Corps
-
Make sure your DDR voltage setting is correct in the BIOS. Some memories get wrongly detected in BIOS and run at under-spec voltage. This will cause random problems.
I had a similar problem after upgrading my ram but luckily I knew my new overclocking ram required higher than normal voltage to run and saw the BIOS detected the settings wrong. Haven't had a single hiccup since that.
And no I don't overclock, I got the ram to have some room for upgrades.
-
Originally posted by Krusty
I'm curious where those cheap-o allendale chips (E4000's) rank vs Conroes (E6000's) and AMD chips. Anybody know if we're talking Celerons here, or what?
4500 is a conroe.
-
Originally posted by wabbit
I had a similar freeze problem when I installed my GS7800 in my AMD opteron system. I had to uncheck 'optimize objects' just to get Aces to run. Once that was fixed, I started noticing 2-3 system freezes, mostly while I was browsing online. I'd take a look at your video drivers for the freezing problem
Yer, i think i will if i think the power supply isnt the problem.
Originally posted by wabbit
If you still have your old vid card, you might try runing with it for a time to see if the freezing goes away.
Can't, my old video card was AGP. New one is PCI-E otherwise i would have just kept my x800pro.
Originally posted by wabbit
On the power supply, what is the max amps available on the 12V legs. Many new vid cards require a power supply to have at least 20amps available. Depending on what else you're running in your system, a 400W P/S might work ok, as long as it can supply the needed amps. Find out what amps the P/S supplies and check with the vid card company to see what is required for their card to work properly. Not having enough amps can cause weird problems... like freezing.
Yer, i think its a pretty crappy power supply and im getting more convinced its the problem.
-
Right going to pull apart the case and find out more about the power supply unit...
-
Here's a pic of my power supply:
(http://www.my2cents.co.nz/taurineman/ps.jpg)
-
15amps on the 12v is rather low. I suspect, that if you call your vid card company, they'll say it's too low for that card. I think yer right in thinking it's the P/S, but call your vid card company just to be sure...
Wabbit
Morals & Manners Officer
Whitey's Buccaneers
5th Army Air Corps
-
I've installed the NGO 1.7.2 drivers and that improved my frame rates around 30% - so im happy(ish) with the framerates now. Im getting 55 FPS on average and as low as 35-40 and high as 70-75.
The lockup issue can be reproduced easy by starting iTunes. Locks solid before we get to the GUI. Browsing the web and using explorer seems a little more stable now too.
-
FYI, i think i've got to the bottom of my instabilities.
I installed the NGO 1.7.2 drivers after trying the 1.7.3s with some issues. The NGO drivers have boosted my framerates about 30% and made the instabilities that i had been seeing in explorer and firefox dissapear.
But i still get these wierd solid lock-ups when starting itunes with the ipod connected. I tried lots of things including upgrading to an AcBel E2 470Watt power supply and nothing has worked in getting iTunes going. Everything else seems good now and getting 65-75 FPS in game and no micropauses.
My fix for the iTunes issue, was to uninstall it, and use WinAmp - it integrates perfectly with my ipod and is much better than iTunes.
So, im all sorted now :)
-
If you have iAnything installed in your computer you can only blame yourself for instabilities.
Did you try to boost the memory voltage already?
-
Originally posted by MrRiplEy[H]
If you have iAnything installed in your computer you can only blame yourself for instabilities.
Did you try to boost the memory voltage already?
Nah, not yet - might try.
-
1st,
your PS isnt worth keeping. You need 18@'s on your 12V rail. I think most people go overboard on PS's...but you do need to be prudent. 15@'s just is cutting it to close. I'd all but gaurantee the PS is contributing to the problems...given the investment in new "stuff" its not worth the risk. You dont need much more 18@'s on the 12V rail is fine. Most of the good reasonable PS's now have 20@'s on the 1st 12V and 18@ on the second. 16@'s is the bare minimum. As an example I have a 350W PS with 22@'s on my 12V rail (is driving my sons box). It's the usable wattage not the total. Your current PS has way to much unused pop in the 3.3 & 5 volt rails, which is typical...
-
Originally posted by humble
1st,
your PS isnt worth keeping. You need 18@'s on your 12V rail. I think most people go overboard on PS's...but you do need to be prudent. 15@'s just is cutting it to close. I'd all but gaurantee the PS is contributing to the problems...given the investment in new "stuff" its not worth the risk. You dont need much more 18@'s on the 12V rail is fine. Most of the good reasonable PS's now have 20@'s on the 1st 12V and 18@ on the second. 16@'s is the bare minimum. As an example I have a 350W PS with 22@'s on my 12V rail (is driving my sons box). It's the usable wattage not the total. Your current PS has way to much unused pop in the 3.3 & 5 volt rails, which is typical...
I've replaced the PSU with an AcBel E2 470Watt supply w/ 2 x 12v Rails with 18Amps each. Hasn't really made any noticable difference. But its in there now and is much better than my old generic no-name POS supply and i can now rule out the PSU as a cause of anything.
-
E4500 may be "Core 2 Duo" but it's not "conroe" - it's the lower-end Allendale core.
For example:
http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=2+50001157+40000343+1050722265+1051707842&Configurator=&Subcategory=343&description=&Ntk=&srchInDesc= (let's see if that shows up properly)
Hold the phone! Winamp works with ipods?!?!? WTF didn't somebody tell me 2 months ago before I installed itunes?!?!? :lol
How?
-
My BIOS doesnt seem to have options for upping the voltage to the RAM :(
-
Originally posted by Krusty
E4500 may be "Core 2 Duo" but it's not "conroe" - it's the lower-end Allendale core.
Yer, i found that out. One of my diagnostic tools calls it a conroe, the other called it an Allendale. How much boost will a conroe give me over an allendale? Not that i really need it at the moment, i get good framerates as is.
Originally posted by Krusty
Hold the phone! Winamp works with ipods?!?!? WTF didn't somebody tell me 2 months ago before I installed itunes?!?!? :lol
How?
Yup, just worked out of the box. Just uninstall all traces of itunes, and associated apps like applemobiledevice thingy and apple update etc. Double-check all services and startup registry entries are deleted.
You can copy 2-way to and from the ipod. I wiped my ipod and re-loaded all the tracks from the WinAmp library.
-
I don't know benchmarks for sure, but my impression is that allendales are like celerons: cheaper to make and stripped down, using the same technology but with less performance. I could be wrong, but they are the "lower end" and will have lower performance.
-
I had probs with my radeon 1950 pro as well. I dont know if this issue has been fixed by the maker, but there might be two chips on the card which get extremely hot, like 260F°.
I dont find a good picture right now. But they are fairly easy to locate, if they are on your card, still.
The are opposite to the monitor plug, on the same plane as the cooling assembly. Open the case and look for two small (roughly 1x0,5"), black bricks which are so hot you cannot touch them when running a 3d application.
My fix was to get small passive RAM coolers and glue them to the aforementioned small black bricks with some heat conducting glue (arctic cooling for example. [edit] not to be confused with thermal grease!). Plus I put a 40mm low noise fan next to the coolers to blow the warm waste-air of the gfx card away from them.
No issues since.
Best regards,
Matt
-
We've tried the Dual Core Windows XP Patch already, right?
Allendales are very good CPUs. Very good price/performance ratio. They may be cheaper, but these aren't your old Celerons. They out bench some Athlon X2's depending on which Allendale you have. They are definantly faster than the Older P4 Smithfield and Presler cores. Single core Prescott's that are 3.6ghz are still out benched by the Allendale.
Oh, and they overclock very well.
-
Yer, i applied both the patches and followed skuzzy's advice in the posts in the Technical Support board. That fixed the spinning clipboard issues etc.
Now my system is solid as a rock. Performance in AH2 is more than adequate, so im happy. One day i may upgrade to a E6XXX conroe, but no real need to do so now.