PDA

View Full Version : Problems with GF3 Ti 200 64mb


livez
08-20-03, 12:34 PM
I recently formatted my computer (Thunderbird 1Ghz), and had to go through the tedious work of patching all hardware etc up-to-date. My graphics card is a Nvidia Geforce Ti 200.

My problem is, whenever I do something that requires advanced graphics, my computer reboots after a few minutes!When I get back to windows I get an error message that goes along the lines" a driver made an exceptional error" or something like that.

At first I thought it might have something to do whith the game, or with the new detonator that recently came out, but Ive tried alot of games and earlier versions of detonator, with the same results. Ive also formatted my computer once more, and done it all over again, but the problem remains. Does anyone have a clue what I should do?

Directx:9b
Vcard driver: 6.14.10.4403
Bios version: 30.20.00.20.03

BlueScreen
08-20-03, 02:24 PM
hi!

first, did you had this problem before formating?
if yes then i suspect your power supply to dont be enough powerfull for your computer. else try the 30 to 40 driver cause the newer one are optimise for the gf4 and fx and will not change anything on your gf3. i can send them to you if you want.

thats all i can think for now.

livez
08-20-03, 02:35 PM
Hello BlueScreen!

No I didnt have the problem before I formated. After it first didnt work out with the latest detonator release, I formated again and installed the same detonator release I had before I formated the first time, and I still have the same problem. One difference I can think of between before and after formation, I didnt have Windows XP service pack 1 installed before, but I did so after. I wonder if that can have something to do with it.

BlueScreen
08-20-03, 11:49 PM
hi!

i dont think installing the service pack after can cause this problem. can you get the exact error message. i think you can get the name of the driver file that cause this error (i just think cause i dont use winXP). maybe its something else than the video card. if you can't get the device thats cause the problem i suggest to reformat the whole thing and rip as much peripheral of your case (should only remain cpu, mobo, ram, vid card and hard disk) and try to see if you get the same problem. if not try reinstalling them one by one to see wich is in problem and then try to get a working driver for this one.

livez
08-21-03, 03:20 AM
this is the complete error message:

1)

The computer has been recovered after a serious error

For more information click here

2)

BCcode: 9c
PCP1: 00000002
PCP2: 805366F0
PCP3: F6002000
PCP4: 0000017A
OS_ver: 5_1_2600
SP: 1_0
Product: 256_1

For more technical info click here

3)

Following files are in the error report

C:\Windows\Minidump\mini082103-01.dump
C:\docume~1\mange\lokala~1\temp\Wer1.tmp.dir00\sys data.xml

BlueScreen
08-21-03, 11:46 AM
ive found on the microsoft website how to read the minidump that should contain the information on whats wrong. its in C:\Windows\Minidump\mini082103-01.dump. it look a bit complex to do but im sure you can do it. here is the url:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315263

if you can get to decrypting the file post back with the content of it so we can check whats wrong.
i dont use winXP/2000 so i cant test this myself.

livez
08-21-03, 12:42 PM
I tried that debugging thing, and to be honest I failed miserably. Ill try again when Ive gotten my strength back ;)

BlueScreen
08-21-03, 02:43 PM
ok ill try something. the minidump filesize should be 64k so you can attach it to a reply. you will have to rename the .dump extension to something valid (gif, jpg, png, txt, zip...) to be able to attach it. my computer need formating so i will install winXP and download your dump file and try the debugger hopping it will work. btw wich version of winXP do you have? pro or home?

livez
08-21-03, 03:40 PM
I have WinXP PRO

Thx for your help man, I really appreciate it.

BlueScreen
08-21-03, 04:05 PM
ive found another place where they explain how to read dump files in a much easier way here: http://x220.minasi.com/forum/topic.asp?TOPIC_ID=3026
let me know if it work.

BlueScreen
08-22-03, 12:45 AM
i installed win2000 in my comp and tried the debugger.
here's what ive been able to get from him:

C:\Program Files\Debugging Tools for Windows>kd -y SRV*c:\symbols*http://msdl.mi
crosoft.com/download/symbols -i g:\i386 -z e:\mini082103-01.dump

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


Loading Dump File [e:\mini082103-01.dump]
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: g:\i386
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Thu Aug 21 04:07:12 2003
System Uptime: 0 days 0:34:33.878
Loading Kernel Symbols
.................................................. ..............................
..............................
Loading unloaded module list
.........
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {2, 805366f0, f6002000, 17a}

Probably caused by : Machine_Check

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

kd> !analyze -show
Unknown bugcheck code (10000)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA
.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing M
CA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing I
NIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing
INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
Arguments:
Arg1: 00000002
Arg2: 805366f0
Arg3: f6002000
Arg4: 0000017a

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


