PDA

View Full Version : Fatal Application Error - Help...


DeSTRoYa
2003-12-16, 07:23 PM
Fatal Application Error

Fatal Error: Corrupted memory block in Engine3d
FILE: c:\dev\2003-11-25\source\Lib\game_engine\mymem.cpp Line 541

---------------

That ^ is the error I keep getting while playing PS. It happens every 2-20 minutes usually. I freeze, sound keeps going (looping) and I can sometimes minimize out of PS to see this message. I have tried so many things in trying to get it to work. Does anyone know how I can fix this?

I could not post MSInfo because it is too large. Also I had to remove many items from the dxdiag. I would have posted this on Planetside's Official Forum but I'm only on the 7 day trial and not a PS Subscriber.

My dxdiag:

------------------
System Information
------------------
Time of this report: 12/16/2003, 16:05:16
Machine name: FESTER-SNOH09U6
Operating System: Windows XP Professional (5.1, Build 2600) (2600.xpclient.010817-1148)
Language: English (Regional Setting: English)
System Manufacturer: NVIDIA
System Model: AWRDACPI
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) XP 2500+, MMX, 3DNow, ~1.8GHz
Memory: 1024MB RAM
Page File: 156MB used, 2818MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0 (4.09.0000.0902)
DX Setup Parameters: Not found
DxDiag Version: 5.03.0000.0900 32bit Unicode

