BSOD ntoskrnl.exe: When browsing folders networked through Ethernet PC-to-PC

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by gggirlgeek, Apr 29, 2012.

  1. gggirlgeek

    gggirlgeek New Member

    Joined:
    Apr 29, 2012
    Messages:
    2
    Likes Received:
    0
    Hello,

    I am consistently getting a BSOD on my new system build (Win7x64SP1.) It happens only when I browse my network folders while connected to my other desktop (Win7x86SP1) though ethernet (no router.) In this configuration both computers have their own wifi adapters for Internet connectivity to the apartment building's router. I have also tried sharing the Internet connection with one and the same thing happens. Browsing either mapped drives or network shares produces the same result. I detached all other external hardware to test as well.

    The minidump refers to ntoskrnl.exe

    It doesn't happen right away. Sometimes it's within 5 minutes, sometimes after an hour or two. I get no other BSODs at all.

    If I network the two computers over a wifi adhoc, or through the landlord's router no BSOD happens. I can browse my home netowork, public network, mapped drives, whatever. It also does not happen when the ethernet NIC is connected to the router. I don't want to network through the loandlord's router for obvious reasons. Adhoc networking is a PITA and never retains the settings.

    I built this system on 3/24/12 so all drivers are the newest. My memtests come out fine. (BTW my ram modules in the attached screenshots are 4 identical modules, so the specs are the same for all.) See my profile for system details. The Bios settings are not OC'd, and are default as much as possible.

    The one thing I haven't tested yet is disabling both antivirus programs on the computers. The BSOD computer (the new one) has AVG 2012, and the other has Avast.

    Oh, and I am using a different ethernet cable for the connection to the router than with the connection between the 2 computers (the one where no BSOD's happen is running outside so I really don't want to undo all the work.) I haven't tried borrowing another cable for testing.

    Thanks in advance!
     

    Attached Files:

    #1 gggirlgeek, Apr 29, 2012
    Last edited: Apr 29, 2012
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Well you're on the right track.
    The dump files are definitely trapping network issues
    My guess would be AVG. So try it without it. You really can't disable it completely so uninstall it using the program's own uninstaller or the programs and features applet in the control panel and follow that up by using this proprietary vendor specific removal tool AVG Download tools and utilities (get the correct version for your architecture) and see how it goes.
    DUMP FILE:
    Code:
    BugCheck 7F, {8, 80050033, 406f8, fffff80002e8329e}
    
    Unable to load image avgtdia.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]avgtdia.sys[/B][/U][/COLOR]
    *** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]avgtdia.sys[/B][/U][/COLOR]
    Probably caused by : tcpip.sys ( tcpip!WfpAuditEventGeneral+1da )
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050033
    Arg3: 00000000000406f8
    Arg4: fffff80002e8329e
    BUGCHECK_STR:  0x7f_8
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    LAST_CONTROL_TRANSFER:  from fffff80002edfbe9 to fffff80002ee0640
    STACK_TEXT:  
    fffff800`047d9d28 fffff800`02edfbe9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`047d9d30 fffff800`02ede0b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`047d9e70 fffff800`02e8329e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0757cf50 fffff880`01b1623a : 00000000`00000007 00000000`00000011 fffff880`0757e1a0 00000000`00000000 : nt!SeReportSecurityEventWithSubCategory+0x9e
    fffff880`0757d3e0 fffff880`01b169a1 : 00000000`0000002c 00000000`00000000 00000000`00003900 00000000`00003912 : tcpip!WfpAuditEventGeneral+0x1da
    fffff880`0757d860 fffff880`01b16c8c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IndicateDropAudit+0x341
    fffff880`0757dab0 fffff880`01b16e79 : 00000000`00000000 00000000`00000000 fffffa80`04514040 fffffa80`04514040 : tcpip!ShimIndicateDiscard+0xac
    fffff880`0757dd20 fffff880`01b628af : fffff880`0757e508 fffffa80`09c0c7b0 fffff880`0757e1a0 fffff880`0757ded8 : tcpip!WfpShimIndicateDiscardGeneral+0x99
    fffff880`0757dd90 fffff880`01b2a6f8 : fffffa80`09b9f010 fffff880`0757ec18 fffff880`01c287a0 fffff880`0757ecf0 : tcpip!WfpAleClassify+0xdf
    fffff880`0757dde0 fffff880`01b29a88 : 00000000`00000000 00000000`00000000 fffffa80`09b9f010 00000000`00000000 : tcpip!WfpAlepAuthorizeReceive+0x818
    fffff880`0757e410 fffff880`01b28a2c : 00000000`00000000 fffffa80`0000002c 00000000`0000000b fffffa80`073519a0 : tcpip!WfpAleAuthorizeReceive+0x2e8
    fffff880`0757e6f0 fffff880`01b6245e : 00000000`00000000 fffff880`0757ebd0 fffff880`0757eb68 00000000`00000006 : tcpip!WfpAleConnectAcceptIndicate+0x29c
    fffff880`0757e7e0 fffff880`01b63087 : 00000000`00000000 00000000`00000001 00000000`0000bd01 00000000`00000000 : tcpip!ProcessALEForTransportPacket+0x5fe
    fffff880`0757ea50 fffff880`01b407d1 : 00000000`00000000 00000000`00000000 0000000b`00000000 00000000`00000010 : tcpip!WfpProcessInTransportStackIndication+0x7b7
    fffff880`0757ef40 fffff880`01b15df9 : fffffa80`087e2440 fffffa80`0454e8d0 00000000`00000000 00000000`00000002 : tcpip!InetInspectReceiveDatagram+0x121
    fffff880`0757f000 fffff880`01b15ac4 : fffffa80`07ace6e0 fffffa80`087e2440 fffffa80`07e6dd00 00000000`00000000 : tcpip!RawBeginMessageIndication+0x69
    fffff880`0757f0d0 fffff880`01b1ddf2 : fffffa80`00000000 fffffa80`07ace6e0 fffffa80`00000006 fffff880`0757f398 : tcpip!RawDeliverDatagrams+0x124
    fffff880`0757f290 fffff880`01b3b197 : 00000000`00000000 00000000`00000000 fffffa80`0454e820 fffffa80`0454e8d0 : tcpip!RawReceiveDatagrams+0x142
    fffff880`0757f390 fffff880`01b3acaa : 00000000`00000000 fffff880`01c4f9a0 fffff880`0757f540 00000000`00000000 : tcpip!IppDeliverListToProtocol+0xf7
    fffff880`0757f450 fffff880`01b3a4a4 : fffff880`018bd110 00000000`00000002 00000000`00000000 00000000`00000000 : tcpip!IppProcessDeliverList+0x5a
    fffff880`0757f4f0 fffff880`01b1d17f : fffff880`01c4f9a0 fffff880`00000000 00000000`00000000 fffff880`0757f688 : tcpip!IppReceiveHeaderBatch+0x435
    fffff880`0757f5d0 fffff880`01b1d7e4 : 00000000`00000001 fffffa80`087e2440 fffffa80`04540b48 00000000`00000000 : tcpip!IppLoopbackTransmit+0x38f
    fffff880`0757f680 fffff880`01b3f5d6 : 00000000`00000000 fffffa80`073519a0 fffffa80`07253700 00000000`00000000 : tcpip!IppLoopbackEnqueue+0x1f5
    fffff880`0757f720 fffff880`01b3c3b7 : fffff880`01c4f9a0 00000000`00000000 00000000`00000000 fffff800`01c40800 : tcpip!IppFragmentPackets+0x796
    fffff880`0757f840 fffff880`01b3e805 : fffff880`0757fba0 00000000`00140005 00000000`00000000 00000001`00000002 : tcpip!IppDispatchSendPacketHelper+0x87
    fffff880`0757f900 fffff880`01b3cf43 : fffffa80`0398bd06 00000000`0000bd00 fffffa80`00000014 fffff880`00000000 : tcpip!IppPacketizeDatagrams+0x2d5
    fffff880`0757fa20 fffff880`01b403ae : fffff880`07580230 fffff880`01cee307 fffff880`01c4f9a0 fffffa80`0398bdb0 : tcpip!IppSendDatagramsCommon+0x753
    fffff880`0757fcf0 fffff880`01b19d55 : 00000000`00000000 fffff880`075806f0 fffff880`075806f0 fffff880`07580858 : tcpip!IpNlpSendDatagrams+0x3e
    fffff880`0757fd30 fffff880`01b422af : fffffa80`0735c010 6d61fea9`6bc00002 00000000`00000000 00000000`00000000 : tcpip!IppSlowSendDatagram+0x75
    fffff880`0757fe30 fffff880`01b4804b : fffffa80`04560430 00000000`00000001 fffff880`07580b00 00000000`00003912 : tcpip!IpNlpFastSendDatagram+0xc3f
    fffff880`075801e0 fffff880`01b491de : 00000000`00001c7f 00000000`00000000 00000000`00000002 00000000`00000000 : tcpip!TcpTcbHeaderSend+0x47b
    fffff880`07580390 fffff880`01b697e6 : 00000000`00000000 00000000`00000000 fffff880`01c49128 00000000`00000000 : tcpip!TcpTcbSend+0x88e
    fffff880`07580610 fffff880`01b3023d : 00000000`00000000 00000000`00000000 fffff880`03730000 00000000`00000001 : tcpip!TcpFlushDelay+0x316
    fffff880`075806f0 fffff880`01b3003c : fffff880`075808f0 fffffa80`0398acf0 fffffa80`07c27350 fffffa80`03926b20 : tcpip!TcpDeliverInput+0x18d
    fffff880`075807f0 fffff880`01815d15 : fffffa80`03926b20 00000000`00000002 fffffa80`03926b20 fffffa80`09d17bb8 : tcpip!TcpRequestReceive+0x18c
    fffff880`075808b0 fffff880`0180cb8a : fffffa80`09d17bb8 00000000`00000002 fffffa80`03926b20 fffffa80`03d503e0 : tdx!TdxReceiveConnection+0x1f5
    fffff880`07580950 fffff880`01602a06 : fffffa80`03d503e0 00000000`00000010 fffffa80`069c4860 fffffa80`09d17aa0 : tdx! ?? ::FNODOBFM::`string'+0x47cf
    fffff880`075809d0 fffffa80`03d503e0 : 00000000`00000010 fffffa80`069c4860 fffffa80`09d17aa0 fffff880`063ee110 : [COLOR=#ff0000][U][B]avgtdia[/B][/U][/COLOR]+0x2a06
    fffff880`075809d8 00000000`00000010 : fffffa80`069c4860 fffffa80`09d17aa0 fffff880`063ee110 fffff880`063d6dc7 : 0xfffffa80`03d503e0
    fffff880`075809e0 fffffa80`069c4860 : fffffa80`09d17aa0 fffff880`063ee110 fffff880`063d6dc7 fffffa80`08fde4f0 : 0x10
    fffff880`075809e8 fffffa80`09d17aa0 : fffff880`063ee110 fffff880`063d6dc7 fffffa80`08fde4f0 fffff880`07580c70 : 0xfffffa80`069c4860
    fffff880`075809f0 fffff880`063ee110 : fffff880`063d6dc7 fffffa80`08fde4f0 fffff880`07580c70 00000000`00000000 : 0xfffffa80`09d17aa0
    fffff880`075809f8 fffff880`063d6dc7 : fffffa80`08fde4f0 fffff880`07580c70 00000000`00000000 fffffa80`09c62a20 : mrxsmb!WPP_GLOBAL_Control
    fffff880`07580a00 fffff880`01602d16 : fffffa80`09d17aa0 fffff800`0300b1de 00000000`c0000016 fffffa80`03936800 : mrxsmb!SmbCseDissociateMidFromBufferContextLite+0x207
    fffff880`07580a50 fffffa80`09d17aa0 : fffff800`0300b1de 00000000`c0000016 fffffa80`03936800 fffff880`07580b30 : avgtdia+0x2d16
    fffff880`07580a58 fffff800`0300b1de : 00000000`c0000016 fffffa80`03936800 fffff880`07580b30 fffff880`016035d5 : 0xfffffa80`09d17aa0
    fffff880`07580a60 fffffa80`096f8f40 : fffffa80`00000000 00000000`00004000 00000000`00000000 fffffa80`09c62950 : nt!ExAllocatePoolWithTag+0xfe
    fffff880`07580b50 fffffa80`00000000 : 00000000`00004000 00000000`00000000 fffffa80`09c62950 fffffa80`03a20cb0 : 0xfffffa80`096f8f40
    fffff880`07580b58 00000000`00004000 : 00000000`00000000 fffffa80`09c62950 fffffa80`03a20cb0 fffff880`063df875 : 0xfffffa80`00000000
    fffff880`07580b60 00000000`00000000 : fffffa80`09c62950 fffffa80`03a20cb0 fffff880`063df875 fffffa80`03a20cb0 : 0x4000
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    tcpip!WfpAuditEventGeneral+1da
    fffff880`01b1623a 33c0            xor     eax,eax
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  tcpip!WfpAuditEventGeneral+1da
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: tcpip
    IMAGE_NAME:  tcpip.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79420
    FAILURE_BUCKET_ID:  X64_0x7f_8_tcpip!WfpAuditEventGeneral+1da
    BUCKET_ID:  X64_0x7f_8_tcpip!WfpAuditEventGeneral+1da
    May possibly be a network adapter driver which you may want to consider updating.
    athurx.sys 1/4/2010 Atheros AR9271 Wireless Network Adapter from here ATHEROS drivers for Microsoft Windows (Atheros?????)
    and or
    Rt64win7.sys 9/27/2011 slightly newer one here Realtek
    Good Luck
    Randy
    EDIT: Sorry forgot.... alternative to AVG = http://www.microsoft.com/security/pc-security/mse.aspx
     
    #2 Trouble, May 1, 2012
    Last edited: May 1, 2012
  3. John Lauhoff

    John Lauhoff New Member

    Joined:
    Dec 2, 2011
    Messages:
    12
    Likes Received:
    0
    im getting similar crash can take look at mine thank you

    [FONT=Segoe UI, Arial]On Sat 5/5/2012 1:34:24 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050412-31715-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x44A7E)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E8EA7E, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
    Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Sat 5/5/2012 1:34:24 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002E8EA7E, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
    Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Fri 5/4/2012 10:48:54 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050412-48656-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031851CA, 0xFFFFF8800A7D1F60, 0x0)
    Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Fri 5/4/2012 5:04:45 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050412-33072-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF80002EE6B46)
    Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Fri 5/4/2012 3:07:27 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050412-27300-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFE9A, 0x8, 0xFFFFFFFFFFFFFE9A, 0x0)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Thu 5/3/2012 10:21:31 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050312-24320-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030042FE, 0xFFFFF8800A1BBAA0, 0x0)
    Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Thu 5/3/2012 6:43:49 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050312-23852-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0xC7 (0x4, 0xFFFFF80000000000, 0x1, 0xFFFFFFFF)
    Error: [FONT=Segoe UI, Arial]TIMER_OR_DPC_INVALID[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Wed 5/2/2012 10:45:26 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050212-34725-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880049EEAC7)
    Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Tue 5/1/2012 9:42:56 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050112-34320-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
    Bugcheck code: 0xFC (0xFFFFF88003E93AB8, 0x80000000B24E1963, 0xFFFFF88003E938B0, 0x2)
    Error: [FONT=Segoe UI, Arial]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that an attempt was made to execute non-executable memory.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    [/FONT]

    [FONT=Segoe UI, Arial]On Tue 5/1/2012 5:05:32 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\050112-34913-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70590)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Tue 5/1/2012 1:16:14 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\043012-28329-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
    Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002EC33BC)
    Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Tue 5/1/2012 12:12:38 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\043012-42759-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
    Bugcheck code: 0xA (0x1E, 0x2, 0x1, 0xFFFFF80002CA50E0)
    Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Mon 4/23/2012 10:55:25 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\042312-18408-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x1, 0xFFFFF80002CCF682, 0x0)
    Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Sun 4/22/2012 12:54:16 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\042112-16801-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
    Bugcheck code: 0xA (0x60910A342, 0x2, 0x1, 0xFFFFF80002C6E2BE)
    Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    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.
    [/FONT]

    [FONT=Segoe UI, Arial]On Sun 4/22/2012 12:07:49 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\042112-17690-01.dmp
    This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
    Bugcheck code: 0xA (0x48D8, 0x2, 0x0, 0xFFFFF80002D2F00E)
    Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
    file path: C:\Windows\system32\ntoskrnl.exe
    product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
    company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
    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.
    [/FONT]
     

Share This Page

Loading...