BSOD ntoskrnl.exe (nt+0x7CC40) - 0xA


  1. Posts : 3
    Windows 7 Professional x64
       #1

    BSOD ntoskrnl.exe (nt+0x7CC40) - 0xA


    I am experienceing the BSOD very often. More than 15 - 20 times a day.
    Before coming to this site I had already deleted all the files in C:\Windows\minidump to do a clean troubleshooting.
    Then when I got the BSOD the first time I used the http://jcgriff2.com/0x2/Windows_NT6_..._jcgriff2_.exe tool to dump everything.

    I have attached the dmp and perfmon report.

    Following is a report from WhoCrashed

    computer name: MEDIA-PC
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz Intel586, level: 6
    2 logical processors, active mask: 3
    RAM: 4293320704 total
    VM: 2147352576, free: 1951793152


    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Wed 2/22/2012 1:12:44 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\022112-16536-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000280533E)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 2/22/2012 1:12:44 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: rt64win7.sys (Rt64win7+0x10BB8)
    Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000280533E)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\rt64win7.sys
    product: Realtek 8101E/8168/8169 PCI/PCIe Adapters
    company: Realtek Corporation
    description: Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rt64win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver , Realtek Corporation ).
    Google query: rt64win7.sys Realtek Corporation IRQL_NOT_LESS_OR_EQUAL


    Any help is appreciated.
      My Computer


  2. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #2

    I tried running sfc /scannow
    It did not find any errors
    running chkdsk /r /v ... will post results
      My Computer


  3. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #3

    No errors were found with sfc and chkdsk

    Any help???
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Problem devices:
    Code:
    Mass Storage Controller	PCI\VEN_104C&DEV_803B&SUBSYS_9015104D&REV_00\4&32B6E616&0&3AF0	The drivers for this device are not installed.


    The following drivers may be outdated (do not worry about them unless we mention one):
    Code:
    SFEP	fffff880`03e1e000	fffff880`03e20c80	Thu Aug 02 23:35:53 2007 (46b2beb9)	00003282		SFEP.sys
    VSTCNXT6	fffff880`084f9000	fffff880`085c4000	Wed Oct 15 18:52:22 2008 (48f69046)	000b6676		VSTCNXT6.SYS
    VSTAZL6	fffff880`05200000	fffff880`05252000	Wed Oct 15 18:53:42 2008 (48f69096)	0004c45d		VSTAZL6.SYS
    VSTDPV6	fffff880`0823e000	fffff880`083b2000	Wed Oct 15 18:57:45 2008 (48f69189)	001727ae		VSTDPV6.SYS
    atikmdag	fffff880`04856000	fffff880`04f0a000	Mon Dec 01 14:04:09 2008 (49345149)	004c9c54		atikmdag.sys
    Rt64win7	fffff880`0436c000	fffff880`0439e000	Thu Feb 26 02:04:13 2009 (49a65b0d)	0002eb30	None	Rt64win7.sys
    netw5v64	fffff880`03e31000	fffff880`0436c000	Thu Mar 26 10:21:24 2009 (49cbab84)	00533de3		netw5v64.sys


    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\rk7417\Windows_NT6_BSOD_jcgriff2\022112-16536-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`0284c000 PsLoadedModuleList = 0xfffff800`02a91670
    Debug session time: Tue Feb 21 18:12:44.994 2012 (UTC - 7:00)
    System Uptime: 0 days 0:49:02.695
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {8, 2, 0, fffff8000280533e}
    
    Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys ( Rt64win7+10bb8 )
    
    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: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff8000280533e, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afb100
     0000000000000008 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    hal!HalpDmaFreeMapRegisters+1a
    fffff800`0280533e 488b5a08        mov     rbx,qword ptr [rdx+8]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88008dbd840 -- (.trap 0xfffff88008dbd840)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88008dbd970 rbx=0000000000000000 rcx=fffffa8005e0c1b8
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000280533e rsp=fffff88008dbd9d0 rbp=0000000000000b00
     r8=fffff88008dbd970  r9=fffff8000282fc60 r10=0000000000000a4a
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac po nc
    hal!HalpDmaFreeMapRegisters+0x1a:
    fffff800`0280533e 488b5a08        mov     rbx,qword ptr [rdx+8] ds:00000000`00000008=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800028c81e9 to fffff800028c8c40
    
    STACK_TEXT:  
    fffff880`08dbd6f8 fffff800`028c81e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08dbd700 fffff800`028c6e60 : fffffa80`03eaa420 00000000`000007ff fffffa80`0645ed70 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`08dbd840 fffff800`0280533e : fffffa80`040164e0 fffffa80`040164e0 fffffa80`05f43100 00000000`00000001 : nt!KiPageFault+0x260
    fffff880`08dbd9d0 fffff800`02807b82 : fffffa80`05e0c140 00000000`00000000 fffffa80`05e0c140 00000000`000005e3 : hal!HalpDmaFreeMapRegisters+0x1a
    fffff880`08dbda00 fffff800`02807825 : fffffa80`05e7d140 00000000`00000b90 00000000`00000000 fffffa80`04137b50 : hal!IoFreeMapRegisters+0x62
    fffff880`08dbda70 fffff880`014be831 : fffffa80`04137a80 fffffa80`04137950 fffffa80`05332ab0 fffffa80`040164e0 : hal!HalPutScatterGatherList+0xd5
    fffff880`08dbdad0 fffff880`0437cbb8 : fffff800`02a69201 fffffa80`05332ab0 00000000`00000000 fffff800`02a69201 : ndis!NdisMFreeNetBufferSGList+0x31
    fffff880`08dbdb10 fffff800`02a69201 : fffffa80`05332ab0 00000000`00000000 fffff800`02a69201 00000000`00000000 : Rt64win7+0x10bb8
    fffff880`08dbdb18 fffffa80`05332ab0 : 00000000`00000000 fffff800`02a69201 00000000`00000000 fffff880`08dbdc00 : nt!ExpThreadSetManagerShutdownEvent+0x1
    fffff880`08dbdb20 00000000`00000000 : fffff800`02a69201 00000000`00000000 fffff880`08dbdc00 00000000`00000001 : 0xfffffa80`05332ab0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Rt64win7+10bb8
    fffff880`0437cbb8 ??              ???
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  Rt64win7+10bb8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Rt64win7
    
    IMAGE_NAME:  Rt64win7.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49a65b0d
    
    FAILURE_BUCKET_ID:  X64_0xA_Rt64win7+10bb8
    
    BUCKET_ID:  X64_0xA_Rt64win7+10bb8
    
    Followup: MachineOwner
    ---------
    Caused by Rt64win7.sys which is your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC and should be updated from Realtek .



    What Sony VAIO model do you have so I can help you update the important drivers listed as outdated?

    SFEP.sys is a big one (and you probably won't find the update for your model through your model's support page). Your wireless and graphics card drivers also need to be updated.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 15:26.
Find Us