BUGCHECK_STR: 0x9C_IA32_AuthenticAMD

MODULE_NAME: Machine_Check

IMAGE_NAME: Machine_Check

DEBUG_FLR_IMAGE_TIMESTAMP: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 806aed8f to 804f4103

STACK_TEXT:
805366c8 806aed8f 0000009c 00000002 805366f0 nt!KeBugCheckEx+0x19
805367f4 806abc3e 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdb


FOLLOWUP_NAME: MachineOwner

STACK_COMMAND: kb

BUCKET_ID: 0x9C_IA32_AuthenticAMD

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

kd> !drivers
System Driver and Image Summary
Base Code Size Data Size Image Name Creation Time
804d4000 0 ( 0 k) 0 ( 0 k) ntoskrnl.exe Thu Apr 24 11:57:43 2003
806ab000 0 ( 0 k) 0 ( 0 k) hal.dll Thu Aug 29 04:05:02 2002
f9f32000 0 ( 0 k) 0 ( 0 k) kdcom.dll Fri Aug 17 16:49:10 2001
f9e42000 0 ( 0 k) 0 ( 0 k) BOOTVID.dll Fri Aug 17 16:49:09 2001
f99e5000 0 ( 0 k) 0 ( 0 k) ACPI.sys Thu Aug 29 04:09:03 2002
f9f34000 0 ( 0 k) 0 ( 0 k) WMILIB.SYS Fri Aug 17 17:07:23 2001
f9a32000 0 ( 0 k) 0 ( 0 k) pci.sys Thu Aug 29 04:09:10 2002
f9a42000 0 ( 0 k) 0 ( 0 k) isapnp.sys Fri Aug 17 16:58:01 2001
f9f36000 0 ( 0 k) 0 ( 0 k) viaide.sys Thu Aug 29 04:27:48 2002
f9cb2000 0 ( 0 k) 0 ( 0 k) PCIIDEX.SYS Thu Aug 29 04:27:47 2002
f9a52000 0 ( 0 k) 0 ( 0 k) MountMgr.sys Fri Aug 17 16:47:36 2001
f99c6000 0 ( 0 k) 0 ( 0 k) ftdisk.sys Fri Aug 17 16:52:41 2001
f9f38000 0 ( 0 k) 0 ( 0 k) dmload.sys unavailable
f99a2000 0 ( 0 k) 0 ( 0 k) dmio.sys Fri Aug 17 16:58:27 2001
f9cba000 0 ( 0 k) 0 ( 0 k) PartMgr.sys Fri Aug 17 21:32:23 2001
f9a62000 0 ( 0 k) 0 ( 0 k) VolSnap.sys Fri Aug 17 16:53:19 2001
f998c000 0 ( 0 k) 0 ( 0 k) atapi.sys Thu Aug 29 04:27:48 2002
f9a72000 0 ( 0 k) 0 ( 0 k) ultra.sys Fri Aug 17 16:52:19 2001
f9975000 0 ( 0 k) 0 ( 0 k) SCSIPORT.SYS Thu Aug 29 04:27:47 2002
f9a82000 0 ( 0 k) 0 ( 0 k) disk.sys Thu Aug 29 04:27:56 2002
f9a92000 0 ( 0 k) 0 ( 0 k) CLASSPNP.SYS Thu Aug 29 05:08:42 2002
f9964000 0 ( 0 k) 0 ( 0 k) sr.sys Thu Aug 29 04:17:56 2002
f9950000 0 ( 0 k) 0 ( 0 k) KSecDD.sys Fri Aug 17 16:50:01 2001
f98c6000 0 ( 0 k) 0 ( 0 k) Ntfs.sys Thu Aug 29 05:13:37 2002
f989d000 0 ( 0 k) 0 ( 0 k) NDIS.sys Thu Aug 29 05:09:23 2002
f9cc2000 0 ( 0 k) 0 ( 0 k) viaagp.sys Fri Aug 17 16:58:00 2001
f9883000 0 ( 0 k) 0 ( 0 k) Mup.sys Thu Aug 29 05:12:53 2002
f9b72000 0 ( 0 k) 0 ( 0 k) processr.sys Thu Aug 29 04:05:03 2002
f9709000 0 ( 0 k) 0 ( 0 k) nv4_mini.sys Fri May 02 18:55:13 2003
f96f7000 0 ( 0 k) 0 ( 0 k) VIDEOPRT.SYS Thu Aug 29 04:32:03 2002
f9d0a000 0 ( 0 k) 0 ( 0 k) fdc.sys unavailable
f96e4000 0 ( 0 k) 0 ( 0 k) parport.sys Thu Aug 29 04:27:29 2002
f9b92000 0 ( 0 k) 0 ( 0 k) serial.sys Thu Aug 29 05:08:27 2002
f9efa000 0 ( 0 k) 0 ( 0 k) serenum.sys Fri Aug 17 16:50:13 2001
f9ba2000 0 ( 0 k) 0 ( 0 k) i8042prt.sys Thu Aug 29 05:06:37 2002
f9d12000 0 ( 0 k) 0 ( 0 k) kbdclass.sys Thu Aug 29 04:26:59 2002
f9bb2000 0 ( 0 k) 0 ( 0 k) cdrom.sys Thu Aug 29 04:27:55 2002
f9bc2000 0 ( 0 k) 0 ( 0 k) redbook.sys Thu Aug 29 04:27:45 2002
f96c4000 0 ( 0 k) 0 ( 0 k) ks.sys Wed Dec 04 12:09:38 2002
f9bd2000 0 ( 0 k) 0 ( 0 k) Imapi.SYS Thu Aug 29 04:28:05 2002
f9d1a000 0 ( 0 k) 0 ( 0 k) usbuhci.sys Thu Aug 29 04:32:48 2002
f96a2000 0 ( 0 k) 0 ( 0 k) USBPORT.SYS Thu Aug 29 04:32:49 2002
f9d22000 0 ( 0 k) 0 ( 0 k) DM9PCI5.SYS Fri Mar 02 03:56:34 2001
f965c000 0 ( 0 k) 0 ( 0 k) emu10k1m.sys Fri Aug 03 22:36:34 2001
f963b000 0 ( 0 k) 0 ( 0 k) portcls.sys Thu Aug 29 05:00:58 2002
f9be2000 0 ( 0 k) 0 ( 0 k) drmk.sys Thu Aug 29 04:32:30 2002
f9bf2000 0 ( 0 k) 0 ( 0 k) sfmanm.sys Fri Aug 03 22:36:35 2001
f9f50000 0 ( 0 k) 0 ( 0 k) ctlfacem.sys Fri Aug 03 22:36:32 2001
fa105000 0 ( 0 k) 0 ( 0 k) ctljystk.sys Thu Jul 19 18:28:02 2001
f9f0a000 0 ( 0 k) 0 ( 0 k) gameenum.sys Thu Aug 29 04:32:42 2002
fa106000 0 ( 0 k) 0 ( 0 k) audstub.sys Fri Aug 17 16:59:40 2001
f9c02000 0 ( 0 k) 0 ( 0 k) rasl2tp.sys Thu Aug 29 05:06:36 2002
f9f0e000 0 ( 0 k) 0 ( 0 k) ndistapi.sys Fri Aug 17 16:55:29 2001
f9625000 0 ( 0 k) 0 ( 0 k) ndiswan.sys Thu Aug 29 04:58:38 2002
f9c12000 0 ( 0 k) 0 ( 0 k) raspppoe.sys Fri Aug 17 16:55:33 2001
f9c22000 0 ( 0 k) 0 ( 0 k) raspptp.sys Tue Oct 01 20:52:28 2002
f9f12000 0 ( 0 k) 0 ( 0 k) TDI.SYS Fri Aug 17 16:57:25 2001
f9614000 0 ( 0 k) 0 ( 0 k) psched.sys Thu Aug 29 04:35:54 2002
f9c32000 0 ( 0 k) 0 ( 0 k) msgpc.sys Fri Aug 17 16:54:19 2001
f9d2a000 0 ( 0 k) 0 ( 0 k) ptilink.sys Fri Aug 17 16:49:53 2001
f9d32000 0 ( 0 k) 0 ( 0 k) raspti.sys Fri Aug 17 16:55:32 2001
f9547000 0 ( 0 k) 0 ( 0 k) rdpdr.sys Thu Aug 29 04:06:34 2002
f9c42000 0 ( 0 k) 0 ( 0 k) termdd.sys Thu Aug 29 04:40:32 2002
f9d3a000 0 ( 0 k) 0 ( 0 k) mouclass.sys Thu Aug 29 04:27:00 2002
fa107000 0 ( 0 k) 0 ( 0 k) swenum.sys Wed Dec 04 12:10:07 2002
f94fd000 0 ( 0 k) 0 ( 0 k) update.sys Fri Aug 17 23:53:56 2001
f9c52000 0 ( 0 k) 0 ( 0 k) NDProxy.SYS Fri Aug 17 16:55:30 2001
f9d6a000 0 ( 0 k) 0 ( 0 k) flpydisk.sys unavailable
f9c82000 0 ( 0 k) 0 ( 0 k) usbhub.sys Thu Aug 29 04:32:49 2002
f9f7e000 0 ( 0 k) 0 ( 0 k) USBD.SYS Fri Aug 17 17:02:58 2001
f9f80000 0 ( 0 k) 0 ( 0 k) Fs_Rec.SYS unavailable
fa17b000 0 ( 0 k) 0 ( 0 k) Null.SYS unavailable
f9f82000 0 ( 0 k) 0 ( 0 k) Beep.SYS Fri Aug 17 16:47:33 2001
f9d7a000 0 ( 0 k) 0 ( 0 k) vga.sys Thu Aug 29 04:32:03 2002
f9f84000 0 ( 0 k) 0 ( 0 k) mnmdd.SYS Fri Aug 17 16:57:28 2001
f9f86000 0 ( 0 k) 0 ( 0 k) RDPCDD.sys Fri Aug 17 16:46:56 2001
f9d82000 0 ( 0 k) 0 ( 0 k) Msfs.SYS Fri Aug 17 16:50:02 2001
f9d8a000 0 ( 0 k) 0 ( 0 k) Npfs.SYS Fri Aug 17 16:50:03 2001
f9543000 0 ( 0 k) 0 ( 0 k) rasacd.sys Fri Aug 17 16:55:39 2001
f9c92000 0 ( 0 k) 0 ( 0 k) ipsec.sys Thu Aug 29 05:07:19 2002
f4353000 0 ( 0 k) 0 ( 0 k) tcpip.sys Thu Aug 29 04:58:10 2002
f432c000 0 ( 0 k) 0 ( 0 k) netbt.sys Thu Aug 29 05:01:56 2002
f9ca2000 0 ( 0 k) 0 ( 0 k) netbios.sys Thu Aug 29 04:35:45 2002
f4304000 0 ( 0 k) 0 ( 0 k) rdbss.sys Thu Aug 29 04:58:48 2002
f427c000 0 ( 0 k) 0 ( 0 k) mrxsmb.sys Mon Nov 18 14:27:37 2002
f9ac2000 0 ( 0 k) 0 ( 0 k) Fips.SYS Fri Aug 17 21:31:49 2001
f9ad2000 0 ( 0 k) 0 ( 0 k) wanarp.sys Fri Aug 17 16:55:23 2001
f9ae2000 0 ( 0 k) 0 ( 0 k) Cdfs.SYS Thu Aug 29 04:58:50 2002
f9d9a000 0 ( 0 k) 0 ( 0 k) usbccgp.sys Thu Aug 29 04:32:51 2002
f9b02000 0 ( 0 k) 0 ( 0 k) usbaudio.sys Thu Aug 29 04:32:30 2002
f9843000 0 ( 0 k) 0 ( 0 k) hidusb.sys Fri Aug 17 17:02:16 2001
f9b12000 0 ( 0 k) 0 ( 0 k) HIDCLASS.SYS Thu Aug 29 04:32:40 2002
f9da2000 0 ( 0 k) 0 ( 0 k) HIDPARSE.SYS Fri Aug 17 17:02:04 2001
f983b000 0 ( 0 k) 0 ( 0 k) mouhid.sys Fri Aug 17 16:47:57 2001
f41c6000 0 ( 0 k) 0 ( 0 k) dump_atapi.sys Thu Aug 29 04:27:48 2002
f9f8a000 0 ( 0 k) 0 ( 0 k) dump_WMILIB.SYS Fri Aug 17 17:07:23 2001

