WinXP BSOD IRQL_NOT_LESS_OR_EQUAL

[Sarge]

The analyze command said this

IRQL_NOT_LESS_OR_EQUAL (a)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If a kernel debugger is available get the stack backtrace.

Now how do I know which driver is causing this. :huh:

 

[booo]

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 003f0001, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80502000, address which referenced memory

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: snpstd3

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  413fec72

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 003f0001 

CURRENT_IRQL:  1c

FAULTING_IP: 
nt+2b000
80502000 8916            mov     dword ptr [esi],edx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from 80502259 to 80502000

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b9bf0c0c 80502259 00000000 b9bf0c28 00000000 nt+0x2b000
b9bf0c38 804f9f92 00000000 00000000 88e9a008 nt+0x2b259
b9bf0c4c 804f4a7e b9bf0cd8 00000000 00000000 nt+0x22f92
b9bf0ca8 804febb5 88e9a048 b9bf0cf4 b9bf0ce8 nt+0x1da7e
b9bf0cf8 80502b35 00000000 00000000 00000000 nt+0x27bb5
b9bf0d38 b7392301 00000000 00000000 00000000 nt+0x2bb35
b9bf0da8 b7392bbf 805ce794 895265e8 00000000 snpstd3+0x26301
b9bf0ddc 805450ce b7392bb2 895265e8 00000000 snpstd3+0x26bbf
00000000 00000000 00000000 00000000 00000000 nt+0x6e0ce
STACK_COMMAND:  kb

FOLLOWUP_IP: 
snpstd3+26301
b7392301 ??              ???

SYMBOL_STACK_INDEX:  6

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  snpstd3.sys

SYMBOL_NAME:  snpstd3+26301

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

see, its obvious, the driver snpstd3.sys is causing the crash.

IMAGE_NAME:  snpstd3.sys

now you gotta uninstall this one.

this site tells that its some camera driver.
snpstd3.sys on Spyware-Net

now open regedit
1. Win+R(opens run dialog)->Type Regedit
2. goto "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" in the left tree.
3. press f3 to start search and search for "snpstd3.sys"
4. you should find that string in the right pane.
5. delete the entire tree node in the left tree which has this sys file. (basically we are trying to remove the driver from the sytem's services. drivers are services which are not shown in the computer management.)

ciao

 

[Sarge]

Yes indeed .. I checked out which driver my IBall Robo 351 USB Camera is using and its snpstd3.sys

Will uninstalling or disabling this device do the trick ?

 

[booo]

if you can uninstall the driver and get a newer stable driver... nothing like it.

if you cant then just remove the driver from registry.

 

[Sarge]

Seems to work .. havent had the error for quite some time.

Also the driver was newer one downloaded from their site.

Guess the older one is better.

 

[Sarge]

Its been a week .. no errors at all .. also random screen freezes have also stopped.

Thanx a lot.

 

[booo]

see, analyzing a bsod is easy. ppl have many misconceptions and always think that ram/mobo etc... are faulty which is usually not.
IMHO installing windbg is easier than ripping the box open and doing trial and error methods.