For a few weeks now I've been getting BSoD's with the IRQL_NOT_LESS_OR_EQUAL error, and I've been trying to locate the source of the crashes every time they pop up.
I'm pretty sure this isn't a hardware error, mostly because of the fact that I've been running several memory test programs on and off for a few days time, but also because verifier.exe confirms that it is in fact a driver trying to "corrupt the kernel" which sounds really dangerous.
Thing is, I don't know which driver it is.
I've included the two latest .dmp files, where the latest is the [url=http://dl.dropbox.com/u/24880991/112011-8174-01.dmp]verifier-induced crash[/url], and the other one is a genuine [url=http://dl.dropbox.com/u/24880991/112011-17940-01.dmp]IRQL_NOT_LESS_OR_EQUAL crash[/url].
I really want to get to the bottom of this, so I downloaded WhoCrashed to help me get a better view of the situation, and it gave me this:
[code]
On Sun 2011-11-20 06:31:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpipreg.sys (tcpipreg+0x45A1)
Bugcheck code: 0xC4 (0x0, 0x0, 0x0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\tcpipreg.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Registry Compatibility Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver requested a zero-byte pool allocation.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect.
Possibly this problem is caused by another driver on your system which cannot be identified at this time.
[/code]
verifier.exe points to tcpipreg.sys, which only seems to request 0-byte allocs when it's given an IP address with zero length. I've found a key in the registry where the variable IPAddress is set to "", so I did what the internet commanded me to and deleted it. Aside from some network errors on the next reboot, it's working fine, but I'm still worried.
My graphics driver is my prime suspect, because it keeps crashing and restoring. However, I've rolled back and updated a few times the last two weeks, so it doesn't seem to be that.
Are there any more steps I need to take to be sure, or should the removing of a zero-length IP address be enough?
Bump, I guess? Nobody has anything?
Sorry, you need to Log In to post a reply to this thread.
