News:

Tekforums.net - The improved home of Tekforums! :D

Main Menu

Whats causing the CTD/Bluescreens?

Started by Eagle, April 14, 2006, 23:28:52 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Eagle

Quote from: ShaunIs Sideband Addressing enabled in BIOS??? If it is disable it.
Dont think I have that in mine?...  :?

QuoteHave you got the latest DirectX installed???
First thing I did. :)

QuoteTry a older Omega driver from the archive http://www.omegadrivers.net/ (6.1 or 6.2)
Ill try one. I know to use DriverCleaner too so no worries on that score. ;)

Hang on... arent they drivers for Radeon/ATI Cards?

I still get the feeling it isnt driver-related (what caused the continual reboot?...) - but if thats what its suggesting...

:)

Shaun

Ignore the 6.1 or 6.2 that was me being a nub :P but there is Nvidia drivers as well.

Eagle

:D

Still dont know which one? [spinning eyes] :) lol


Pete

Tried crippling the ram yet? Set it to cas3, 266mhz and give it a spin.

Can you put the rad back in and look at any error messages you get, or can you try the ram & cards in another system?

Temps ok?
I know sh*ts bad right now with all that starving bullsh*t and the dust storms and we are running out of french fries and burrito coverings.

Eagle

Quote from: sdpTried crippling the ram yet? Set it to cas3, 266mhz and give it a spin.
Could be worth trying but remember that my old RAM was running at safe timings and the problems were just the same.  Thats the hook here - the new hardware is experiencing the same problems as the old. :)

QuoteCan you put the rad back in and look at any error messages you get, or can you try the ram & cards in another system?
Too little time Im afraid. :(

QuoteTemps ok?
IIRC, the CPU temp is around 52 deg or so (straight after gaming).  Warm, but not so blisteringly hot as to cause so many crashes.  Besides some crashes/freezes/BSODs are happening hours into a game.

Ive now tried running one stick in slot one (again) and it crashed this time within a few minutes.  Therefore, Im now inclined to think that it could be something to do with a background event.  Some prog or something trying to do something thats pulling the rug from under the CPU and/or memory.  Just generally being annoying in a Windows stylee...  :roll:

Heres what I have running when gaming:

Red indicates what I can successfully shut down/stop before starting a game.  The ones left alone are those that either I cant shut down or wont because I dont know whether I should...

McSheild and CTHELPER definitely wont stop.

CAN I run games from Safe Mode?...  What about creating a new user with F-all going on in the background?  How would I acheive that? :)



:)
Ã, 

Shaun

You cant run games in Safe mode but you can run with the minimum amount running.
 Type msconfig into run box, then under Services tab put a tick in hide all Microsoft services, then turn everything off that hasnt got Nvidia as the Manufacturer and your sound card, then all off under Startup tabs except Nvidia again and your soundcard then reboot.

Tbh I dont think it will help Im about 80% sure its your mobo and the other 20% could be your PSU so I think you need to try a different PSU if you can.

Eagle

Cheers. :)

Fair cop on the mobo but out of interest, what makes you think its the PSU?  (550W Enermax).

Settings again:

http://www.tekforums.co.uk/posts/list/75/761.page#10031

If it came to it, and I had to install a new mobo, would I have to reinstall Windows?...  :shock:

:)

Shaun

The voltages look fine there, but seeing the problems you had when you put the volts up on the Ram it could be PSU related,
so better testing that before you get a new mobo and IMO there the only 2 things left it could be with everything thing else you have done lol  :P .

If it is the mobo you best bet I think would be to try and get a second-hand NF7.

Pete

Yup, you can put the xp disk in after swapping the mainboard, choose install new but when it detects your existing install itll say hey I can sort that out," and you click repair and itll sort itself out.

-

Cost of cheap motherboard & 50p ebugger psu for testing + spares drawer: Ã,£peanuts

Time taken farting around & staring at laras boobs waiting for a crash: hours n hours

Put a price on your time - throwing money at stuff like this is the best thing to do.
I know sh*ts bad right now with all that starving bullsh*t and the dust storms and we are running out of french fries and burrito coverings.

knighty

have you treid the other thing they sugested ? turning down video acceleration ?

right click on the desktop / properties / settings tab / advanced / trouble shoot


never know, it might make a difference, and it all helps narrow down the fault ;)

Eagle

Quote from: ShaunIf it is the mobo you best bet I think would be to try and get a second-hand NF7.
Might try that anyway. :)

Eagle

Quote from: sdpPut a price on your time - throwing money at stuff like this is the best thing to do.
You nailed it there!  Thats the way I usually solve things because I lose more money than I spend when my systems not running tickety-boo!

Probably lost about Ã,£800 already since last friday in lost sales, fannying around with this!  :roll:  :mrgreen:

Eagle

Quote from: knightyhave you treid the other thing they sugested ? turning down video acceleration ?
On the list! :)

Cheers, all. :)

Eagle

Ã, 
Turning down the sound hardware acceleration in DXDiag has made a significant difference. :D A well documented fix too.

Testing hasnt been exhaustive but Ill try some more tomorrow when I get TR: Legend.  Again... :/

Do these settings affect sound quality in Windows as well as games?

:)