------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: The file ati2dvag.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
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 9600 SERIES (Omega 2.4.96c)
Manufacturer: ATI Technologies Inc. (Omega 2.4.96c)
Chip type: RADEON 9600 Series AGP (0x4150)
DAC type: Internal DAC(500MHz)
Device Key: Enum\PCI\VEN_1002&DEV_4150&SUBSYS_00021002&REV_00
Display Memory: 128.0 MB
Current Mode: 1024 x 768 (32 bit) (75Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6396 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 9/30/2003 18:29:58, 374784 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 11/6/2003 13:32:56, 618496 bytes
Device Identifier: {D7B71EE2-0210-11CF-4E6B-0820A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x4150
SubSys ID: 0x00021002
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=DeinterlaceTech_BOBVerticalStretch
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=DeinterlaceTech_BOBVerticalStretch
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=DeinterlaceTech_BOBVerticalStretch
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=DeinterlaceTech_BOBVerticalStretch
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 2 Audio [D000]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_10071102&REV_04
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, 192000
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 2 Audio [D000]
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 2 DirectMusic Synthesizer [D000], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
MPU-401, Hardware (Kernel Mode), Input, No DLS, External
MPU-401, Hardware (Kernel Mode), Output, No DLS, External
SB Audigy 2 Audio [D000], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 Synth A [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
MPU-401 [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
SB Audigy 2 Sw Synth [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 Synth B [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 MIDI IO [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
MPU-401 [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
SB Audigy 2 MIDI IO [D000] [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
Registry: OK
Test Result: Not run

----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.0000.0900)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.0000.0900)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.0000.0900)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.0000.0900)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.0000.0900)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.0000.0900)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.0000.0900)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.0000.0900)

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: Network Bridge - 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

DeSTRoYa
2003-12-16, 07:24 PM
--------------
System Devices
--------------
Name: Creative Game Port
Device ID: PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_04\4&3B1D9AB8&0&2940
Driver: C:\WINDOWS\system32\drivers\gameenum.sys, 5.01.2600.0000 (English), 8/17/2001 14:02:32, 9728 bytes

Name: OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_04\4&3B1D9AB8&0&2A40
Driver: C:\WINDOWS\System32\DRIVERS\ohci1394.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 55424 bytes
Driver: C:\WINDOWS\System32\DRIVERS\1394bus.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 49536 bytes
Driver: C:\WINDOWS\System32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/17/2001 13:46:40, 6400 bytes
Driver: C:\WINDOWS\System32\DRIVERS\nic1394.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 56960 bytes
Driver: C:\WINDOWS\System32\DRIVERS\arp1394.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 54016 bytes

Name: Creative SB Audigy 2 (WDM)
Device ID: PCI\VEN_1102&DEV_0004&SUBSYS_10071102&REV_04\4&3B1D9AB8&0&2840
Driver: C:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.0000 (English), 8/17/2001 14:01:20, 57344 bytes
Driver: C:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.0000 (English), 8/17/2001 22:24:38, 135040 bytes
Driver: C:\WINDOWS\system32\drivers\stream.sys, 5.03.0000.0900 (English), 12/12/2002 00:14:32, 45696 bytes
Driver: C:\WINDOWS\System32\wdmaud.drv, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 22016 bytes
Driver: C:\WINDOWS\System32\ksuser.dll, 5.03.0000.0900 (English), 12/12/2002 00:14:32, 4096 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: NVIDIA nForce2 Memory Controller
Device ID: PCI\VEN_10DE&DEV_01EF&SUBSYS_0C1710DE&REV_C1\3&13C0B0C5&0&05
Driver: n/a

Name: NVIDIA nForce2 Memory Controller
Device ID: PCI\VEN_10DE&DEV_01EE&SUBSYS_0C1710DE&REV_C1\3&13C0B0C5&0&02
Driver: n/a

Name: NVIDIA nForce2 Memory Controller
Device ID: PCI\VEN_10DE&DEV_01ED&SUBSYS_0C1710DE&REV_C1\3&13C0B0C5&0&03
Driver: n/a

Name: NVIDIA nForce2 Memory Controller
Device ID: PCI\VEN_10DE&DEV_01EC&SUBSYS_0C1710DE&REV_C1\3&13C0B0C5&0&04
Driver: n/a

Name: NVIDIA nForce2 Memory Controller
Device ID: PCI\VEN_10DE&DEV_01EB&SUBSYS_0C1710DE&REV_C1\3&13C0B0C5&0&01
Driver: n/a

Name: NVIDIA nForce2 AGP Host to PCI Bridge
Device ID: PCI\VEN_10DE&DEV_01E8&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&F0
Driver: C:\WINDOWS\System32\DRIVERS\nv_agp.SYS, 4.12.0001.0334 (English), 3/18/2003 23:51:00, 18688 bytes
Driver: C:\WINDOWS\System32\nvugart.exe, 1.00.0000.0030 (English), 3/18/2003 23:51:00, 114688 bytes
Driver: C:\WINDOWS\System32\nvgart.nvu, 3/18/2003 23:51:00, 819 bytes

Name: PCI standard host CPU bridge
Device ID: PCI\VEN_10DE&DEV_01E0&SUBSYS_00000000&REV_C1\3&13C0B0C5&0&00
Driver: n/a

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_10DE&DEV_006C&SUBSYS_00000000&REV_A3\3&13C0B0C5&0&40
Driver: C:\WINDOWS\System32\DRIVERS\pci.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 62464 bytes

Name: Universal Serial Bus (USB) Controller
Device ID: PCI\VEN_10DE&DEV_0068&SUBSYS_0C1110DE&REV_A4\3&13C0B0C5&0&12
Driver: n/a

Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN_10DE&DEV_0067&SUBSYS_0C1110DE&REV_A4\3&13C0B0C5&0&11
Driver: C:\WINDOWS\system32\drivers\usbohci.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 15616 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 123264 bytes
Driver: C:\WINDOWS\System32\usbui.dll, 5.01.2600.0000 (English), 8/17/2001 22:36:34, 67072 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 50688 bytes

Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN_10DE&DEV_0067&SUBSYS_0C1110DE&REV_A4\3&13C0B0C5&0&10
Driver: C:\WINDOWS\system32\drivers\usbohci.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 15616 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 123264 bytes
Driver: C:\WINDOWS\System32\usbui.dll, 5.01.2600.0000 (English), 8/17/2001 22:36:34, 67072 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 50688 bytes

Name: NVIDIA nForce MCP Networking Controller
Device ID: PCI\VEN_10DE&DEV_0066&SUBSYS_0C1110DE&REV_A1\3&13C0B0C5&0&20
Driver: C:\WINDOWS\System32\DRIVERS\NVENET.sys, 4.14.0001.0313 (English), 11/27/2002 03:52:00, 80896 bytes
Driver: C:\WINDOWS\System32\DRIVERS\jedih2rx.bin, 11/27/2002 03:52:00, 1024 bytes
Driver: C:\WINDOWS\System32\DRIVERS\ramsed.bin, 11/27/2002 03:52:00, 122 bytes
Driver: C:\WINDOWS\System32\DRIVERS\jedireg.pat, 11/27/2002 03:52:00, 42 bytes

Name: NVIDIA NForce MCP2 IDE Controller
Device ID: PCI\VEN_10DE&DEV_0065&SUBSYS_05B210DE&REV_A2\3&13C0B0C5&0&48
Driver: C:\WINDOWS\System32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Driver: C:\WINDOWS\System32\DRIVERS\pciidex.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:50, 23680 bytes
Driver: C:\WINDOWS\System32\DRIVERS\atapi.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:56, 86656 bytes

Name: NVIDIA nForce PCI System Management
Device ID: PCI\VEN_10DE&DEV_0064&SUBSYS_0C1110DE&REV_A2\3&13C0B0C5&0&09
Driver: n/a

Name: PCI standard ISA bridge
Device ID: PCI\VEN_10DE&DEV_0060&SUBSYS_00000000&REV_A4\3&13C0B0C5&0&08
Driver: C:\WINDOWS\System32\DRIVERS\isapnp.sys, 5.01.2600.0000 (English), 8/23/2001 12:00:00, 35840 bytes

Name: RADEON 9600 SERIES - Secondary (Omega 2.4.96c)
Device ID: PCI\VEN_1002&DEV_4170&SUBSYS_00031002&REV_00\4&102AC5BC&0&01F0
Driver: n/a

Name: RADEON 9600 SERIES (Omega 2.4.96c)
Device ID: PCI\VEN_1002&DEV_4150&SUBSYS_00021002&REV_00\4&102AC5BC&0&00F0
Driver: n/a

Rbstr
2003-12-16, 08:40 PM
Wow we have never had someone post thins mush info, DL the newest Catalyst's the 3.9's i think. Do a full scan if that doen't help, then download and reinstal DX9, tehn if that doen't work reinstall PS all together. And if that doen't work I don't know what else to do, pehaps call PS tech suport, they may have had other people call with this problem.

dscytherulez
2003-12-16, 08:43 PM
Someone posted this on Dicepoint a while ago...they said they fixed it by running PS and doing a full scan as Rbstr suggested.

TheRagingGerbil
2003-12-17, 09:44 AM
Start the PS Launcher and enter your password. Don't press the play button.

Open your planetside directory and look for the file in the error message.

Delete the file then run a full scan.

DeSTRoYa
2003-12-17, 10:42 AM
Yeah...I've tried all that...and more.

Thanks guys.

Any more suggestions?

Rbstr
2003-12-17, 02:57 PM
On second look you may have a bad memory modual someware, something similar happened to me about a year ago were windows would crash to to a corupted memory alocation or something like that, tunrs out my stick of memory had a bad chip and thats why it was crashing. i don't know if you can fix it tough without getting new stick of memory

DeSTRoYa
2003-12-17, 03:00 PM
Would I be able to tell if there is something wrong by running Memtest86?

DeSTRoYa
2003-12-19, 06:27 PM
Well...I ran Memtest86 and there were no problems found. This is really not cool. Help me! Someone must know wtf the problem is...

Daleon
2003-12-19, 07:48 PM
Memtest is bs. Look for Prime95, it is THE memory testing tool. Its dos based and you have to run it from floppy, but its the best.

Normally sound locks like you describe are often memory related. PS is very memory intensive. How much free memory resources do you have before launching PS? You have a gig, so you should try to keep it at around 85-90 megs being used idle, atleast under 100.

btw - latest cat's are 3.10's.

DeSTRoYa
2003-12-19, 08:23 PM
I have the Cat 3.10's now...but it still freezes. I'm gonna try running that memory test and see if anything shows up. In Windows Task Manager > Performance Tab, I have the following information, without PS running and restarting without playing PS:

CPU Usage: Fluxautes every few seconds between 0 and 4 percent

PF Usage: 127 MB

Totals:
-Handles 4765
-Threads 283
-Processes 24

Commit Charge (K)
-Total 130000 (avg. it fluxuates)
-Limit 3046244
-Peak 944392

Physical Memory (K)
-Total 1048048
-Available 813900 (avg. it fluxuates)
-System Cache 519700 (avg. it fluxuates)

Kernel Memory (K)
-Total 49680 (avg. it fluxuates)
-Paged 24300 (avg. it fluxuates)
-Nonpaged 25356

-End-

Now ALSO...there are some other things I have noticed.

1) In the Device Manager, Under System Devices, I have 5 functions for NVIDIA nForce 2 Memory Controller, and none of them have drivers installed. Is that a problem?