bf800000 0 ( 0 k) 0 ( 0 k) win32k.sys Wed Oct 23 12:54:58 2002
f43d5000 0 ( 0 k) 0 ( 0 k) watchdog.sys Thu Aug 29 04:32:20 2002
f43d1000 0 ( 0 k) 0 ( 0 k) Dxapi.sys Fri Aug 17 16:53:19 2001
bff80000 0 ( 0 k) 0 ( 0 k) dxg.sys Mon Sep 09 17:06:54 2002
fa039000 0 ( 0 k) 0 ( 0 k) dxgthk.sys Fri Aug 17 16:53:12 2001
bf99e000 0 ( 0 k) 0 ( 0 k) nv4_disp.dll Fri May 02 18:58:51 2003
f3fa4000 0 ( 0 k) 0 ( 0 k) afd.sys Thu Aug 29 05:01:13 2002
f40b5000 0 ( 0 k) 0 ( 0 k) ndisuio.sys Thu Aug 29 04:35:40 2002
f3e11000 0 ( 0 k) 0 ( 0 k) mrxdav.sys Fri Aug 17 16:50:20 2001
f9faa000 0 ( 0 k) 0 ( 0 k) ParVdm.SYS unavailable
f3cfa000 0 ( 0 k) 0 ( 0 k) srv.sys Fri Mar 28 14:54:53 2003
f9dea000 0 ( 0 k) 0 ( 0 k) secdrv.sys Fri Jan 11 10:39:40 2002
f3ba7000 0 ( 0 k) 0 ( 0 k) wdmaud.sys Thu Aug 29 05:00:46 2002
f3f24000 0 ( 0 k) 0 ( 0 k) sysaudio.sys Thu Aug 29 05:01:17 2002
f3606000 0 ( 0 k) 0 ( 0 k) kmixer.sys Thu Aug 29 04:32:28 2002

