STOP: 0x0000000A (0x00000020, 0x00000002, 0x00000000, 0x8044173c)

[CSForbious]

This is first of all the configuration that I am dealing with:



Asus K7V Motherboard
768mb PC-133
AMD 950mhz CPU
Maxtor 7200rpm 40gig as the master, Maxtor 7200rpm 80gig as secondary
Maxtor IDE controller for the two HD?s so I can get the full ATA/133
Sound Blaster Live!
SMC Network Card
Samsung DVD
Plextor 24x10x40
Elsa Gladiac 32mg G-Force2 Ultra


This is being run with Windows 2000 for the last 2 years. Within the last 3 days I started receiving the BSD (Blue Screen of Death). I was also receiving errors in CS more often like ?HL.exe has created errors and will be shutdown?. The error on the BSD was happening more frequent as time went on. The message on the BSD was as follows:



STOP: 0x0000000A (0x00000020, 0x00000002, 0x00000000, 0x8044173c)
IRQL_NOT_LESS_OR_EQUAL





I have found several websites that are telling me it is either

· a device driver trying to do something its priority level didn?t permit.

· RAM going bad.

· Hardware conflict



Mcafee VirusScan for Windows NT issue

Exact error is as follows:

STOP: 0x0000000A (0x0000015a, 0x0000001c, 0x00000000, 0x80116bf4)
IRQL_NOT_LESS_OR_EQUAL

Mcafee VirusScan for Windows NT 2.5.1(9607) and 2.5.2(9609) are not compatible with Windows NT 4.0

Uninstall Mcafee

Windows NT 3.51 upgrade from Windows NT 4.0

Exact error is as follows:

STOP: 0x0000000A (0x0000015a, 0x0000001c, 0x00000000, 0x80116bf4)
IRQL_NOT_LESS_OR_EQUAL

If you have upgraded your computer to Windows NT 4.0 from Windows NT 3.51 and have a server with Gateway Services for Netware to Windows NT 4.0 installed remove the Gateway Services for Netware and reinstall the service to resolve this issue.

Service Pack

Exact error is as follows:

STOP 0x0000000a (0x00000006, 0x00000002, 0x00000000, **********) IRQL_NOT_LESS_OR_EQUAL

********** - This portion may vary

Earlier service packs may have had issues with the TCP handling and updating the Service Pack will resolve the issue. Ensure you have the latest service pack installed in the computer.

Links to locations to download the latest service packs can be found through our Windows NT download section.

Driver issue

Drivers which have errors of their own can also cause the IRQL_NOT_LESS_OR_EQUAL error. Consider updating or reinstalling your drivers (more specifically your network and/or SCSI drivers).

For a listing of driver manufacturer company pages see our drivers page.

Hardware issue

In the event that the above information does not help to resolve your issue it is possible that the computer may be encountering a hardware issue. Attempt to exchange or replace hardware in the computer. Our recommendation would be:

RAM / CPU / NIC

I have checked all three sticks of ram and still receive this error. Any suggestions?

You know besides the obvious?.A three pound sledge. :

After I wrote this out My system crashed and I took the 40 gig and reformated and put a ghost image on it.
It worked for a week and the same symptoms have returned. Can someone please help me

 

[BenRosey]

The hard drive may be bad.

I've had problems where files have been corrupted and similar problems have ensued.

But then again, there are so many other possibilities...

 

[pcman2002b]

Microsoft Reference

The link posted above is from Microsoft's Website it may or may not help you determine the problem.


If you installed any devices just recently that may be the problem.
Any new software just recently, according to Microsoft this type of error can be hardware and/or software.


Look on the bright side, atleast your not trying to troubleshoot a Win98 BSD. With 2000 you get some info.

 

[NogginBoink]

Hmmmm.... no hits on that address in my supersecret database. 🙂

So let's break this down and get to good old-fashioned troubleshooting:

STOP: 0x0000000A (0x00000020, 0x00000002, 0x00000000, 0x8044173c)

means that the instruction at address 0x8044173c illegally touched memory address 0x00000020 while the processor was at IRQL 0x00000002. In this case, it was a read operation. Now, I realize this is gobbldeygook for many, but if you're really curious, "Inside Windows 2000, 3rd ed." contains good explanations.

Now, the first 64K of memory is ALWAYS off limits to EVERY process. The most frequent cause of touching bad memory is using a null pointer. So MS helps developers catch this type of error by marking the first 64K of memory no access. If a developer has a null pointer when accessing memory, the app crashes, or if the "app" is a driver, the box crashes. That's what's happening here.

You don't mention what service pack you're running. Please post that, because address 0x8044173c is an address in ntoskrnl.exe. This does NOT mean that the kernel itself is bad; more likely, a driver is making an API call that resides in ntoskrnl and passing bad data to the kernel, and the kernel is dutifully doing what it was told to do. Performing validity checks on every call to the kernel would get very expensive (read: slow), so the kernel trusts that drivers making API calls in kernel mode are passing good data.

If the problem just started 3 weeks ago and you've made no changes to the system, bad RAM is certainly a possibility. But I'm guessing you've made changes. Have you updated any drivers? How about virus signature files? (Antivirus programs run as a device driver.)

The fact that half life is suddenly generating errors could indicate bad RAM as well.

Open your System event log and apply a filter on source "Save Dump." This will give you a list of all the times your machine crashed. Look through the list of crashes. If they're all STOP 0x0A's with last parameter of 0x8044173c, it's a software error. If you're getting STOP 0x0A's, 0x50's, 0x4E's, then you're looking at bad hardware, most likely RAM. Basically, if the OS is crashing left and right for different reasons every crash, it's likely RAM/hardware. If it's always crashing on the same instruction, it's software.

Do you have a memory dump? Is it a kernel, small, or a full dump? (Check in the Advanced tab of System control panel, startup/shutdown options.) Set your system to produce a kernel dump.

 

[CSForbious]

The only software that I have added is antivirus defenitions for Norton AntiVirus 2002. I am running SP2 in it.
I have added some maps to the Half Life folder a couple times. The memory is suspect, but I am leaning towards
the HD Master as the problem. It was set to small dump and I changed it to kernel as you have suggested.


From the sysevent.log these are some of the errors that are happening repeatedly:

1. 5:02:53 PM BROWSER Error None 8032 N/A xxxxxxx The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{3AD7EC71-5868-49B8-944C-285482C84FCF}. The backup browser is stopping.
   
   NetBT Error None 4319 N/A xxxxxxx A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.
   

Hope this helps....🙂

 

[LiLithTecH]

Error code 8032 is caused by not having File and Printer sharing enable on a
PC that has shares on it.

Error code 4319 means you have either 2 machines with the same name or
are logged in to 2 PC's at one time.

Neither error has anything to do with your original problem.

The problem has something to do with Half-Life and the video card drivers.

 

[CSForbious]

Well guess what??? I am an idiot....DOH!!!!
It was a bad stick of Memory. A very bad stick....it would check out on boot up.
But when I used Memtest86 it had over 389 errors. Thanks guys for all your help.