BSOD while on Skype, IRQL_NOT_LESS_OR_EQUAL 0x0000000a

Hello and welcome to SF :) .

You MSINFO32 is empty due to the WMI service not being active.
Please confirm you have these services running and active:
Security Center, IP Helper, Windows Management Instrumentation.
> Services.msc > hit enter.


Once that is done please upload a new instance of the MSINFO32 file;

Start> Run> Type MSINFO32 then hit [Enter].
In MSINFO32 go to, File> Save> name it your user-name and upload.



The bugchecks seem to be cause by an old Dell OEM driver which I suggest you remove.

Code:

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: 000007fef43bf610, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation
Arg4: fffff80002cd8710, address which referenced memory

Code:

Unable to load image \SystemRoot\system32\DRIVERS\stdflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for stdflt.sys
*** ERROR: Module load completed but symbols could not be loaded for stdflt.sys

Code:

lmvm stdflt
start             end                 module name
fffff880`01941000 fffff880`01949000   stdflt   T (no symbols)           
    Loaded symbol image file: stdflt.sys
    Image path: \SystemRoot\system32\DRIVERS\stdflt.sys
    Image name: stdflt.sys
    Timestamp:        Thu Jul 16 18:36:50 2009

• Driver Reference Table - stdflt.sys

USBSTOR was loaded and unloaded multiple times just prior to the bugcheck, because the MSinfo32
is empty I wasn't able to pinpoint the devices attached but I did find a set of old drivers that needs to be updated or removed.

Code:

fffff880`0734c000 fffff880`0736e000   NisDrvWFP.sy
fffff880`07636000 fffff880`0766c000   WUDFRd.sys
fffff880`07636000 fffff880`0766c000   WUDFRd.sys
fffff880`077cd000 fffff880`077e8000   USBSTOR.SYS
fffff880`08600000 fffff880`08636000   WUDFRd.sys
fffff880`08636000 fffff880`08651000   USBSTOR.SYS
fffff880`0864c000 fffff880`086bd000   spsys.sys
fffff880`08651000 fffff880`08687000   WUDFRd.sys
fffff880`08687000 fffff880`086a2000   USBSTOR.SYS
fffff880`086c8000 fffff880`086e3000   USBSTOR.SYS
fffff880`086c8000 fffff880`086fe000   WUDFRd.sys
fffff880`086e3000 fffff880`08719000   WUDFRd.sys
fffff880`086fe000 fffff880`08719000   USBSTOR.SYS
fffff880`08719000 fffff880`08734000   USBSTOR.SYS
fffff880`08719000 fffff880`0874f000   WUDFRd.sys
fffff880`08734000 fffff880`0876a000   WUDFRd.sys
fffff880`0874f000 fffff880`0876a000   USBSTOR.SYS
fffff880`0876a000 fffff880`08785000   USBSTOR.SYS
fffff880`0876a000 fffff880`087a0000   WUDFRd.sys
fffff880`08785000 fffff880`087bb000   WUDFRd.sys
fffff880`087bb000 fffff880`087d6000   USBSTOR.SYS

Code:

risdpe64 - Wed Jul 01 12:31:57 2009
rimspe64 - Thu Jul 02 02:54:49 2009
rixdpe64 - Sat Jul 04 13:27:00 2009

• Driver Reference Table - risdpe64.sys
• Driver Reference Table - rimspe64.sys
• Driver Reference Table - rixdpe64.sys

Post back with the results!

Thanks for the feedback :) .
You decided to update rather then remove which is fine by me (I would personally remove it though :) ).

Thanks for the MSINFO32 file, hopefully it won't have to be in use .
Keep us posted.

Good news!
I'm happy to hear, you're welcome :) .
For other issues we are here.