Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: Stone on July 26, 2005, 08:35:00 AM
-
I have just re-installed my PC some weeks ago, and all seems fine, except, that now and then during AH2 my pc completly rebots.
Screen goes black and then the POST boot sequens starts (counting memory etc.)
I send a error report, some times it does not return any info, some time it says somthing about some unspecified driver (does not know what driver faild I guess)
I was thinkin GPU or CPU heat, but I dont know how hot it was when the PC crashed. Directly after the crash GPU is 52c and CPU is 55c. I guess they could be much hotter, before a crash would happend? And I have AMD, it would just burn I guess?
But hardware related maybe?
Any ideas "o guru of computer wisdom"?
-
Strange..almost sounds like your having a brief loss of power during play. Are you running any power battery backup units? I would think even if it was a driver problem, that the worst would happen is a lockup or CTD..not a complete reboot, but then again, Im no huge expert on it
Maybe also due to an overheat..but doesnt your Mobo have a heat alram? if so, let us know what temp you have it set to activate the alarm.
-
No UPS. But I have in the same room an other PC that never gets this problem, and the lights does not go, so I think it unlikely to be a power thing.
The power suply is brand new 550w, that I got when I re-installed my PC.
If the RAM fails, would it reboot the PC?
Is there any way to get CPU and GPU temperatures logged into some place, so I could see how hot the system was next time the PC crashes ?
-
I edited my above post after you replied, so Im going to repost my edit:
Doesnt your Mobo have an alarm to let you know its getting hot? If so, let us know what temp you have it set at for the alarm, as well as what temp you have it set at to shut down (can find this in the BIOS).
Maybe a memory issue..possibly running out of memory during play?? not sure, but it wouldnt hurt to take your mem chips out and blowing out the sockets. maybe a short due to dust collecting up.
Have you placed your comp case in a new location since the upgrade? reason i ask is, if your comp is like mine, the front of the case allows airflow coming in from the bottom. If my case sits on a carpeted floor, the airflow is obstructed and i get heat alarms.
-
Oh, I had the same problem of a reboot when my hard drive was close to being full. I think it ended up being a swap-file problem because of the full disk. Long shot, i know, but worth advising you of.
-
Yes the bios has an heat alarm. I set it, and found a mobo program that also monitors the heat of the cpu and system. In nvidia driver there is some kind of alarm also.
I dont think its the heat, but if it is, I should now get the alarm.
My disk is mostly empty space. (AH is about only program installed)
-
"My disk is mostly empty space. (AH is about only program installed"
Lol, now there's the reason to have a computer.. AH2 ONLY.
But seriously..wouldn't hurt to blow out the cobwebs in your system. You'd be surprised at how fast a system can get dirty
-
What made you buy a new Power supply. did the other one blow up, or were you just doint an upgrade?
-
I just wanted a more quiet power suply.
I also got quiet CPU and GPU coolers.
Aaah the silence in the room is nice.
Just would be nice with A/C in the room tho. At worst I had 30c in the room, but then it was a very hot day outside also.
When I re-installed the PC, I dissasemled the thing and cleaned it before re-assembly. So no dust.
Still, I think the case temp is now much higer than before, as the quiet system is more effective to get heat from GPU and CPU.
Dont know how hot the case temp can go befroe I get problems.
I set the alarms on for case temp at 50c and CPU at 70c.
It has not alarmed me yet.
I suspect the SoundBlaster Audigity for no reason other than it being a SoundBlaster card :rolleyes:
-
If it's overclocked, back it off to stock settings and try again. If it's not, try underclocking to see if it works then. If it works when it's underclocked, then it's likely heat related and you may need better cooling. Case cooling is just as important as the cpu and gpu cooling.
-
What Eagl said...usually when you are stressing (gaming) your pc and you get a reboot it is heat or voltage related. Either with the graphics card or the cpu...usually with memory you will get weird errors first. The real trick is duplicating the error.
-
My Gut Reaction here is a multimedia driver error, but let's rule out hardware first.
Assuming you have a CD burner, download the ISO image for the Ultimate Boot CD at http://www.ultimatebootcd.com/.
Burn the disc. Boot from the disc.
Run the Memory Tester first, at least overnight. This should rule out bad memory.
Run the CPU tester next. This should rule out the CPU for errors (but not heat - keep reading.)
Run the Hard Disk Checker next. There are utilities for each of the major vendors' hard drives on the disc. Run the one that matches your vendor. You're looking for surface errors, hardware controller errors, or any S.M.A.R.T. errors. Do the "quick tests" first, and then the "detailed tests" next. The latter may take an hour or two. This should rule out the hard drive.
Next, reboot into Windows. Download and install and RUN CPUBurn-In, at http://users.bigpond.net.au/cpuburn/.
Let it run for a few minutes at first, and then longer and longer, until you run it all night. This will REALLY HEAT UP your CPU like nothing else. If your PC runs all night without rebooting or sounding a heat alarm, we can rule out CPU overheating problems.
If it passes all these tests, then I think we should start looking at DirectX, video drivers, and sound card drivers. Note that the tests I've mentioned thus far don't really touch multimedia things, but only the base hardware, which should rule that out.
Finally, check the Windows Logs for errors - do you see any?
Get back to us with the results of your tests.
-Llama
-
Ok, thx.
I am downloading UBCD now. Lets see what I can found out...
The PC-Alert program that I am running, has not allerted about CPU or case heat. It also monitors the voltages.
Memory or some other component may not like the case heat tho.
In windows the case seems to be 40c, but I dont know how hot it gets when I get my Spit V in the air :)
I do not get the crash every day, but that just makes the fault more vierd I think...
I do think it some hw driver issue, but I run the test and write here how it goes :)
(if it is the memory I get a nice excuse to spend some $$ to get 1 gb in my system :lol )
-
There are 7-8 different memory test on the UBCD. Can I run any of those ?
Wich memory test is good to run over night?
-
memtest86+ is a good one. So is the regular memtest.
-Llama
-
Heat. Pure and simple. 60c (140F) = dead for your AMD CPU. If the CPU itself doesnt fry, you'll be popping motherboard components like Jiffy-pop if you spend too much time at those temps.
My post isnt entirely clear. AMD I think rates the CPUs up to 85c or 90c. But they also say in the papers I downloaded from their website that normal temperature ranges should never be above 60c. Damage to motherboard components can occur above that temp. If you are seeing 55c AFTER the reboot, you could have hit 60 and the motherboard reset the computer.
-
Hey Stone-
I had the same problem a few weeks ago...
Only for me, it was a bad driver. It turned out that the drivers I was using for my Medusa 5.1 USB headset were not on good terms with AH2. I discovered this because of the error report and it just so happened that my computer re-start would happen when I was talking on my mic.
(To be clear) I would be fly'n, press T or f12 to talk to someone and my computer would turn off completly, and then restart. It didn't happen all the time, and appeared fairly randome so it took me a while to figure it out.
For me the fix was simple, I just un-installed the Medusa drivers and let XP recognize the divice instead. Not sure if this is what you're experiencing, but I thought I'd share just in case.
Good luck bud-
-scott
-
its your power supply.
-
If this is Windows XP it will reboot rather than show a bluescreen by default. I'd go to control panel -> system -> startup and recovery and uncheck the option to reboot automatically after an error. This will now let your system display a bluescreen rather than just rebooting instantly. That might help you find out if this is a driver problem.
-
Memtest has run all night, and no errors are found.
I do the other tests.
I also take try to get the case heat down a bit. I think I have the case fans not on full speed.
I also set the Bluescreen thing on, as bloom25 says.
I hope its not the powersuply. Its brand new. My PC has now been runing the memtest for aprox. 12 hours without problems, so I think the power suply is ok, and the memory at this temperature.
I guess the case temp does not get to hot during the memtest.
Thanks all for reply. I will continue with the tests now.
-
dont forget it could be a virous too .
as for an amd @54c thats were it starts getting pushed some of them work fine others start to crash there . your temp at idle should be down at 46c at idle even with a cheap fan set up .
one thing to look at is the side case fan (if applicable) is it blowing In ?? or outward fighting for air from the cpu ?
if the mem tests are ok .. then i would suspect a driver issue perhaps .
-
My PC did have the reboot option in the settings selected. Now I removed it, so I see the blue screen.
But I have the minidumps, that windows generates.
This also means that it IS windows who restarted my PC !
Good news I think:)
I remeber that I once used some tool to analyze the minidump files. They should have the same info as the bluescreen, and more.
I have to goole for the tools now :)
I run a CPU test for 10 minutes. It did not find an error, but did write at one point:
"spurious 8259A interupt IRQ7"
I dont know what spurious means, but I will google that also ;)
I have two case fans. One in front blowing air in, and one in the back, blowing it out.
The case temp is now after some test running and now finlay back in windows at 40c, it is the alarm I set at 50c, but it never kicks in.
-
Well I have run the tests now. The CPU stress test get the heat up 61c and case temp to 41. That is not to bad I think?
The run "dumpchek" on the 4 dump files I have got generated, but they all gave different proboble causes :(
Last time I had a zeke in my sights at D200 when my pc went *puff*.
Oh well, just have to wait and see when the crash comes next time. Its not a daily problem.
-
heh one time during a very hot summer I found myself opening the case and had a household fan blowing on it..overheat solved :)
-
Originally posted by Stone
I run a CPU test for 10 minutes. It did not find an error, but did write at one point:
"spurious 8259A interupt IRQ7"
I have two case fans. One in front blowing air in, and one in the back, blowing it out.
The case temp is now after some test running and now finlay back in windows at 40c, it is the alarm I set at 50c, but it never kicks in.
....
Well I have run the tests now. The CPU stress test get the heat up 61c and case temp to 41. That is not to bad I think?
OK, we're getting somewhere.
First of all, I am going to go on record to say that anyone saying it is the power supply is just plain wrong.
Second of all, I think this shows that this isn't a heat problem. That CPU heating program I directed you to gets my CPU hotter than Aces High, or indeed, any other game I've tried, and if it runs OK for a long time and your CPU never got hotter than 61c, I think you're in good shape.
Now then, IRQ 7 usually relates to your parallel port, or if you don't have one, your sound card or network card. Usually. Not always, but usually. Here's how to find out:
Run the Windows Device Manager (right-click My Computer, choose Properties, click Hardware tab, then click Device Manager button). Pull Down View menu and choose Resources by Type. Click the "+" next to Interrupt request (IRQ). See what hardware is linked to IRQ7. Let us know.
-Llama
-
I wouldnt totally rule out the power supply .... but normally it would crash during a stress test .
61c on an amd is hot .. mine hits 50-54c when i stress test it .
i would check into that irq 7 .. you could have too much stuff sharing on that one and its causing a conflict . such as a added sound card ect .
one question . have you tested with a different high stress type game ??? and does it only crash while running ah2 ?
if thats the case then i would suspect a driver issue or an irq , sound card issue perhaps . could even be a bios problem..
-
What information does the bluescreen give you?
I highly doubt temperature is the root cause of this one. It's probably a driver issue.
-
The IRQ 7 thing is nothing to wory about. I found tons of the "spurious 8259A interupt IRQ7" error, and its not an error, just some anoying Linux thing?
I did check the IRQ7 and its free.
I have not got a blue screen since the start of this post, but the minidumps windows writes at a crash all have different reasons.
I have 4 dumps:
1) Probably caused by : ntoskrnl.exe ( nt!CcWorkerThread+269 )
2) Probably caused by : Unknown_Image
3) Probably caused by : kmixer.sys ( kmixer!MxSetMixLvlTable+148 )
4) Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpDestroyCollection+cd )
I have no other games installed, so I dont know if it just AH that would crash the PC. And it is not a daily thing either. Has hapend about once a week, but always in game.
-
I had the same problem with an asus A8V. updated the via mb drivers and it went away
shamus
-
Originally posted by Stone
I have 4 dumps:
1) Probably caused by : ntoskrnl.exe ( nt!CcWorkerThread+269 )
2) Probably caused by : Unknown_Image
3) Probably caused by : kmixer.sys ( kmixer!MxSetMixLvlTable+148 )
4) Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpDestroyCollection+cd )
Well, let's see...
1. NTOSKRNL.EXE is a process used to boot windows properly. You should NOT be seeing it in the task manager (process list) unless you've been infected by w32.bolzano and variants.
2. Unknown is just that. Unknown. Sorry.
3. kmixer.sys is the audio mixer/volume manager for Windows. I think this is telling.
4. HIDanything refers to a Human Interface Device - mouse, keyboard, joystick, etc. - plugged into a USB port.
I still think we're looking at a multimedia device driver issue. If I were you, I would try updating the following, maybe just one thing a week to see if anything is improving things:
1. Motherboard drivers. (especially if you have onboard sound or network in use).
2. Sound card drivers.
3. Video card drivers.
4. DirectX.
5. Joystick or mouse or keyboard drivers.
Obviously, we're all here for assistance if you need it.
-Llama
-
Have you tried turning down your sound exceperation a notch ??
this is looking like a driver/sound issue to me .
post up the 1st 1/3rd of your dxdiag and lets look it over ... maybe one of us can catch it from there .
-
Time of this report: 7/29/2005, 08:33:56
Machine name: PETER
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: Finnish)
System Manufacturer: NVIDIA
System Model: AWRDACPI
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) XP 2800+, MMX, 3DNow, ~2.1GHz
Memory: 512MB RAM
Page File: 183MB used, 1066MB 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: NVIDIA GeForce FX 5900 Ultra
Manufacturer: NVIDIA
Chip type: GeForce FX 5900 Ultra
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0330&SUBSYS_00000000&REV_A1
Display Memory: 256.0 MB
Current Mode: 1024 x 768 (32 bit) (120Hz)
Monitor: Default Monitor
Monitor Max Res:
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.6177 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 7/15/2004 11:42:00, 3740032 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 7/15/2004 11:42:00, 2459712 bytes
Device Identifier: {D7B71E3E-4070-11CF-917B-0A2000C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0330
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_MedianFilteri ng
{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
{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_MedianFilteri ng
{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_BOBVerticalSt retch
{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_MedianFilteri ng
{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_BOBVerticalSt retch
{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_MedianFilteri ng
{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 2 ZS Audio [D000]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0442 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 11/19/2003 05:13:54, 366160 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Standard
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
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 ZS Audio [D000]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0442 (English)
Driver Attributes: Final Retail
Date and Size: 11/19/2003 05:13:54, 366160 bytes
Cap Flags: 0x0
Format Flags: 0x0
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB Audigy 2 ZS DirectMusic Synthesizer [D000], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB Audigy 2 ZS Audio [D000], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 ZS Synth A [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 ZS Sw Synth [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 ZS Synth B [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy 2 ZS 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
SB Audigy 2 ZS 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
-------------------
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: Microsoft SideWinder Force Feedback 2
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x001B
FF Driver: C:\WINDOWS\system32\swpdflt2.dll
FF Driver Date: 8/17/2001 22:36:32
FF Driver Version: 4.05.2600.0000
FF Driver Size: 10240 bytes
Device Name: 6-button joystick w/two POVs
Attached: 1
Controller ID: 0x1
Vendor/Product ID: 0x045E, 0x01F5
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x0067
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 8/4/2004 09:08:42, 57600 bytes
| Driver: usbd.sys, 8/18/2001 15:00:00, 4736 bytes
|
+-+ USB Human Interface Device
| | Vendor/Product ID: 0x046D, 0xC025
| | Location: USB-PS/2 Optical Mouse
| | Matching Device ID: usb\class_03&subclass_01
| | Service: HidUsb
| | Driver: hidclass.sys, 8/4/2004 09:08:20, 36224 bytes
| | Driver: hidparse.sys, 8/4/2004 09:08:16, 24960 bytes
| | Driver: hid.dll, 8/4/2004 10:56:42, 20992 bytes
| | Driver: hidusb.sys, 8/17/2001 14:02:20, 9600 bytes
| |
| +-+ HID-compliant mouse
| | | Vendor/Product ID: 0x046D, 0xC025
| | | Matching Device ID: hid_device_system_mouse
| | | Service: mouhid
| | | Driver: mouclass.sys, 8/4/2004 08:58:32, 23040 bytes
| | | Driver: mouhid.sys, 8/18/2001 15:00:00, 12160 bytes
-
Stone have you tried not playing?
See if it does. If it does then i'm thinking graphics card. I was having a problem where my card was stuck in a loop or something like that. (graphic driver problem) Just reinstall your video card driver.
-
I wonder if theres a newer driver for your Sound card , these look dated (old)
Driver Name: ctaud2k.sys
Driver Version: 5.12.0001.0442 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 11/19/2003
id try these : Creative Sound Blaster Audigy2 and Audigy2 ZS Driver Update 1.84.55 (16.34 MB) 12 May 05
http://us.creative.com/support/downloads/download.asp (http://us.creative.com/support/downloads/download.asp)
-
You are right!
That sound driver is old. I update it :)
-
Ok, the sound card driver is now update, I let you know if my PC crashes again. (It did not do it allways, so time will tell)
Thank you all for your help :)
-
Thats the same driver I use for my SBLive! 5.1 card. Wonder if it makes a difference that his card is an Audigy.
-
i dont think so SA2
some sound cards are just like video cards and can use the same ole same ole ..
I looked it up for his SB Audigy 2 ZS , running win xp .
-
No boots anymore, so the soundbasterd driver update did the trick.
Thanks all :aok