WinXP BSOD...need help

[TheMonk]

Hey,

I am getting random blue screens of death with the same error message. The first few times there was no Minidump.

Anyways the error code is Driver IRQL not less or equal

0x0000001D (0x71A5DF52, 0x00000002, 0x00000008, 0x71A5DF52)

but it has no file relating to the error, however in event viewer under system I have a warning with the same time that the BSOD occured and if i open it up description is: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Please help

Thanks in advance

[Jazz_Data]

download windbg from microsoft (google it)

install it

start program, file -> open crah dump

open latest crash dump (c:\windows\minidump)

you will get errors, etc... dont worry

then type in the command area:

!analyze -v

You will get detailed info and possibly a driver name that caused the crash. It will give you a better idea etc...

[Mekoa]

but it has no file relating to the error, however in event viewer under system I have a warning with the same time that the BSOD occured and if i open it up description is: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Were you running something like a BitTorrent client when this happens?

[TheMonk]

Yeah using uTorrent, however its only started to happen recently. Anyways last night i got a completely different error which was 0x00000024 Ntfs.sys had a problem or something along those lines.

Could these BSOD be indicating to damaged hardware? (i have run memtest86+ 6 passes and no errors, Ran Seagate Seatools, Hitachi DFT and no errors in the hard drive either. and CPU doesn't seem to overheating (30degC at idle using core temp (its a Q6600 B3))

System specs:
Asus Striker Extreme
Q6600
OCZ Flexxlc 9200 2GB
Seagtae 7200.10 500GB
EVGA 8800GTS 640MB

[ShambleS]

"0x0000001D"

Is Either a network related address usualy refering to the ipx protocall.
Or it could be a no sipn lock stop error.
(most common culprates i know of)

It should either be a error on the hard disk drive so you need to run chkdsk on the drive.

Or you have been changeing your networks ipx frametype settings
So change that back to autodetect.
This can happen becous you installed NWLink IPX/SPX/NetBIOS Compatible Transport protocol.
And there was a hot fix released, but it was suposedly also adressed in service pack 2.

The stop error being Driver irQ is strange.
But would tend to imply NDIS.SYS as the culprate stemming from the ipx fault.

you did not state it but i am working on the assumption that you are using windows xp.
Im also assuming that you have updated xp fully.

Hope this helps some.

P.S

Hello :)

[TheMonk]

Ok nevermind guys thanks very much for the help. I have run memtest for the umpteenth time and eventually its found errors, many errors.

Thanks.

[LIQUIDHERION]

yeah if you type that error ....
Driver IRQL not less or equal,,,into google...it says its a ram issue...
The all knowing google.