Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD : IRQL_NOT_LESS_OR_EQUAL Caused By ntoskrnl.exe ( nt+90413 )

28 Feb 2011   #1
MPIXAPP

Windows 7 Home Premium 32bit
 
 
BSOD : IRQL_NOT_LESS_OR_EQUAL Caused By ntoskrnl.exe ( nt+90413 )

Hi ..

This Problem Happens To Me Every Time I Install Windows 7 ..
When I Leave A Download Or Something A BSOD Happens ..
And the blue screen top says IRQL_NOT_LESS_OR_EQUAL ..
IT'S A FRESH INSTALL SO THIS IS NOT FROM A SECURITY PROGRAM !

I Can See It's From The Driver ( Nvidia GeForce FX 5200 ) ..
Because When I Uninstalled The Driver ..

THE BSOD Disappeared ..
THERE IS NO A WINDOWS 7 DRIVER FOR NVIDIA GEFORCE FX 5200 .. AND I TRIED THE VISTA DRIVER AND XP DRIVER .. AND STILL THE BSOD !

Anyway ..

The Dumpfile is attached .. and here it's the analysation ..

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mohamed\Desktop\New folder\022811-29250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is: 
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82813000 PsLoadedModuleList = 0x829535b0
Debug session time: Mon Feb 28 23:34:01.088 2011 (GMT+2)
System Uptime: 0 days 0:31:25.932
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {83be67f0, 2, 1, 828a3413}

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+90413 )

Followup: MachineOwner
---------
I Don't Know What TO DO !!!

Please Help Me .. !!!!!


My System SpecsSystem Spec
.
28 Feb 2011   #2
DeanP

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

The Graphics Card does not look like if it has support for Windows 7. Drivers - Download NVIDIA Drivers
If uninstalling the drivers seem to have the BSOD disappear - then you will need to find a new GPU.

Also, please update these...
Code:
ac97via.sys  Tue Nov 23 09:29:55 2004
nv4_mini.sys  Sat May 17 09:45:57 2008
Note   Note
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Regards...
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {83be67f0, 2, 1, 828a3413}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+271 )

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

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: 83be67f0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 828a3413, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82973700
Unable to read MiSystemVaType memory at 82953100
 83be67f0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmZeroPageThread+271
828a3413 f00fba2800      lock bts dword ptr [eax],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  80d86c5c -- (.trap 0xffffffff80d86c5c)
ErrCode = 00000002
eax=83be67f0 ebx=83be67f0 ecx=84800802 edx=00000000 esi=83be67e8 edi=ffffeeff
eip=828a3413 esp=80d86cd0 ebp=80d86d44 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MmZeroPageThread+0x271:
828a3413 f00fba2800      lock bts dword ptr [eax],0   ds:0023:83be67f0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 828a3413 to 8284bc5b

STACK_TEXT:  
80d86c5c 828a3413 badb0d00 00000000 82c1cba9 nt!KiTrap0E+0x2cf
80d86d44 82997454 00000000 80d86d90 829fc400 nt!MmZeroPageThread+0x271
80d86d50 829fc400 8080a538 bc491a7e 00000000 nt!Phase1Initialization+0x14
80d86d90 8289c969 82997440 8080a538 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmZeroPageThread+271
828a3413 f00fba2800      lock bts dword ptr [eax],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MmZeroPageThread+271

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78a06

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MmZeroPageThread+271

BUCKET_ID:  0xA_nt!MmZeroPageThread+271

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

