25 replies to this topic

[chrisandsarah]

Might sound silly, take the side off and run the hoover on the CPU fan, might fix the issue. Also run a disk check on the 'C' drive. You will need to restart windows to get it to run through.

[Youngowner93]

Well it's been ok since i've turned write debugging off i've had many happy hours of gameplay without a problem. It's not over heating i've set a shutdown temp as it hasent shutdown i suspect it's fine, i;ve had the card under load for 20mins and tempatures are good no real concern there. So as far as im concerned it's working as it should (at least that how it seeems) and until it happens again im happy.

[mini77]

Might sound silly, take the side off and run the hoover on the CPU fan, might fix the issue. Also run a disk check on the 'C' drive. You will need to restart windows to get it to run through.

It’s not a silly suggestion as you can buy compressed air in an aerosol can that’s just for the job you mentioned

[minimender]

be careful with compressed air as you could build up static if its too fierce and you dont want static building up

[mini77]

be careful with compressed air as you could build up static if its too fierce and you dont want static building up

Thanks, but I wonder why it sells if it can cause static...that can zap chips including RAM

[MaxAndPaddy]

The most probable cause is going to be either a faulty component or device driver. It sounds like you have done most of the obvious checks as Memory and corrupt disk sectors would have been my first guesses. Unfortunately its a bit of trial and error now. I would consider using the rollback facility if you have updated any drivers recently and if you havent already run checkdsk /f from dos command prompt then reboot.

I had an almost identical error which drove me mad for the best part of a week, it turned out to be a fault with the on-board wireless card, disabling it solved the problem (although I had a get a USB replacement). So try disabling different components one by one and see if that helps. If you are extremely lucky then you might find the event viewer (in admin tools) has recorded some useful dump information, although in my experience this doesnt happen very often, but it might help you pinpoint the component.

Edited by MaxAndPaddy, 02 September 2011 - 08:54 AM.

[Deathrow]

With regards to cleaning out the inside of your PC.

Compressed air is your best bet. If you're worried about static, leave the power cable plugged in but turn the power supply off at the rear. This keeps the whole case earthed.

If you choose to hoover out the dust do not have the hoover itself anywhere near your PC. Keep the base of the hoover away and use the flexy hose to do the work. You're still better off with compressed air though.

[mini77]

The most probable cause is going to be either a faulty component or device driver. It sounds like you have done most of the obvious checks as Memory and corrupt disk sectors would have been my first guesses. Unfortunately its a bit of trial and error now. I would consider using the rollback facility if you have updated any drivers recently and if you havent already run checkdsk /f from dos command prompt then reboot.

I had an almost identical error which drove me mad for the best part of a week, it turned out to be a fault with the on-board wireless card, disabling it solved the problem (although I had a get a USB replacement). So try disabling different components one by one and see if that helps. If you are extremely lucky then you might find the event viewer (in admin tools) has recorded some useful dump information, although in my experience this doesnt happen very often, but it might help you pinpoint the component.

lol you wasted your time writing all this, if you read the thread you would know he has fixed the problem

[mini77]

With regards to cleaning out the inside of your PC.

Compressed air is your best bet. If you're worried about static, leave the power cable plugged in but turn the power supply off at the rear. This keeps the whole case earthed.

If you choose to hoover out the dust do not have the hoover itself anywhere near your PC. Keep the base of the hoover away and use the flexy hose to do the work. You're still better off with compressed air though.

I agree Compressed air is best for the job

[MaxAndPaddy]

The most probable cause is going to be either a faulty component or device driver. It sounds like you have done most of the obvious checks as Memory and corrupt disk sectors would have been my first guesses. Unfortunately its a bit of trial and error now. I would consider using the rollback facility if you have updated any drivers recently and if you havent already run checkdsk /f from dos command prompt then reboot.

I had an almost identical error which drove me mad for the best part of a week, it turned out to be a fault with the on-board wireless card, disabling it solved the problem (although I had a get a USB replacement). So try disabling different components one by one and see if that helps. If you are extremely lucky then you might find the event viewer (in admin tools) has recorded some useful dump information, although in my experience this doesnt happen very often, but it might help you pinpoint the component.

lol you wasted your time writing all this, if you read the thread you would know he has fixed the problem

I'm always late

[mini77]

The most probable cause is going to be either a faulty component or device driver. It sounds like you have done most of the obvious checks as Memory and corrupt disk sectors would have been my first guesses. Unfortunately its a bit of trial and error now. I would consider using the rollback facility if you have updated any drivers recently and if you havent already run checkdsk /f from dos command prompt then reboot.

I had an almost identical error which drove me mad for the best part of a week, it turned out to be a fault with the on-board wireless card, disabling it solved the problem (although I had a get a USB replacement). So try disabling different components one by one and see if that helps. If you are extremely lucky then you might find the event viewer (in admin tools) has recorded some useful dump information, although in my experience this doesnt happen very often, but it might help you pinpoint the component.

lol you wasted your time writing all this, if you read the thread you would know he has fixed the problem

I'm always late

lol at least what you wrote made sense