Windows 7 Forums


Windows 7: BSOD about once a week, ntoskrnl.exe

09 Sep 2011   #1

Windows 7 Home Premium 64 bit
 
 
BSOD about once a week, ntoskrnl.exe

A friend of mine has a brand new Dell Inspiron 620 with OEM 64 bit Windows 7 Home Premium. She is getting BSOD about once a week, usually when not using her computer. Her printer (Epson Stylus CX4800) is old so I tried updating the printer driver - still gets BSOD.

I've attached the zip file specified in posting directions, let me know if you need anything else. Any help greatly appreciated!

Thanks,
JG

My System SpecsSystem Spec

09 Sep 2011   #2

Windows 7 Ultimate x64
L.A.
 
 

Get rid of Symantec Software and use MSE..
Norton Removal tool: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\bsod files\Windows_NT6_BSOD_jcgriff2\081711-17674-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c8f670
Debug session time: Wed Aug 17 17:11:21.970 2011 (UTC - 6:00)
System Uptime: 0 days 8:44:15.813
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002ace6ec}

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

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: 0000000000000000, 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 (only on chips which support this level of status)
Arg4: fffff80002ace6ec, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf9100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`02ace6ec f00fba2e07      lock bts dword ptr [rsi],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009e6d80 -- (.trap 0xfffff880009e6d80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000001ec481 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ace6ec rsp=fffff880009e6f10 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff880009e9180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x13c:
fffff800`02ace6ec f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ac61e9 to fffff80002ac6c40

STACK_TEXT:  
fffff880`009e6c38 fffff800`02ac61e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009e6c40 fffff800`02ac4e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009e6d80 fffff800`02ace6ec : fffffa80`085c7ed0 fffff880`0149319a 00000000`00000001 00000000`abababab : nt!KiPageFault+0x260
fffff880`009e6f10 fffff880`016f1982 : 00000000`00000000 fffffa80`00000000 fffff880`009e6f00 00000000`00000000 : nt!KeWaitForSingleObject+0x13c
fffff880`009e6fb0 fffff880`01b086d1 : 00000000`00000000 00000000`00000088 00000000`00000001 00000000`00000000 : ndis!NdisWaitEvent+0x32
fffff880`009e6ff0 00000000`00000000 : 00000000`00000088 00000000`00000001 00000000`00000000 fffff880`014283e0 : scmndisp+0x16d1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
scmndisp+16d1
fffff880`01b086d1 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  scmndisp+16d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: scmndisp

IMAGE_NAME:  scmndisp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45add4b3

FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1

BUCKET_ID:  X64_0xA_scmndisp+16d1

Followup: MachineOwner
---------
My System SpecsSystem Spec
09 Sep 2011   #3

Windows 7 Professional x64
Rednecksville
 
 

Hmm, it seems scmndisp.sys is the cause; Symantec is probably unrelated. scmndisp.sys is the driver for your Netgear wireless adapter. Try installing the latest updates from here: WNA3100 Software Version 1.1.3.22
Code:
scmndisp.sys            Wed Jan 17 02:48:03 2007 (45ADD4B3)
If the BSODs persist after that, go ahead and remove Symantec as suggested.

...Summary of the dumps:
Code:

Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Sep  9 11:08:15.377 2011 (UTC - 4:00)
System Uptime: 0 days 1:17:48.595
*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
Probably caused by : scmndisp.sys ( scmndisp+16d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
.


09 Sep 2011   #4

Windows 7 Home Premium 64 bit
 
 

Thank you! I will update the wireless adapter driver and let you know in a couple weeks if that solved the problem.

JG
My System SpecsSystem Spec
13 Oct 2011   #5

Windows 7 Home Premium 64 bit
 
 

Updating the driver for the Netgear wireless adapter didn't fix the problem so I replaced it with a Dlink DWA-125 adapter and there have been no more BSODs.

Thanks again for your help!
JG
My System SpecsSystem Spec
13 Oct 2011   #6

Windows 7 Professional x64
Rednecksville
 
 

Glad to hear it!
My System SpecsSystem Spec
Reply

 BSOD about once a week, ntoskrnl.exe problems?



Thread Tools



Similar help and support threads for: BSOD about once a week, ntoskrnl.exe
Thread Forum
BSOD All week. BSOD Help and Support
BSOD playing bf3, hal.dll hal.dll+12a3b , ntoskrnl.exe ntoskrnl.exe+18 BSOD Help and Support
BSOD Once a week BSOD Help and Support
Solved BSOD ntoskrnl.exe+26ee0 ntoskrnl.exe+7cc40 BSOD Help and Support
BSOD once a week BSOD Help and Support


All times are GMT -5. The time now is 01:25 AM.


Seven Forums Android App Seven Forums IOS App Follow us on Facebook

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
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32