kd> lmtsmn
start    end        module name
906d7000 906f6000   ac97via  ac97via.sys  Tue Nov 23 09:29:55 2004 (41A24C43)
89232000 8927a000   ACPI     ACPI.sys     Sat Nov 20 21:37:52 2010 (4CE788E0)
89b82000 89bdc000   afd      afd.sys      Sat Nov 20 21:40:00 2010 (4CE78960)
907e9000 907fb000   AgileVpn AgileVpn.sys Tue Jul 14 11:55:00 2009 (4A5BC954)
89384000 8938d000   amdxata  amdxata.sys  Sat Mar 20 05:19:01 2010 (4BA3A3F5)
89358000 89361000   atapi    atapi.sys    Tue Jul 14 11:11:15 2009 (4A5BBF13)
89361000 89384000   ataport  ataport.SYS  Sat Nov 20 21:38:00 2010 (4CE788E8)
89aed000 89af4000   Beep     Beep.SYS     Tue Jul 14 11:45:00 2009 (4A5BC6FC)
89418000 89426000   blbdrive blbdrive.sys Tue Jul 14 11:23:04 2009 (4A5BC1D8)
890be000 890c6000   BOOTVID  BOOTVID.dll  Tue Jul 14 13:04:34 2009 (4A5BD9A2)
92281000 9229a000   bowser   bowser.sys   Tue Jul 14 11:14:21 2009 (4A5BBFCD)
89ac7000 89ae6000   cdrom    cdrom.sys    Sat Nov 20 21:38:09 2010 (4CE788F1)
89108000 891b3000   CI       CI.dll       Sun Nov 21 01:05:17 2010 (4CE7B97D)
89a70000 89a95000   CLASSPNP CLASSPNP.SYS Tue Jul 14 11:11:20 2009 (4A5BBF18)
890c6000 89108000   CLFS     CLFS.SYS     Tue Jul 14 11:11:10 2009 (4A5BBF0E)
89596000 895f3000   cng      cng.sys      Tue Jul 14 11:32:55 2009 (4A5BC427)
907dc000 907e9000   CompositeBus CompositeBus.sys Sat Nov 20 22:50:21 2010 (4CE799DD)
9212e000 9213b000   crashdmp crashdmp.sys Tue Jul 14 11:45:50 2009 (4A5BC72E)
89400000 89418000   dfsc     dfsc.sys     Sat Nov 20 21:42:32 2010 (4CE789F8)
897eb000 897f7000   discache discache.sys Tue Jul 14 11:24:04 2009 (4A5BC214)
89a5f000 89a70000   disk     disk.sys     Tue Jul 14 11:11:28 2009 (4A5BBF20)
9216d000 92191000   Dot4     Dot4.sys     Tue Jul 14 11:45:05 2009 (4A5BC701)
92191000 9219a000   Dot4Prt  Dot4Prt.sys  Sat Nov 20 22:50:05 2010 (4CE799CD)
92160000 9216d000   dot4usb  dot4usb.sys  Tue Jul 14 11:45:03 2009 (4A5BC6FF)
90725000 9073e000   drmk     drmk.sys     Tue Jul 14 12:36:05 2009 (4A5BD2F5)
92146000 9214f000   dump_atapi dump_atapi.sys Tue Jul 14 11:11:15 2009 (4A5BBF13)
9213b000 92146000   dump_dumpata dump_dumpata.sys Tue Jul 14 11:11:16 2009 (4A5BBF14)
9214f000 92160000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 11:12:47 2009 (4A5BBF6F)
9219a000 921a4000   Dxapi    Dxapi.sys    Tue Jul 14 11:25:25 2009 (4A5BC265)
94000000 94017000   dxg      dxg.sys      unavailable (00000000)
9077d000 90788000   fdc      fdc.sys      Tue Jul 14 11:45:45 2009 (4A5BC729)
90772000 9077cc00   fetnd6   fetnd6.sys   Thu Jun 19 23:45:41 2008 (485A46E5)
893c1000 893d2000   fileinfo fileinfo.sys Tue Jul 14 11:21:51 2009 (4A5BC18F)
920fa000 92104000   flpydisk flpydisk.sys Tue Jul 14 11:45:45 2009 (4A5BC729)
8938d000 893c1000   fltmgr   fltmgr.sys   Tue Jul 14 11:11:13 2009 (4A5BBF11)
89601000 8960a000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 11:11:14 2009 (4A5BBF12)
89a2d000 89a5f000   fvevol   fvevol.sys   Sat Nov 20 21:40:22 2010 (4CE78976)
89960000 89991000   fwpkclnt fwpkclnt.sys Sat Nov 20 21:39:08 2010 (4CE7892C)
82c17000 82c4e000   hal      halmacpi.dll Sat Nov 20 21:37:38 2010 (4CE788D2)
921fc000 92281000   HTTP     HTTP.sys     Sat Nov 20 21:40:17 2010 (4CE78971)
89a25000 89a2d000   hwpolicy hwpolicy.sys Sat Nov 20 21:37:35 2010 (4CE788CF)
907aa000 907c2000   i8042prt i8042prt.sys Tue Jul 14 11:11:23 2009 (4A5BBF1B)
9232c000 92344000   idmwfp   idmwfp.sys   Tue Jan 25 03:51:49 2011 (4D3D9205)
89000000 89012000   intelppm intelppm.sys Tue Jul 14 11:11:03 2009 (4A5BBF07)
907cf000 907dc000   kbdclass kbdclass.sys Tue Jul 14 11:11:15 2009 (4A5BBF13)
80bd1000 80bd9000   kdcom    kdcom.dll    Tue Jul 14 13:08:58 2009 (4A5BDAAA)
9073e000 90772000   ks       ks.sys       Sat Nov 20 22:50:17 2010 (4CE799D9)
89583000 89596000   ksecdd   ksecdd.sys   Sat Nov 20 21:38:54 2010 (4CE7891E)
896ff000 89724000   ksecpkg  ksecpkg.sys  Tue Jul 14 11:34:00 2009 (4A5BC468)
921d9000 921e9000   lltdio   lltdio.sys   Tue Jul 14 11:53:18 2009 (4A5BC8EE)
921a4000 921bf000   luafv    luafv.sys    Tue Jul 14 11:15:44 2009 (4A5BC020)
89028000 890ad000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sun Nov 21 01:00:54 2010 (4CE7B876)
980c6000 980d1000   monitor  monitor.sys  Tue Jul 14 11:25:58 2009 (4A5BC286)
907c2000 907cf000   mouclass mouclass.sys Tue Jul 14 11:11:15 2009 (4A5BBF13)
89342000 89358000   mountmgr mountmgr.sys Sat Nov 20 21:38:09 2010 (4CE788F1)
9229a000 922ac000   mpsdrv   mpsdrv.sys   Tue Jul 14 11:52:52 2009 (4A5BC8D4)
922ac000 922cf000   mrxsmb   mrxsmb.sys   Sat Nov 20 21:42:40 2010 (4CE78A00)
922cf000 9230a000   mrxsmb10 mrxsmb10.sys Sat Nov 20 21:44:15 2010 (4CE78A5F)
9230a000 92325000   mrxsmb20 mrxsmb20.sys Sat Nov 20 21:42:47 2010 (4CE78A07)
89b46000 89b51000   Msfs     Msfs.SYS     Tue Jul 14 11:11:26 2009 (4A5BBF1E)
89283000 8928b000   msisadrv msisadrv.sys Tue Jul 14 11:11:09 2009 (4A5BBF0D)
89558000 89583000   msrpc    msrpc.sys    Tue Jul 14 11:11:59 2009 (4A5BBF3F)
897e1000 897eb000   mssmbios mssmbios.sys Tue Jul 14 11:19:25 2009 (4A5BC0FD)
89a15000 89a25000   mup      mup.sys      Tue Jul 14 11:14:14 2009 (4A5BBFC6)
8960a000 896c1000   ndis     ndis.sys     Sat Nov 20 21:39:19 2010 (4CE78937)
90018000 90023000   ndistapi ndistapi.sys Tue Jul 14 11:54:24 2009 (4A5BC930)
9203e000 92060000   ndiswan  ndiswan.sys  Sat Nov 20 23:07:48 2010 (4CE79DF4)
92104000 92115000   NDProxy  NDProxy.SYS  Sat Nov 20 23:07:39 2010 (4CE79DEB)
89be3000 89bf1000   netbios  netbios.sys  Tue Jul 14 11:53:54 2009 (4A5BC912)
89724000 89756000   netbt    netbt.sys    Sat Nov 20 21:39:22 2010 (4CE7893A)
896c1000 896ff000   NETIO    NETIO.SYS    Sat Nov 20 21:40:03 2010 (4CE78963)
89b51000 89b5f000   Npfs     Npfs.SYS     Tue Jul 14 11:11:31 2009 (4A5BBF23)
89bf1000 89bfb000   nsiproxy nsiproxy.sys Tue Jul 14 11:12:08 2009 (4A5BBF48)
82813000 82c17000   nt       ntkrnlmp.exe Sat Nov 20 21:42:46 2010 (4CE78A06)
89429000 89558000   Ntfs     Ntfs.sys     Sat Nov 20 21:39:08 2010 (4CE7892C)
89ae6000 89aed000   Null     Null.SYS     Tue Jul 14 11:11:12 2009 (4A5BBF10)
94c00000 951d4000   nv4_disp nv4_disp.dll unavailable (00000000)
90031000 90671ee0   nv4_mini nv4_mini.sys Sat May 17 09:45:57 2008 (482E0095)
89756000 89775000   pacer    pacer.sys    Tue Jul 14 11:53:58 2009 (4A5BC916)
90792000 907aa000   parport  parport.sys  Tue Jul 14 11:45:34 2009 (4A5BC71E)
892c0000 892d1000   partmgr  partmgr.sys  Sat Nov 20 21:38:14 2010 (4CE788F6)
92325000 9232c000   parvdm   parvdm.sys   Tue Jul 14 11:45:29 2009 (4A5BC719)
8928b000 892b5000   pci      pci.sys      Sat Nov 20 21:37:57 2010 (4CE788E5)
89334000 89342000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 11:11:15 2009 (4A5BBF13)
895f3000 89601000   pcw      pcw.sys      Tue Jul 14 11:11:10 2009 (4A5BBF0E)
92344000 923db000   peauth   peauth.sys   Tue Jul 14 12:35:44 2009 (4A5BD2E0)
906f6000 90725000   portcls  portcls.sys  Tue Jul 14 11:51:00 2009 (4A5BC864)
890ad000 890be000   PSHED    PSHED.dll    Tue Jul 14 13:09:36 2009 (4A5BDAD0)
90000000 90018000   rasl2tp  rasl2tp.sys  Tue Jul 14 11:54:33 2009 (4A5BC939)
92060000 92078000   raspppoe raspppoe.sys Tue Jul 14 11:54:53 2009 (4A5BC94D)
92078000 9208f000   raspptp  raspptp.sys  Tue Jul 14 11:54:47 2009 (4A5BC947)
9208f000 920a6000   rassstp  rassstp.sys  Tue Jul 14 11:54:57 2009 (4A5BC951)
897a0000 897e1000   rdbss    rdbss.sys    Sat Nov 20 21:42:44 2010 (4CE78A04)
89b2e000 89b36000   RDPCDD   RDPCDD.sys   Sat Nov 20 23:22:19 2010 (4CE7A15B)
89b36000 89b3e000   rdpencdd rdpencdd.sys Tue Jul 14 12:01:39 2009 (4A5BCAE3)
89b3e000 89b46000   rdprefmp rdprefmp.sys Tue Jul 14 12:01:41 2009 (4A5BCAE5)
899e8000 89a15000   rdyboost rdyboost.sys Sat Nov 20 22:00:07 2010 (4CE78E17)
921e9000 921fc000   rspndr   rspndr.sys   Tue Jul 14 11:53:20 2009 (4A5BC8F0)
923db000 923e5000   secdrv   secdrv.SYS   Thu Sep 14 01:18:32 2006 (45080528)
90788000 90792000   serenum  serenum.sys  Tue Jul 14 11:45:27 2009 (4A5BC717)
89775000 8978f000   serial   serial.sys   Tue Jul 14 11:45:33 2009 (4A5BC71D)
899e0000 899e8000   spldr    spldr.sys    Tue May 12 04:13:47 2009 (4A084EBB)
980d1000 9813b000   spsys    spsys.sys    Tue May 12 04:37:10 2009 (4A085436)
98054000 980a5000   srv      srv.sys      Sat Nov 20 21:45:29 2010 (4CE78AA9)
98005000 98054000   srv2     srv2.sys     Sat Nov 20 21:44:35 2010 (4CE78A73)
92000000 92021000   srvnet   srvnet.sys   Sat Nov 20 21:44:27 2010 (4CE78A6B)
920a6000 920a7380   swenum   swenum.sys   Tue Jul 14 11:45:08 2009 (4A5BC704)
89816000 89960000   tcpip    tcpip.sys    Sat Nov 20 21:41:36 2010 (4CE789C0)
92021000 9202e000   tcpipreg tcpipreg.sys Sat Nov 20 23:07:13 2010 (4CE79DD1)
89b76000 89b82000   TDI      TDI.SYS      Sat Nov 20 21:39:18 2010 (4CE78936)
89b5f000 89b76000   tdx      tdx.sys      Sat Nov 20 21:39:17 2010 (4CE78935)
8978f000 897a0000   termdd   termdd.sys   Sat Nov 20 23:21:10 2010 (4CE7A116)
94030000 94039000   TSDDD    TSDDD.dll    unavailable (00000000)
893d2000 893f3000   tunnel   tunnel.sys   Sat Nov 20 23:06:40 2010 (4CE79DB0)
920a8000 920b6000   umbus    umbus.sys    Sat Nov 20 23:00:23 2010 (4CE79C37)
9212c000 9212d700   USBD     USBD.SYS     Tue Jul 14 11:51:05 2009 (4A5BC869)
906c8000 906d7000   usbehci  usbehci.sys  Sat Nov 20 22:59:43 2010 (4CE79C0F)
920b6000 920fa000   usbhub   usbhub.sys   Sat Nov 20 23:00:34 2010 (4CE79C42)
9067d000 906c8000   USBPORT  USBPORT.SYS  Sat Nov 20 22:59:49 2010 (4CE79C15)
92115000 9212c000   USBSTOR  USBSTOR.SYS  Sat Nov 20 22:59:48 2010 (4CE79C14)
90672000 9067d000   usbuhci  usbuhci.sys  Tue Jul 14 11:51:10 2009 (4A5BC86E)
892b5000 892c0000   vdrvroot vdrvroot.sys Tue Jul 14 11:46:19 2009 (4A5BC74B)
89af4000 89b00000   vga      vga.sys      Tue Jul 14 11:25:50 2009 (4A5BC27E)
899d0000 899e0000   viaagp   viaagp.sys   Tue Jul 14 11:25:39 2009 (4A5BC273)
8932c000 89334000   viaide   viaide.sys   Tue Jul 14 11:11:20 2009 (4A5BBF18)
89b00000 89b21000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 11:25:49 2009 (4A5BC27D)
892d1000 892e1000   volmgr   volmgr.sys   Sat Nov 20 21:38:06 2010 (4CE788EE)
892e1000 8932c000   volmgrx  volmgrx.sys  Tue Jul 14 11:11:41 2009 (4A5BBF2D)
89991000 899d0000   volsnap  volsnap.sys  Sat Nov 20 21:38:13 2010 (4CE788F5)
89800000 89813000   wanarp   wanarp.sys   Sat Nov 20 23:07:45 2010 (4CE79DF1)
89b21000 89b2e000   watchdog watchdog.sys Tue Jul 14 11:24:10 2009 (4A5BC21A)
891b3000 89224000   Wdf01000 Wdf01000.sys Tue Jul 14 11:11:36 2009 (4A5BBF28)
89224000 89232000   WDFLDR   WDFLDR.SYS   Tue Jul 14 11:11:25 2009 (4A5BBF1D)
89bdc000 89be3000   wfplwf   wfplwf.sys   Tue Jul 14 11:53:51 2009 (4A5BC90F)
941a0000 943ec000   win32k   win32k.sys   unavailable (00000000)
8927a000 89283000   WMILIB   WMILIB.SYS   Tue Jul 14 11:11:22 2009 (4A5BBF1A)
921bf000 921d9000   WudfPf   WudfPf.sys   Sat Nov 20 22:58:55 2010 (4CE79BDF)
980a5000 980c5480   WUDFRd   WUDFRd.sys   Sat Nov 20 22:59:19 2010 (4CE79BF7)