2) When I am loading a continent, the everything seems to be loading twice - the loading bar completes once, and then goes back to the start and loads again. Is this normal? This may be related to #3 below...

3) I have a file name Engine3d (text file) in my PS directory. In this file is a whole bunch of cool errors! I will copy and paste come of it onto here, starting from the beginning. Things seem to get added everytime I play PS, and if I delete it, it comes back just showing more and more errors everytime I play.

Engine3d::MyMem(280 MB)
FileMemory(anims.ubr) 62450877 bytes.
FileMemory(./patch1/anim_patch1.ubr) 5105571 bytes.
FileMemory(./patch2/anim_patch2.ubr) 3397096 bytes.
FileMemory(./patch3/anim_patch3.ubr) 20 bytes.
VertexShader Failed: Failed to load .Cg program file animated_decal.cg. Examine listing file for more information.

Available Texture Memory: 176 MB
WARNING*** Texture(vehiclegentread_1a_!.dds) is duplicated in FlatFile: ./patch1/dds_patch1_dxt5.fat
WARNING*** Texture(vanguardgen_1_!.dds) is duplicated in FlatFile: ./patch1/dds_patch1_dxt5.fat

-The "WARNING*** Texture(__________.dds/fat)....." text keeps going for hundreds of textures. At the bottom, after all the WARNING*** messages It says the following:

