PC crash and do a hard reboot when....

[Ctuchik]

whenever i log out a char. every time since a few days the PC crashes and do a hard reboot (like when u press the reset button on the box) ive reinstalled both the OS and the game (in that order) new drivers and everything. hell i dont even get a error message in the error logs to show what the hell is wrong..

but every damn time i log out a toon i crash. and every damn time a tiny bit of my HD fucks up and i get more "unreadable sectors". and yes its only this game that does it. and yes ive tried with a diff HD. thats not the problem it seems as it does the same thing on the other 4 HD's ive tried to.

never had any problems what so ever with this game (apart from the lag but thats diffrent)

not even a ctrl + alt + delete and close the game in task manager works.. PC still reboots.

Soooo.. anyone have any suggestions?

 

[scorge]

whenever i log out a char. every time since a few days the PC crashes and do a hard reboot (like when u press the reset button on the box) ive reinstalled both the OS and the game (in that order) new drivers and everything. hell i dont even get a error message in the error logs to show what the hell is wrong..

but every damn time i log out a toon i crash. and every damn time a tiny bit of my HD fucks up and i get more "unreadable sectors". and yes its only this game that does it. and yes ive tried with a diff HD. thats not the problem it seems as it does the same thing on the other 4 HD's ive tried to.

never had any problems what so ever with this game (apart from the lag but thats diffrent)

not even a ctrl + alt + delete and close the game in task manager works.. PC still reboots.

Soooo.. anyone have any suggestions?

1) defrag see if it does pick up bad sectors, try changing hard drive IDE or SATA cable.

2) update motherboard bios

3) Partion HD and install in partion.

 

[Ctuchik]

ok done all that and its a tad better now. but still not good. im still getting random reboots whenever i exit the game (log out a char)

funny part is that now im getting a really quick error message on the scandisk that something is wrong with the .ini files that belong to the last char i played on daoc.....

resulting in scandisk trying to fix it and i loose my QB settings

 

[jigsaw]

You using an ATi graphics card and AMD processor?

 

[Ctuchik]

AMD xp 2400+

no ATI card tho.. GF fx5200 there.. (not the best but its showing pictures)

heres part of the DXdiag for those that can understand it...

------------------
System Information
------------------
Time of this report: 12/30/2004, 14:01:10
Machine name: SUCK
Operating System: Windows XP Professional (5.1, Build 2600) (2600.xpclnt_qfe.021108-2107)
Language: English (Regional Setting: Swedish)
System Manufacturer: VIA Technologies, Inc.
System Model: KT600-8237
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) XP 2400+, ~2.0GHz
Memory: 512MB RAM
Page File: 349MB used, 900MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.0001.0904 32bit Unicode

