Solved

Blue Screen

Posted on 2012-03-14
3
739 Views
Last Modified: 2012-04-03
0x00000000A (0x00000016 0x00000002 0x82E88f61 0x0000000

Please take a look at the mini dump files and see if you can tell me what the problem was.
031412-23540-01.dmp
WER-132803-0.sysdata.xml
0
Comment
Question by:tfgeorge
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 4

Accepted Solution

by:
sivanov earned 500 total points
ID: 37719806
looks like a driver issue:


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


Loading Dump File [E:\031412-23540-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x82e51000 PsLoadedModuleList = 0x82f9a4d0
Debug session time: Wed Mar 14 10:16:24.530 2012 (GMT+2)
System Uptime: 0 days 9:48:51.888
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {16, 2, 0, 82e88f61}

*** WARNING: Unable to verify timestamp for NWVNdis.sys
*** ERROR: Module load completed but symbols could not be loaded for NWVNdis.sys
Probably caused by : NWVNdis.sys ( NWVNdis+13a1f )

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

1: 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: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82e88f61, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fba848
Unable to read MiSystemVaType memory at 82f99e20
 00000016

CURRENT_IRQL:  2

FAULTING_IP:
nt!KiSignalNotificationObject+13
82e88f61 807f1601        cmp     byte ptr [edi+16h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  8f07320c -- (.trap 0xffffffff8f07320c)
ErrCode = 00000000
eax=88df8bac ebx=00000000 ecx=00000002 edx=00010202 esi=88df8bb4 edi=00000000
eip=82e88f61 esp=8f073280 ebp=8f07328c iopl=0         nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
nt!KiSignalNotificationObject+0x13:
82e88f61 807f1601        cmp     byte ptr [edi+16h],1       ds:0023:00000016=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e88f61 to 82e925fb

STACK_TEXT:  
8f07320c 82e88f61 badb0d00 00010202 8f07325c nt!KiTrap0E+0x2cf
8f07328c 82ec855d 807c3120 8f07337b 8ef65c83 nt!KiSignalNotificationObject+0x13
8f0732b4 82e88681 88df8bac 00000000 00000000 nt!KeSetEvent+0x98
8f0732e4 8ef61a1f 88df8ba4 8f07338c 00000018 nt!IoReleaseRemoveLockEx+0xdf
WARNING: Stack unwind information not available. Following frames may be wrong.
8f0732f8 8ef579f2 88df8ba4 8f07338c 88caeca8 NWVNdis+0x13a1f
8f073380 8b676f0f 88df8000 fc010209 8f07394c NWVNdis+0x99f2
8f0733bc 8b67236c 889360e0 009ee988 889360e0 ndis!ndisMOidRequestToRequest+0x213
8f073404 8b61ece3 009360e0 c0000001 88bf6ce8 ndis!ndisMDoOidRequest+0x3e2
8f07342c 8b61e7ff 00000000 899ee988 88bfc940 ndis!ndisFQueueRequestOnNext+0x21e
8f073494 907a34fb 88bf6ce8 899ee988 82e1d7a0 ndis!NdisFOidRequest+0x181
8f0734b4 8b672961 00000000 88e21810 00000000 vpcnfltr!FilterOidRequest+0xc1
8f073514 8b61ec5c 00bf6ce8 c0000001 88c09830 ndis!ndisFDoOidRequest+0x1a2
8f07353c 8b61e7ff 00000000 88e21810 88e21890 ndis!ndisFQueueRequestOnNext+0x197
8f0735a4 90787086 88c09830 88e21810 82e1d7a0 ndis!NdisFOidRequest+0x181
8f0735c4 8b672961 88c07810 856202f8 00000000 pacer!PcFilterRequest+0x78
8f073624 8b61ec5c 00c09830 c0000001 88c0a830 ndis!ndisFDoOidRequest+0x1a2
8f07364c 8b61e7ff 00000000 856202f8 88c08818 ndis!ndisFQueueRequestOnNext+0x197
8f0736b4 9077bb22 88c0a830 856202f8 82e1d7a0 ndis!NdisFOidRequest+0x181
8f0736d4 8b672961 88c08818 8f0737fc 00000000 wfplwf!FilterOidRequest+0x50
8f073734 8b61d799 00c0a830 889360e0 8f0737fc ndis!ndisFDoOidRequest+0x1a2
8f073760 8b683602 889360e0 8f0737fc 00000000 ndis!ndisQueueRequestOnTop+0x224
8f0737d4 8b683686 88c0faa8 8f0737fc 8f0738a0 ndis!ndisMOidRequest+0x1dd
8f0737e4 8b8b07a6 88c0faa8 8f0737fc c0000056 ndis!NdisOidRequest+0xf
8f0738a0 8b8b0a29 88bfa860 00000000 fc010209 tcpip!FlpNdisRequestUnderReference+0x7d
8f0738c8 8b8b0acb 88bfa860 00000000 fc010209 tcpip!FlpNdisRequest+0x34
8f0738ec 8b8b0aa1 8f073910 8f073990 8f073924 tcpip!FlpQueryOid+0x20
8f0738fc 8b8ae772 8f073910 88c01810 88df8554 tcpip!FlQueryInterface+0x5d
8f073924 8b8afe8a 88c02bc0 00000007 fc010209 tcpip!IppQueryInterfaceProperty+0xc3
8f073994 8b6d82b4 8f0739e0 00000040 88df8000 tcpip!IpGetAllSubInterfaceParameters+0x184
8f073a4c 90612ba1 88df8000 1f665a0d 0000003c NETIO!NsiEnumerateObjectsAllParametersEx+0x4e6
8f073ac0 90613efc 88df803c 00000000 88df8054 nsiproxy!NsippEnumerateObjectsAllParameters+0xeb
8f073ae4 90613fe5 896c8801 00000000 890cb470 nsiproxy!NsippDispatchDeviceControl+0x78
8f073afc 82e8858e 85e78a18 896c8878 896c8878 nsiproxy!NsippDispatch+0x33
8f073b14 8307ba49 890cb470 896c8878 896c88e8 nt!IofCallDriver+0x63
8f073b34 8307ec1b 85e78a18 890cb470 00000000 nt!IopSynchronousServiceTail+0x1f8
8f073bd0 830c54b4 85e78a18 896c8878 00000000 nt!IopXxxControlFile+0x6aa
8f073c04 82e8f21a 00000128 00000ae4 00000000 nt!NtDeviceIoControlFile+0x2a
8f073c04 77a97094 00000128 00000ae4 00000000 nt!KiFastCallEntry+0x12a
03a8fc14 00000000 00000000 00000000 00000000 0x77a97094


STACK_COMMAND:  kb

FOLLOWUP_IP:
NWVNdis+13a1f
8ef61a1f ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NWVNdis+13a1f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NWVNdis

IMAGE_NAME:  NWVNdis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4caaac27

FAILURE_BUCKET_ID:  0xA_NWVNdis+13a1f

BUCKET_ID:  0xA_NWVNdis+13a1f

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

1: 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: 00000016, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 82e88f61, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fba848
Unable to read MiSystemVaType memory at 82f99e20
 00000016

CURRENT_IRQL:  2

FAULTING_IP:
nt!KiSignalNotificationObject+13
82e88f61 807f1601        cmp     byte ptr [edi+16h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  8f07320c -- (.trap 0xffffffff8f07320c)
ErrCode = 00000000
eax=88df8bac ebx=00000000 ecx=00000002 edx=00010202 esi=88df8bb4 edi=00000000
eip=82e88f61 esp=8f073280 ebp=8f07328c iopl=0         nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
nt!KiSignalNotificationObject+0x13:
82e88f61 807f1601        cmp     byte ptr [edi+16h],1       ds:0023:00000016=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e88f61 to 82e925fb

STACK_TEXT:  
8f07320c 82e88f61 badb0d00 00010202 8f07325c nt!KiTrap0E+0x2cf
8f07328c 82ec855d 807c3120 8f07337b 8ef65c83 nt!KiSignalNotificationObject+0x13
8f0732b4 82e88681 88df8bac 00000000 00000000 nt!KeSetEvent+0x98
8f0732e4 8ef61a1f 88df8ba4 8f07338c 00000018 nt!IoReleaseRemoveLockEx+0xdf
WARNING: Stack unwind information not available. Following frames may be wrong.
8f0732f8 8ef579f2 88df8ba4 8f07338c 88caeca8 NWVNdis+0x13a1f
8f073380 8b676f0f 88df8000 fc010209 8f07394c NWVNdis+0x99f2
8f0733bc 8b67236c 889360e0 009ee988 889360e0 ndis!ndisMOidRequestToRequest+0x213
8f073404 8b61ece3 009360e0 c0000001 88bf6ce8 ndis!ndisMDoOidRequest+0x3e2
8f07342c 8b61e7ff 00000000 899ee988 88bfc940 ndis!ndisFQueueRequestOnNext+0x21e
8f073494 907a34fb 88bf6ce8 899ee988 82e1d7a0 ndis!NdisFOidRequest+0x181
8f0734b4 8b672961 00000000 88e21810 00000000 vpcnfltr!FilterOidRequest+0xc1
8f073514 8b61ec5c 00bf6ce8 c0000001 88c09830 ndis!ndisFDoOidRequest+0x1a2
8f07353c 8b61e7ff 00000000 88e21810 88e21890 ndis!ndisFQueueRequestOnNext+0x197
8f0735a4 90787086 88c09830 88e21810 82e1d7a0 ndis!NdisFOidRequest+0x181
8f0735c4 8b672961 88c07810 856202f8 00000000 pacer!PcFilterRequest+0x78
8f073624 8b61ec5c 00c09830 c0000001 88c0a830 ndis!ndisFDoOidRequest+0x1a2
8f07364c 8b61e7ff 00000000 856202f8 88c08818 ndis!ndisFQueueRequestOnNext+0x197
8f0736b4 9077bb22 88c0a830 856202f8 82e1d7a0 ndis!NdisFOidRequest+0x181
8f0736d4 8b672961 88c08818 8f0737fc 00000000 wfplwf!FilterOidRequest+0x50
8f073734 8b61d799 00c0a830 889360e0 8f0737fc ndis!ndisFDoOidRequest+0x1a2
8f073760 8b683602 889360e0 8f0737fc 00000000 ndis!ndisQueueRequestOnTop+0x224
8f0737d4 8b683686 88c0faa8 8f0737fc 8f0738a0 ndis!ndisMOidRequest+0x1dd
8f0737e4 8b8b07a6 88c0faa8 8f0737fc c0000056 ndis!NdisOidRequest+0xf
8f0738a0 8b8b0a29 88bfa860 00000000 fc010209 tcpip!FlpNdisRequestUnderReference+0x7d
8f0738c8 8b8b0acb 88bfa860 00000000 fc010209 tcpip!FlpNdisRequest+0x34
8f0738ec 8b8b0aa1 8f073910 8f073990 8f073924 tcpip!FlpQueryOid+0x20
8f0738fc 8b8ae772 8f073910 88c01810 88df8554 tcpip!FlQueryInterface+0x5d
8f073924 8b8afe8a 88c02bc0 00000007 fc010209 tcpip!IppQueryInterfaceProperty+0xc3
8f073994 8b6d82b4 8f0739e0 00000040 88df8000 tcpip!IpGetAllSubInterfaceParameters+0x184
8f073a4c 90612ba1 88df8000 1f665a0d 0000003c NETIO!NsiEnumerateObjectsAllParametersEx+0x4e6
8f073ac0 90613efc 88df803c 00000000 88df8054 nsiproxy!NsippEnumerateObjectsAllParameters+0xeb
8f073ae4 90613fe5 896c8801 00000000 890cb470 nsiproxy!NsippDispatchDeviceControl+0x78
8f073afc 82e8858e 85e78a18 896c8878 896c8878 nsiproxy!NsippDispatch+0x33
8f073b14 8307ba49 890cb470 896c8878 896c88e8 nt!IofCallDriver+0x63
8f073b34 8307ec1b 85e78a18 890cb470 00000000 nt!IopSynchronousServiceTail+0x1f8
8f073bd0 830c54b4 85e78a18 896c8878 00000000 nt!IopXxxControlFile+0x6aa
8f073c04 82e8f21a 00000128 00000ae4 00000000 nt!NtDeviceIoControlFile+0x2a
8f073c04 77a97094 00000128 00000ae4 00000000 nt!KiFastCallEntry+0x12a
03a8fc14 00000000 00000000 00000000 00000000 0x77a97094


STACK_COMMAND:  kb

FOLLOWUP_IP:
NWVNdis+13a1f
8ef61a1f ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NWVNdis+13a1f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NWVNdis

IMAGE_NAME:  NWVNdis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4caaac27

FAILURE_BUCKET_ID:  0xA_NWVNdis+13a1f

BUCKET_ID:  0xA_NWVNdis+13a1f

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

1: kd> lmvm NWVNdis
start    end        module name
8ef4e000 8efa8000   NWVNdis  T (no symbols)          
    Loaded symbol image file: NWVNdis.sys
    Image path: \SystemRoot\system32\DRIVERS\NWVNdis.sys
    Image name: NWVNdis.sys
    Timestamp:        Tue Oct 05 07:40:07 2010 (4CAAAC27)
    CheckSum:         0006125A
    ImageSize:        0005A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmvm NWVNdis
start    end        module name
8ef4e000 8efa8000   NWVNdis  T (no symbols)          
    Loaded symbol image file: NWVNdis.sys
    Image path: \SystemRoot\system32\DRIVERS\NWVNdis.sys
    Image name: NWVNdis.sys
    Timestamp:        Tue Oct 05 07:40:07 2010 (4CAAAC27)
    CheckSum:         0006125A
    ImageSize:        0005A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


search in google show that NWVNdis.sys is part from :
Novatel_Wireless_ NWADI\NOVATEL_WIRELESS-VSCR_1410_4100\1&79F5D87&0&564

check on the site for something newer ?
http://www.novatelwireless.com/index.php?option=com_content&view=article&id=165&Itemid=191

or check on the vendor of the PC site ..was it lenovo ?
0
 
LVL 1

Author Comment

by:tfgeorge
ID: 37720234
Panasonic toughbook 31
0
 
LVL 4

Expert Comment

by:sivanov
ID: 37723739
Please check where you will find the most updated driver for yout 3g/USMT device from Novatel

http://www.nvtl.com/

http://www.panasonic.com/business/toughbook/computer-support-search-downloads.asp


or if you do not use it - simply unsintall the driver/3g software (something like Cingular Novalte ...)
0

Featured Post

[Live Webinar] The Cloud Skills Gap

As Cloud technologies come of age, business leaders grapple with the impact it has on their team's skills and the gap associated with the use of a cloud platform.

Join experts from 451 Research and Concerto Cloud Services on July 27th where we will examine fact and fiction.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ever notice how you can't use a new drive in Windows without having Windows assigning a Disk Signature?  Ever have a signature collision problem (especially with Virtual Machines?)  This article is intended to help you understand what's going on and…
It’s been over a month into 2017, and there is already a sophisticated Gmail phishing email making it rounds. New techniques and tactics, have given hackers a way to authentically impersonate your contacts.How it Works The attack works by targeti…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question