TEXTURE FILE NOT FOUND: xmas_nc_eagle_at2.dds
TEXTURE FILE NOT FOUND: debug.dds
TEXTURE FILE NOT FOUND: lod_banner_flag.dds
UNLITVERTEX: Failed to locate existing VB for 2372 verts in buffer size: 4096.
VB( 1965) Total: 30 MB FatCount: 463936 UnlitCount: 291376
Format:UnlitVertex Active: 33 Count: 128 Unused: 0 Total: 128 Size: 16 Vcount: 2048
Format:UnlitVertex Active: 50 Count: 128 Unused: 0 Total: 128 Size: 32 Vcount: 4096
Format:UnlitVertex Active: 46 Count: 128 Unused: 0 Total: 128 Size: 64 Vcount: 8192
Format:UnlitVertex Active: 71 Count: 128 Unused: 0 Total: 128 Size: 128 Vcount: 16384
Format:UnlitVertex Active: 36 Count: 128 Unused: 0 Total: 128 Size: 256 Vcount: 32768
Format:UnlitVertex Active: 47 Count: 96 Unused: 0 Total: 96 Size: 512 Vcount: 49152
Format:UnlitVertex Active: 64 Count: 96 Unused: 0 Total: 96 Size: 1024 Vcount: 98304
Format:UnlitVertex Active: 4 Count: 17 Unused: 15 Total: 32 Size: 2048 Vcount: 65536
Format:UnlitVertex Active: 0 Count: 1 Unused: 0 Total: 1 Size: 4096 Vcount: 4096
Format:FatVertex Active: 46 Count: 150 Unused: 46 Total: 196 Size: 16 Vcount: 3136
Format:FatVertex Active: 26 Count: 64 Unused: 0 Total: 64 Size: 32 Vcount: 2048
Format:FatVertex Active: 21 Count: 113 Unused: 143 Total: 256 Size: 64 Vcount: 16384
Format:FatVertex Active: 58 Count: 128 Unused: 0 Total: 128 Size: 128 Vcount: 16384
Format:FatVertex Active: 48 Count: 128 Unused: 0 Total: 128 Size: 256 Vcount: 32768
Format:FatVertex Active: 39 Count: 64 Unused: 0 Total: 64 Size: 512 Vcount: 32768
Format:FatVertex Active: 15 Count: 96 Unused: 0 Total: 96 Size: 1024 Vcount: 98304
Format:FatVertex Active: 6 Count: 32 Unused: 0 Total: 32 Size: 2048 Vcount: 65536
Format:FatVertex Active: 2 Count: 6 Unused: 26 Total: 32 Size: 4096 Vcount: 131072
Format:FatVertex Active: 0 Count: 2 Unused: 2 Total: 4 Size: 8192 Vcount: 32768

