BSOD ntoskml.exe+70740 IRQL_NOT_LESS_OR_EQUAL

Hi All, I am newbie submitting to forums - however sometimes read them and now really hope someone can help promptly!?!

I am supporting this E4200 laptop for our CEO and the last 3 months he has had 10 BSOD. I see these via BlueScreenView - however I must admit I do not understand what I can best do from here....

Attached a .doc with various printscreens from BlueScreenView.

Any detailed comments would be greatly appreciated! Many thanks in advance.

Best wishes

Tatia

Hello Tatia

Welcome to Seven Forums :)
Please have a look at his thread as to how to upload your dump files - BSOD - Posting Instructions
The BSOD Squad will require the dump files for analysis.

TIA and regards

Thanks Lomai

I get as far as:

"Windows Explorer will open to your Documents folder" - twice having run the .exe and it said it was nearly finished....

However there is no Windows_NT6_BSOD_jcgriff2 folder in the Documents folder??? I have refreshed and searched for this - but to no avail?

Yours puzzled...

Tatia

Many thanks Tews,

I tried the software for the 3rd time and got to: "Almost finished..." and the same happened ( no new folder seen ).

Anyhow - here is some more info as requested earlier:

Windows 7 Pro
x64
Original installed
OEM
Never reinstalled OS
MS Office 2007, Norton NIS 2011, Vodafone inbuilt SIM
Laptop is 5 months old – fully updated with the latest updates, SPs etc. Strictly business – user runs as a Standard User daily and then I install all updates as the Administrator as per Secunia’s guidance

Attached 2 x attachment: 10xminidump.zip and system_health_report.zip

I REALLY appreciate your prompt help – however please note that from this afternoon ( am already running late!!! ) I am roaming for a few days so I will not easily have access to this forum and his laptop – so please bear with me and understand that I may not be able to report back to you prompt/before early next week - at the very latest.

Many thanks for your co-operation.

I look forward to hearing from you – thanks and best wishes

Tatia

I wonder if we havent missed something. In at least 4 of the 10 a driver (used by Toshiba) WwanUSBmp64.sys was installed and blamed. It also may be responsible for the memory corruption in the other BugChecks.

I will bet that the conflict between the dell driver and the toshiba driver is what caused the crashes. It absolutely must be removed.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidump\060510-21933-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
Debug session time: Sat Jun  5 11:52:42.718 2010 (GMT-4)
System Uptime: 3 days 3:23:01.981
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa800f44c000, 2, 0, fffff88002248d41}

Unable to load image \SystemRoot\system32\DRIVERS\WwanUsbMp64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WwanUsbMp64.sys
*** ERROR: Module load completed but symbols could not be loaded for WwanUsbMp64.sys
Probably caused by : WwanUsbMp64.sys ( WwanUsbMp64+17d41 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa800f44c000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88002248d41, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
 fffffa800f44c000 

CURRENT_IRQL:  2

FAULTING_IP: 
WwanUsbMp64+17d41
fffff880`02248d41 803900          cmp     byte ptr [rcx],0
 
CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Dell.ControlPo

TRAP_FRAME:  fffff80000ba2150 -- (.trap 0xfffff80000ba2150)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffffa800f44c000
rdx=fffffa800f44be00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002248d41 rsp=fffff80000ba22e0 rbp=fffff8800225e510
 r8=0000000000000000  r9=0000000000000000 r10=3a444155432b0a0d
r11=fffffa800f44be00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
WwanUsbMp64+0x17d41:
fffff880`02248d41 803900          cmp     byte ptr [rcx],0 ds:c1b0:fffffa80`0f44c000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002abcb69 to fffff80002abd600

STACK_TEXT:  
fffff800`00ba2008 fffff800`02abcb69 : 00000000`0000000a fffffa80`0f44c000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2010 fffff800`02abb7e0 : 00000000`00000009 00000000`00000004 fffff880`022ca2c0 fffffa80`080b61a0 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2150 fffff880`02248d41 : fffffa80`00000000 fffffa80`65525441 fffff800`02c4cbc0 fffff800`02c37e80 : nt!KiPageFault+0x260
fffff800`00ba22e0 fffffa80`00000000 : fffffa80`65525441 fffff800`02c4cbc0 fffff800`02c37e80 00000000`00000000 : WwanUsbMp64+0x17d41
fffff800`00ba22e8 fffffa80`65525441 : fffff800`02c4cbc0 fffff800`02c37e80 00000000`00000000 fffff880`0223e58c : 0xfffffa80`00000000
fffff800`00ba22f0 fffff800`02c4cbc0 : fffff800`02c37e80 00000000`00000000 fffff880`0223e58c fffffa80`08e3aec0 : 0xfffffa80`65525441
fffff800`00ba22f8 fffff800`02c37e80 : 00000000`00000000 fffff880`0223e58c fffffa80`08e3aec0 00000000`00000200 : nt!NonPagedPoolDescriptor+0x340
fffff800`00ba2300 00000000`00000000 : fffff880`0223e58c fffffa80`08e3aec0 00000000`00000200 fffffa80`08d5a000 : nt!KiInitialPCR+0x180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WwanUsbMp64+17d41
fffff880`02248d41 803900          cmp     byte ptr [rcx],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  WwanUsbMp64+17d41

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WwanUsbMp64

IMAGE_NAME:  WwanUsbMp64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a892046

FAILURE_BUCKET_ID:  X64_0xD1_WwanUsbMp64+17d41

BUCKET_ID:  X64_0xD1_WwanUsbMp64+17d41

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