Unloaded modules:
89a95000 89aa2000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
89aa2000 89aad000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000B000
89aad000 89ab6000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
89ab6000 89ac7000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
My System SpecsSystem Spec
Reply

 BSOD : IRQL_NOT_LESS_OR_EQUAL Caused By ntoskrnl.exe ( nt+90413 )




Thread Tools




Similar help and support threads
Thread Forum
BSOD IRQL_NOT_LESS_OR_EQUAL caused by ntoskrnl.exe
Hey guys! First time poster, long time lurker here. The last couple of days I've been ravaged by BSODs. I did a memtest and found out that I had a bad ram stick. I replaced the ram stick and did a clean install of Windows 7 Home Premium x64 and installed my drivers as well as Avast! Antivirus. ...
BSOD Help and Support
BSOD Mostly ntoskrnl.exe IRQL_NOT_LESS_OR_EQUAL
...
BSOD Help and Support
BSOD which seems to be caused by IRQL_NOT_LESS_OR_EQUAL and ntoskrnl.e
Hi All, I have found multiple helpful answers on this forum regarding similar situations yet none that seems to apply to mine specifically. Though I'm sure my dumps will be more helpful than I could ever be, here's what I noticed: 1. the installation of a new external drive (hp 2TB) seems...
BSOD Help and Support
BSOD: IRQL_NOT_LESS_OR_EQUAL with ntoskrnl.exe
My computer crashed with a BSOD while watching a Youtube video. I have not had any BSOD for the past 6 months, nor did I did install any new apps recently. 6 months ago I was experiencing an issue with BSOD as well but when I resitted the memory the issue has disappeared, I do not have mini...
BSOD Help and Support
IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe BSOD
Hello Forum, Forgive me for my initial post being my problem, but the notebook I'm working on is a gift so I have little time to work with it. The Machine is as follows: HP Pavilion dv7 Notebook AMD Turion Ultra Dual-Core M600 4GB Ram running 64 bi
BSOD Help and Support
BSOD: IRQL_NOT_LESS_OR_EQUAL caused by ntoskrnl.exe
Problem: Upon running WhoCrashed Home Edition 2.10 it told me this: On Wed 4/14/2010 11:42:45 PM your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800031ED477) Error: IRQL_NOT_LESS_OR_EQUAL Dump file: ...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:33.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App