-----------

I'm hoping someone can help me out here.

DraygoKorvan
2003-12-19, 08:44 PM
Ok, Defrag your harddrive, the error means that it is failing to allocate to the memory (probably your pagefile)

Also, how much space do you have left on your harddrive? Make absolutely sure 10%+ is availible for consumption.

If that doesnt fix it, delete your planetside folder and reinstall the game entirely.

if that doesnt work, your RAM is probably currupted try removing one ram stick than the other to see if the error shows up.

DeSTRoYa
2003-12-19, 09:08 PM
-I've tried reformating my comp but it still happens
-Reinstalling does nothing to help either
-I have 55.7 GB Free Space on my comp (out of 75 GB)

I'll try the memory removal gig. But I dual-run my memory, will that do anything?

Cmon guys...I know there's a solution out there!

Cyanide
2003-12-20, 01:50 AM
Make sure you've got the newest version of your sound and motherboard drivers too. People always tell you to update video drivers, but motherboard and sound drivers cause problems too.

If you haven't noticed any stability problems in other modern games, or just from leaving your computer on for a while, then your ram is probably fine. Possibly your hard drive has developed a bad sector over the space where it it placing the page file. Reformating and reinstalling would not solve that. Try running a surface scan of the disk to check for bad sectors.

There's also the outside chance that the files you're installing the game from are corrupt. That error is the kind of error you get when you're compiling source code. Which makes me think there's something wrong with the part of the engine that contained the code from mymem.cpp.

DeSTRoYa
2003-12-20, 02:29 AM
Thx Cyanide...but I do have the latest versions of my sound card and MB drivers. I've also done a surface scan...no problems.

Installation files corrupt/not proper?

Could be...I dunno.

I downloaded it from Gamespot...

Keep it coming...maybe something will work.

Jagd
2003-12-20, 10:17 AM
Hey, that is the exact same error that came up for everyone using Win98 and WinME the day of the server merger. They had a patch to resolve it the next day, so I don't know how you are still getting that. Have you emailed the devs? Send the contents of that whole first post of yours to them via email and see what they say.

Very very strange though, that is exactly the same message as the show stopper bug from 2 weeks ago.

DeSTRoYa
2003-12-20, 02:43 PM
Things I have tried already:

