Important Message

You are browsing the archived Lancers Reactor forums. You cannot register or login.
The content may be outdated and links may not be functional.


To get the latest in Freelancer news, mods, modding and downloads, go to
The-Starport

Something for Taw or Esq

This is where you can discuss your homework, family, just about anything, make strange sounds and otherwise discuss things which are really not related to the Lancer-series. Yes that means you can discuss other games.

Post Mon Apr 05, 2004 7:56 pm

Something for Taw or Esq

Well guys im haveing some major computer issues. My compouter has dumbed for the second time in as many days. When it comes on after a crash the blue screen of death will come one saying,

worker_thread_returned_at_bad_irql 0*0....0e1

ive treid all my ideas on how to fix it but it wont work. Ive done full reinstalls twice includding writing 0's to my hard drive before each time. If anyone has any ideas it would be very appreciated. Ive searched computer.net forums for the error and have found it but now wasy to fix it.

Matt

Post Mon Apr 05, 2004 11:33 pm

Going by the limited info you've provided, I'd say after two reinstalls your problem would most likely be directed at your hardware. RAM is usually a likely culprit in these situations. Best way to check it is (and im hoping you've got at least two sticks of ram) is to remove one stick, test for stability, then shut down, put it back and remove the other and test again. If one test comes up trumps, it's off to the hardware retailer to replace the dogey stick.

Post Tue Apr 06, 2004 5:57 am

presumably this is XP or 2K? this might well be RAM, but both os' can be finnicky about installing at all if there's bad memory. While I must admit I've never seen this message before, the string of numbers you're saying comes afterwards is usually a sign that the data components or registry is being knackered. This might be simply bad data; did you restore your stuff after the re-installs? if so then something you are restoring is fookin' up your installation. If not, then you might have a bad hard drive with corruption in the front end clusters.

then again, I might be completely wrong.

Post Tue Apr 06, 2004 6:22 am

@matt you say you found the error on computer.net forums bot no easy fix,
what info did it give you about the error ? and have you run a memtest proggy
here

Edited by - [STEEL on 4/6/2004 7:24:16 AM

Post Wed Apr 07, 2004 12:08 am

I would have to agree with my esteemed colleagues; possibly a RAM issue, but it also may be a registry issue. One other possibility; if the HDD is going down hill, it can corrupt the registry, thus causing problems. Have you scanned for bad sectors?

Return to Off Topic