• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Constint BSOD's and IRQL Problomes

scotepi

n00b
Joined
Oct 19, 2003
Messages
33
have posted this problem in another forum but no one there seme's to know what's wrong

http://psforums.station.sony.com/ps...scending&page=1

I have reinstalled windows many times, including going back and forth between windows 2k and windows XP pro. I also have a 9200se that my computer works fine with.

has anyone experienced a similar problem or have any idea as to what is causing this?

specs:
DFI Lanparty NFII revB
XP 2800+ Barton
2GB RAM PC 2700 cl2.5
IDE WD 80GB 8mb, WD 160GB 2mb
SATA WD 200GB 8mb , WD 250GB 8mb, WD Raptor 74GB 8mb
8x Plextor DVD+/-RW
48x24x48x16 LiteOn Combo
ATI Radeon 9600xt 128MB
 
some farther research It looks like a possible cause could be my TV card witch is at IRQL 10.

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20936254.html said:
When you get the stop error it will be accompanied by some information i.e.

Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL*** Address x has base at x - filename

The parameters refer to the specific issues that are involved:
Parameter 1 - An address that was referenced improperly
Parameter 2 - An IRQL that was required to access the memory
Parameter 3 - The type of access, where 0 is a read operation and 1 is a write operation
Parameter 4 - The address of the instruction that referenced memory in parameter 1

Make a note of the stop error ESPECIALLY the "filename" as this can point you to a defective driver or the software/hardware at the root of the problem. do a Google search on the "filename" To help you narrow it down.
 
Back
Top