-Restart computer (pffft.)
-Full scan (laff...)
-Reinstalling Planetside
-Reformat computer
-Scandisk (Surface scan)
-Defrag
-Various versions of Catalyst and Omega Drivers
-Updated SB Audigy 2 drivers
-Updated nForce 2 MB drivers
-Adaware scan
-Various settings in Plantetside including very lowest
-Reinstalled Dx 9.0b
-Disabling sound totally
-Disabling startup services
(probably more I can't remember)

Ugh...I've tried to much. I'm going to try removing a stick of RAM...I guess. In the meantime...any other suggestions?

Ait'al
2003-12-20, 07:20 PM
And remember you odnt have to show us all the stuff really in the first two posts(its all just what is physicaly in you comp) well the drivers can help. 8) you just need to show us the one that showed what your comip was doing(always go with the log file and your OS and some basic stuff) We need more log files! ^^ Tell me if there was something else in the first post i didnt notice. Er The patch for 98 couldnt have helped because hes not useing it. Unless hes running some old 98 drive for this that was causing hte problem but then id immagine it be fixed so...? um, I cant really think specifically what this could be 8( i need to get up to where i can do this sorta thing farly easily again. But did you try deleting a cache file or getting a fresh copy of hte file causing errors off hte cd and renaming hte old one to see if it still does this. Im not sure it this would cuase problems on its own from patches though or if it would dl the upgrade to fix it. I would hope so though! 8\ What does it do physically when it has the problem. Were you in a more intense area everytime, around a specific think in the game...... etc. anything you always notice? or specificaly notice happaning that sounds interesting?

Rbstr
2003-12-20, 07:35 PM
I don't know this is a realy wierd but, if you reformated your comuter, you started fresh, so i think its some kind of hardware incompatability, at a low level, mabe a bad ram stick or some incompatable hardware

Ait'al
2003-12-20, 07:39 PM
OH he reformated! yea check what he said 8p Wait didnt he reformat after the problem though ??

Daleon
2003-12-21, 01:55 AM
Looks like you're still using over 200 megs ram at idle. Try and slim some of the fat off XP. Look for some XP tuning sites via google. It will give you a list of crap services you can turn off safely to help ease memory usage.

As for those memory controllers, they should have drivers installed. Go to nvidia's website and d/l the 3.13 nforce drivers and load those ASAP.

DeSTRoYa
2003-12-21, 01:58 PM
I was having the problem before I reformatted also. I tryed to install the 3.13 Drivers, but the installer will not launch...which is kinda weird and uncool. I've already tried "slimming down" stuff happening in XP, but the problem still occurs. No matter what I do, this son of a - female dog will not work. Also, the problems occur randomly, just bam. No notice or hints that it will happen, and there is no link between them. SO...

Add this to the list, I had forgot about this one....

-Deleting the .lst files and machine.ini

AAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRRGGGGH!

/looksforsomethingsharptostabhiseyes

Daleon
2003-12-21, 07:41 PM
If you can't run the driver installer you got some problems. Did you run prime95?

DeSTRoYa
2003-12-22, 12:50 AM
Prime95...I looked for it...but I couldn't find it. I'll look again. Can ya give me a link?

Daleon
2003-12-22, 08:51 AM
http://www.mersenne.org/freesoft.htm

DeSTRoYa
2003-12-22, 04:47 PM
I fail to see how this Prime95 is testing my memory...What is this BS that it will take over a freaking month?

Daleon
2003-12-22, 11:50 PM
Under the options pull down there is a "torture test" option. It pretty much runs indefintely. Most ppl let it run for 24 hrs. If you don't get any errors from this or memtest86... then your cpu/mem should be fine.

DeSTRoYa
2003-12-23, 07:44 PM
I believe I have solved the problem. Yesterday I played for an hour and no freezing. Today I played for 3 hours, and also no freezing.
What I changed:

My screen when I first start up my computer always had said my memory was dual running at 200 MHz. My Proccessor runs at 166 MHz. I changed the memory to also run at 166 MHz, and now the problem is gone.

/happy

DeSTRoYa

Daleon
2003-12-24, 11:15 AM
Should always run your memory sync with cpu for best results. Looks like you were pushing the memory faster than it could handle at whatever timings you have. You could prolly pump up the voltage a little to it to help stability, but its best sync anyway.