Win 2k Issues... :(

[htmlmasterdave]

I seem to be getting a lot of bsod's lately, they are usually irq related, so i figured i would reinstall all my drivers.. i've done that, including sp2, no luck even directx i've reinstalled... anyone have any ideas? TIA

 

[NogginBoink]

I doubt they're IRQ related. An IRQ and an IRQL are different things. (I assume you're getting a STOP 0x0A or a STOP 0xD1, IRQL_NOT_LESS_OR_EQUAL.)

Post the STOP code and the bugcheck parameters (the hex numbers in parentheses). You can get these from the savedump events in the system event log.

Does any particular action on your part seem to trigger the problem? How long has your system been up and running with no problems? When did the problems start? What did you do to your machine before problems started?

 

[htmlmasterdave]

It started a few days ago, it was rock stable before, and it does seem to just randomly do this. Where can I get at the system event log? Ty btw

EDIT: I had to replace a psu about a month ago, it caused MANY bsod's and stuff, since it wasn't giving enough voltage, so that may have messed up my install? Other than that, it's been stable since about mid november



<< I doubt they're IRQ related. An IRQ and an IRQL are different things. (I assume you're getting a STOP 0x0A or a STOP 0xD1, IRQL_NOT_LESS_OR_EQUAL.)

Post the STOP code and the bugcheck parameters (the hex numbers in parentheses). You can get these from the savedump events in the system event log.

Does any particular action on your part seem to trigger the problem? How long has your system been up and running with no problems? When did the problems start? What did you do to your machine before problems started? >>

 

[htmlmasterdave]

Well, it happened again, this is what i got:

STOP: 0x000000D1 (0x2D31C697, 0X0000001D, 0x00000000, 0x2D31C697)

Any ideas?

EDIT: It's the IRQL one you mentioned

 

[NogginBoink]

<< Well, it happened again, this is what i got:

STOP: 0x000000D1 (0x2D31C697, 0X0000001D, 0x00000000, 0x2D31C697)

Any ideas?

EDIT: It's the IRQL one you mentioned >>



Hmmm.... very interesting.

All STOP codes are caused by kernel level problems. In a STOP D1, the last parameter is the address of the instruction that caused the fault. (0x2D31C697)

The problem is, this address isn't in the kernel address space! Kernel space starts at 0x80000000!

Go through the system event log and see if all of the STOPs were the same bugcode (D1) and if they all had the same last parameter (2D31C697).

There are two possibilities: bad RAM, or a driver that's writing to memory that it doesn't own, therefore trashing the data that another driver owns, throwing your box into mayhem. Unfortunately, neither of these is easy to troubleshoot.

Did you make any changes to the machine before it became unstable? (ANY changes.)

EDIT:Okay, not *all* stop codes are caused by kernel level problems. But those are the exceptions rather than the rule.

 

[htmlmasterdave]

I literally haven't changed a thing, however, it seems to have gone away....been stable for 17 hours 30 min so far

 

[Derango]

<< I literally haven't changed a thing, however, it seems to have gone away....been stable for 17 hours 30 min so far >>



You do realize its going to crash now

 

[htmlmasterdave]

lol I thought that just as i said it, but it does still seem good...



<<

<< I literally haven't changed a thing, however, it seems to have gone away....been stable for 17 hours 30 min so far >>



You do realize its going to crash now >>