Unloaded modules:
f3606000 f362d000 kmixer.sys
f3b5d000 f3b84000 kmixer.sys
fa049000 fa04a000 drmkaud.sys
f3b84000 f3ba7000 aec.sys
f95d4000 f95e1000 DMusic.sys
f3f04000 f3f12000 swmidi.sys
f9fdc000 f9fde000 splitter.sys
f9d72000 f9d77000 Cdaudio.SYS
f9ef6000 f9ef9000 Sfloppy.SYS

Loading User Symbols
************************************************** **************************
* *
* LM [lvukfiptm[pattern]] is the recommended command to list modules. *
* *
************************************************** **************************
kd>

i found this on the microsoft's website:

A machine check exception occurs when Windows XP and your hardware platform cannot recover from some type of hardware error so that the system can continue to run successfully and reliably. More specific diagnosis of machine check exceptions is difficult and there is no general solution.

Machine check exceptions are frequently caused by damaged memory
if you have 2stick of ram i recommand trying to remove all of them but one and see what append for everyone of them

BlueScreen
08-22-03, 12:55 AM
in the dump i put in bold this part:

MACHINE_CHECK_EXCEPTION (9c)
Arguments:
Arg1: 00000002
Arg2: 805366f0
Arg3: f6002000
Arg4: 0000017a