------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: The file emu10k1f.sys 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.
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: NVIDIA GeForce FX 5200
Manufacturer: NVIDIA
Chip type: GeForce FX 5200
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0322&SUBSYS_00000000&REV_A1
Display Memory: 128.0 MB
Current Mode: 1024 x 768 (16 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.6693 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 10/29/2004 16:50:00, 3736704 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 10/29/2004 16:50:00, 2826944 bytes
Device Identifier: {D7B71E3E-4062-11CF-9579-0A2000C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0322
SubSys ID: 0x00000000
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{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_BOBVerticalStretch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering
{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_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 Live! Wave Device
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0002&SUBSYS_80271102&REV_08
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: emu10k1f.sys
Driver Version: 5.12.0001.3213 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 12/13/2000 02:00:00, 404335 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 5000, 48000
Static/Strm HW Mix Bufs: 32, 31
Static/Strm HW 3D Bufs: 32, 31
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 Live! Wave Device
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: emu10k1f.sys
Driver Version: 5.12.0001.3213 (English)
Driver Attributes: Final Retail
Date and Size: 12/13/2000 02:00:00, 404335 bytes
Cap Flags: 0x41
Format Flags: 0xFFF

-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not 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 Live! Wave Device, Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
B: SB Live! MIDI Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
MPU-401 [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
A: SB Live! MIDI Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Live! MIDI UART [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 Live! MIDI UART [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
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: Logitech WingMan Extreme Digital 3D
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC029
FF Driver: n/a

Poll w/ Interrupt: No
Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x1106, 0x3038
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 8/23/2001 13:00:00, 50688 bytes
| Driver: usbd.sys, 8/23/2001 13:00:00, 4736 bytes

----------------
Gameport Devices
----------------
+ PCI bus
| Matching Device ID: *pnp0a03
| Service: pci
| Driver: pci.sys, 8/23/2001 13:00:00, 62464 bytes
|
+-+ Standard Game Port
| | Matching Device ID: *pnpb02f
| | Service: gameenum
| | Driver: gameenum.sys, 8/17/2001 15:02:32, 9728 bytes
| |
| +-+ Logitech WingMan Extreme Digital 3D
| | | Vendor/Product ID: 0x046D, 0xC029
| | | Matching Device ID: gameport\vid_046d&pid_c029
| | | Service: LwAdiHid
| | | OEMData: 04 00 00 10 07 00 00 00
| | | Driver: LwAdiHid.sys, 8/17/2001 12:49:14, 20192 bytes
| | | Driver: hidparse.sys, 8/23/2001 13:00:00, 23680 bytes
| | | Driver: hidclass.sys, 8/23/2001 13:00:00, 33152 bytes
| | | Driver: hid.dll, 8/23/2001 13:00:00, 22528 bytes
| | |
| | +-+ HID-compliant game controller
| | | | Vendor/Product ID: 0x046D, 0xC029
| | | | Matching Device ID: hid_device_system_game
| | | | OEMData: 04 00 00 10 07 00 00 00
|
+ PCI bus
| Matching Device ID: *pnp0a03
| Service: pci
| Driver: pci.sys, 8/23/2001 13:00:00, 62464 bytes
|
+-+ Creative SBLive! Gameport
| | Location: PCI bus 0, device 11, function 1
| | Matching Device ID: pci\ven_1102&dev_7002
| | Lower Filters: ctljystk
| | Service: gameenum
| | Driver: ctljystk.sys, 8/17/2001 13:19:20, 3712 bytes
| | Driver: gameenum.sys, 8/17/2001 15:02:32, 9728 bytes

 

[jigsaw]

try changing the AGP apeture size in the BIOS to either 128mb or 64 mb see if that helps


update the SB live drivers if u can as well

 

[Shan]

Sounds like you're getting bluescreen on exit. I used to have same shit when i had sucky GFX card, then again you don't have sucky GFX card Bluescreens are majorly caused by conflict between gfx and mobo. *Shrug*
Or then it hardreboots while clearing RAM swap (if you crash while logouting it's prob. because of this, since swap is partially cleared when you log out to character screen. Can't tell what exactly causes it)

 

[Zlugugg Benvis]

Almost the same problem on one of my comps ... got old sucky gfx though ... BUT worked like a charm for a year up till last week ... now it ALWAYS freezes when loging out to switch char or quit.

 

[Kicks]

I had a similar problem once, in fact I had a whole host of problems with windows generally but the one you're describing was the first sympton I encountered. To cut a long story short, turned out my RAM was buggered, replaced and now all fine .

If you've had the oppertunity to try 4 hard-drives then chances are you've got some spare RAM floating about. Wack it in and give it a try .

 

[Nichii]

If nothing work's... (and it's only the DaoC?) try go complan and get a new CD imo

 

[Void959]

Whilst graphics cards issues are responsible for many bluescreens, I can't see how they could cause the HDD sector corruption. The most common cause of this is faulty ram, as Shan mentioned, and to my mind the most likely cause. That said it could be one of several components causing this - the RAM may be operating badly either because it damaged or because it is receving an inadequate or fluctuating voltage due to a faulty motherboard, or PSU (or both). I can't guarantee any of this will help but for what its worth I can suggest the following steps:

(1 - Reset the BIOS. You can usually do this by unplugging the power, removing the battery, leaving for 1 min or so, putting battery back in, leaving for 1 min or so then reconnecting power.

2 - Try all the common software related fixes (just in case): Latest drivers for graphics card, motherboard, and anything else you can find drivers for. Dont bother with anything disk related as you say you've already tried with 4 HDDs.)

3a - **Test the ram using memtest 86** I dont have a link atm but its easy to find and use (creates a bootable disk which it runs from). Run all tests for a few passes and if it finds no errors then run extended tests for a few passes.
3b - Test your system using Prime95, again dont have a link but its easy to find. Select torture test 2 and run it for a few hours, even overnight. This also puts a good deal of stress on the ram and should find problems, though it won't isolate the cause.

IF either of these progs find problems then reply back with the basic info and i'll try to help you further, if they don't find anything then the problem is probably not ram related and I don't have a clue what to do

 

[Matmardigan]

To cut a long story short, turned out my RAM was buggered, replaced and now all fine.

like he said. Thats the problem.

Change or buy new Ram and ur Problem will be fixed.

U also can drop the FSB. But just do it if u know what ur doing. Go into setup, change ur FSB from, dunno how fast ur FSB is, 400? 333? 266? and change it 2 133. It will slower ur machine but ur problem will be fixed till u got new RAM.

 

[Deerstalker]

like he said. Thats the problem.

Change or buy new Ram and ur Problem will be fixed.

U also can drop the FSB. But just do it if u know what ur doing. Go into setup, change ur FSB from, dunno how fast ur FSB is, 400? 333? 266? and change it 2 133. It will slower ur machine but ur problem will be fixed till u got new RAM.

I had a 512 single in my machine and it rebooted constantly, swapped it out for 3x 256mb simms ( max board can handle ) and it hasn't done it since.

Ram is usally the prime cause of problems.

DS.

 

[Void959]

Although RAM is probably the direct cause of the problem, as I mentioned, it might not be the root cause. By buying new RAM you will solve the problem, but if the mobo or PSU is faulty, you're shooting yourself in the foot as the brand new RAM will still get damaged over time - maybe hours, maybe months. Just bear that in mind.

 

[Awarkle]

it could be down to the new detonator drivers ive heard from other peeps that their computers blue screen when loading daoc.

Might pay you to install some earlier detonator drivers.

also although this might cause you some pain in setting up your quick bars delete all your character ini files in toa and do a scandisk.

might be one of them has corupted and cant save when you exit out of that character THUS its causing the compy to crash out

 

[frogster]

Yada yada yada

Simplest solution is to Rightclick My Computer > Properties > Advanced > Startup and Recovery Settings > Uncheck Automatically Restart under System failure.

This will tell XP not to automatically restart when the system fails and produce a BSOD instead. This should give you some indication of what the problem is.

Every time you log out of DAoC it writes to your Char.ini files to update them of any settings, such as Qbar settings.

It sounds to me that your computer is having trouble doing that and failing. Its all very well people "advising" you to buy this, buy that, but the simple fact is you may not need to. Its always best to examine all the possiblities that wont cost you a penny first.

Such as: Follow my advice on the system failure check box. If it comes up with a HD access error, as i expect it might, then download a low level format utililty from your harddrive manufacturer. This will flag any unusable sectors as such, and windows will not be able to access them. You will obviously lose HD capacity doing this, but atleast your hard drive will work. If this is the problem, it indicates imminent Harddrive failure anyway, so, IF it is the case, buy a new one.

 

[frogster]

Hmm, i guess its always a possibily that your antivirus is viewing the alterations of the ini files as malicious, causing DAoC to exit incorrectly and producing a system failure :O Just a thought.

 

[Void959]

Frogster, the reason many of us think RAM is the problem is because of one the symptoms - HDD sector corruption on reset. Anything can cause a BSOD, but will not do any damage to the HDD, this can only be caused by faulty RAM writing its contents sequentially to a random part of the disk, overwriting any file structure etc. Windows programs can whatever they like to the disk, but it must ultimately be saved as files, so the structure will not be damaged and you will never get unusable sectors.

And the problem is hardly likely to be hard-drive related when he experienced the same problems with 4 drives

 

[frogster]

I agree, but its not likely that DAoC is the only high resource application he uses. Why would faulty RAM only affect one application? The reason i mentioned it was to highlight a possible problem, and a solution.
Buying new RAM is not a solution until the RAM is proven faulty imo.
The main point of my post was to highlight the "Automatically Restart" option, which would give a better idea of what is causing the failure, and to point out that there are plenty of other alternative avenues to try first that wont cost a penny.

 

[Ilum]

I agree, but its not likely that DAoC is the only high resource application he uses. Why would faulty RAM only affect one application? The reason i mentioned it was to highlight a possible problem, and a solution.
Buying new RAM is not a solution until the RAM is proven faulty imo.
The main point of my post was to highlight the "Automatically Restart" option, which would give a better idea of what is causing the failure, and to point out that there are plenty of other alternative avenues to try first that wont cost a penny.

omg its teh Nee