you posted with something like
BCcode: 9c
PCP1: 00000002
PCP2: 805366F0
PCP3: F6002000
PCP4: 0000017A

this is clearly the same thing and prolly the key to solve your problem

in this site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/bccodes_03af.asp
they explain how decode those numbers. i think you have an processor is based on x86 architecture, and has the MCE feature but not the MCA feature so
Parameter Description
1 The low 32 bits of P5_MC_TYPE MSR
2 Reserved
3 The high 32 bits of P5_MC_ADDR MSR
4 The low 32 bits of P5_MC_ADDR MSR

its nice to know that the low 32bits of blabla and bla.... but i just have no idea of what is P5_MC_TYPE MSR and P5_MC_ADDR MSR...
if anyone can explain me what is thi i would really apreciate. try do do some research using those keywords "MACHINE_CHECK_EXCEPTION", "P5_MC_ADDR MSR", "P5_MC_TYPE MSR" maybe you will find something usefull.

ok its 2am for me and i have to wake up at 6am so ill see what i can do tomorow

g'luck

livez
08-22-03, 02:57 AM
Ive never seen stuff like this before, and itīs quite fascinating, though I canīt say I understand that much. Im at that link you gave, Ill see if I find something!

livez
08-22-03, 03:05 AM
It says a bit more about MCA and MCE here.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/appendix/hh/appendix/halmca_1okz.asp

NKVD
08-22-03, 09:28 AM
Never had any problems with mine Ti-200, nice card! All games ran w/o problems.

livez
08-22-03, 09:55 AM
Me neither, for about a year. It was only a few days ago the troubles began.

livez
08-22-03, 10:45 AM
I guess Im gonna have to leave my computer at some store, dont seem to be able to get on top of things, thx for the help yall, especially Bluescreen!

BlueScreen
08-22-03, 11:10 AM
np bro!
when you get your comp back, let me know what the technician did, i want to know what was the problem

livez
08-23-03, 05:48 PM
Hey

I uninstalled detonator, and installed a driver from Creative (My card is a Creative one), and now it seems to work! Though I dont understand why it didnt work with detonator.

BlueScreen
08-23-03, 10:08 PM
hi!

maybe your card had something specific to the creative one so the nVidia drivers dont work. i searched the creative web site for your card and i got a new set of driver right here:
http://files.europe.creative.com/Drivers/Others/2170/4404_Win2K_XP.zip
its the Detonator 44.04 for win2000 and XP. you can try them as you want and if you got problem with them, just do a driver rollback

glad to see your card now work and you didnt had to take it to a computer store!