Intermittent BSOD 0x8000000002

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by masterbyllet, Feb 16, 2010.

  1. masterbyllet

    masterbyllet New Member

    Joined:
    Feb 16, 2010
    Messages:
    12
    Likes Received:
    0
    For the last week or so I've been getting an intermittent BSOD. There doesn't appear to be any pattern to when it happens. This is the Event viewer description when I get back on:

    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.



    - System

    - Provider


    [ Name] Microsoft-Windows-Kernel-Power


    [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}



    EventID 41


    Version 2


    Level 1


    Task 63


    Opcode 0


    Keywords 0x8000000000000002

    - TimeCreated


    [ SystemTime] 2010-02-16T11:42:13.660412600Z



    EventRecordID 4564


    Correlation

    - Execution


    [ ProcessID] 4


    [ ThreadID] 8



    Channel System


    Computer Daniel-LAPTOP

    - Security


    [ UserID] S-1-5-18

    - EventData

    BugcheckCode 0

    BugcheckParameter1 0x0

    BugcheckParameter2 0x0

    BugcheckParameter3 0x0

    BugcheckParameter4 0x0

    SleepInProgress false

    PowerButtonTimestamp 0



    I'm running a DELL Vostro 1520 with 4Gb of memory

    I'm still trying to find the mini.dmp files. If anyone could tell me where to look for them, I cant find them. Not in the usual place I would look on XP...


    Thanks for your suggestions
     
  2. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    go here to setup your system for minidumps and location, then post your next minidump and some system info
    • motherboard make and model
      ram make model and quantity
      operating system
      hard drive(s)
      Power Supply
      antivirus and firewall used
     
  3. masterbyllet

    masterbyllet New Member

    Joined:
    Feb 16, 2010
    Messages:
    12
    Likes Received:
    0
    I cant seem to get it to save the dump files anywhere
    Also I cant get it to stop the auto-restart.

    I've tried updating drivers like graphics, chipset, network etc.... to no avail

    Device manager tells me that the Teredo Psedo-interface driver and the mass storage controller havnt got the right drivers however I cant find them.... I dont htink this would cause a BSOD however...

    Any suggestions on where to go next


    PS. I cant find the motherboard/ ram manufactuer, as its a DELL laptop I cant really get to the innards.. sorry. If theres a way to acess that infomation from the OS please let me know...

    As for RAM its 2x2046MB Modules

    Thanks
     
  4. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    to setup minidumps and stop the auto restart ...............
    • Go to Start and type in sysdm.cpl and press Enter
      Click on the Advanced tab
      Click on the Startup and Recovery Settings button
      Ensure that Automatically restart is unchecked
      Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
      Ensure that the Small Dump Directory is listed as %systemroot%\Minidump
      Click OK twice to exit the dialogs, then reboot for the changes to take effect.
    download and run the free version of >>SIW (third choice) and click file save as HTML report and upload here, or send us the highlights :)
     
  5. masterbyllet

    masterbyllet New Member

    Joined:
    Feb 16, 2010
    Messages:
    12
    Likes Received:
    0
    I've tried doing what you said by setting up the minidump thing... but it still refuses to create the file :S
    I've attached the SIW report aswell...
    (Wont let me attach it for some reason... here's the jist of it)


    Property Value Manufacturer Dell Inc. Family Vostro Product Name Vostro 1520 Version Null

    SKU Number Null PC System Type Mobile Machine Type AT/AT COMPATIBLE Infrared (IR) Supported No DMI System UUID 00000000-00000000-00000000-00000000 UUID 00000000-0000-0000-0000-000000000000 Disk Space Disk C: 125 GB Available, 232 GB Total, 125 GB Free Physical Memory 4057 MB Total, 2456 MB Free Memory Load 39% Virtual Memory 8112 MB Total, 6090 MB Free PageFile Name C:\pagefile.sys PageFile Size 4056 MB In use 211 MB Max used 214 MB Profile GUID {846ee340-7039-11de-9d20-806e6f6e6963} The system clock interval 15 ms Motherboard Top Property Value Manufacturer Dell Inc. Model 0T816J Serial Number . North Bridge Intel GM45/GM47 Revision 07 South Bridge Intel 82801IM (ICH9-M) Revision 07 CPU Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz Cpu Socket Socket P (478) System Slots 1 PCI Memory Summary Maximum Capacity 4096 MBytes Memory Slots 2 Error Correction None Warning! Accuracy of DMI data cannot be guaranteed

    Let me know what you think. thankss
     
  6. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    Once you have setup for recording minidumps it won't create the file until you have had another bluescreen ;)

    to upload a file if it's not on the allowed list then simply zip it first :)

    • allowed file types
      bmp 2.00 MB - -
      doc 2.00 MB - -
      docx 2.00 MB - -
      gif 2.00 MB - -
      iso 2.00 MB - -
      jpe 2.00 MB - -
      jpeg 2.00 MB - -
      jpg 2.00 MB - -
      nfo 2.00 MB - -
      pdf 2.00 MB - -
      png 2.00 MB - -
      psd 2.00 MB - -
      rar 2.00 MB - -
      txt 2.00 MB - -
      xml 2.00 MB - -
      zip 2.00 MB -
     
  7. masterbyllet

    masterbyllet New Member

    Joined:
    Feb 16, 2010
    Messages:
    12
    Likes Received:
    0
    Here is the full file then...
    I've had 1 more BSOD since I re-set the minidump... but alas no file or even a folder.. :S
     

    Attached Files:

  8. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    are you looking in C:\Windows\Minidump ?
     
  9. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    your BIOS looks like it needs updating as the latest version on the DELL site is 26/01/2010 and yours is from 04/08/2009 , >>go here and make sure you have all the updates for your system ?

    spend some time on that site and verify everything ;)
     
  10. masterbyllet

    masterbyllet New Member

    Joined:
    Feb 16, 2010
    Messages:
    12
    Likes Received:
    0
    There isnt even a C:\Windows\Minidump folder :( ... Not sure why...
    I'll try updating the bios then... I'll report once its done thanks
     
  11. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    and all the other drivers that need updating :)
     
  12. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    did you check the part mentioned in line 6*
     
  13. masterbyllet

    masterbyllet New Member

    Joined:
    Feb 16, 2010
    Messages:
    12
    Likes Received:
    0
    Right. The minidump worked this time.

    I've attached it...
     

    Attached Files:

  14. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    According to the debugger it looks like "Probably caused by NETIO.SYS" but I kinda think that it might be more likely that Avast is causing an issue with the network and netio.sys is just catching the blame. These driver files look pretty old
    aswRdr.SYS 11/26/2008 11:16:31 AM
    aswTdi.SYS 11/26/2008 11:16:40 AM and this one is mentioned in the stack trace...I'll highlight it in the STACK TEXT section
    aswMonFlt.sys 11/26/2008 11:17:21 AM
    aswFsBlk.sys 11/26/2008 11:17:29 AM
    aswSP.SYS 11/26/2008 11:17:47 AM
    I think these are all part of the Avast software, monitoring, filtering, packet inspection api(s)
    So you may want to try uninstalling just to check, it's up to you....if you have any other type of firewall / network security suite, there may just be some underlying conflict with them bumping heads and stepping on each other's toes, I just didn't see a mention of any other program.

    Code:
     
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Users\JohnSmith\Desktop\New folder\022510-18844-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*[URL=\"http://\\"http://msdl.microsoft.com/download/symbols\\"\"]Symbol information[/URL]
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
    Debug session time: Thu Feb 25 16:20:38.860 2010 (GMT-6)
    System Uptime: 0 days 10:17:29.780
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    .........................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 7F, {8, 80050031, 406f8, fffff80002a59798}
    Unable to load image aswTdi.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for aswTdi.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
    Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    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: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff80002a59798
    Debugging Details:
    ------------------
     
    BUGCHECK_STR: 0x7f_8
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    PROCESS_NAME: System
    CURRENT_IRQL: 2
    LAST_CONTROL_TRANSFER: from fffff80002a90469 to fffff80002a90f00
    STACK_TEXT: 
    fffff800`00ba4d28 fffff800`02a90469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`02a8e932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff800`02a59798 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`07286ea0 fffff880`01517c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58
    fffff880`07287590 fffff880`0151594f : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0728786a : NETIO!CompareSecurityContexts+0x6a
    fffff880`07287600 fffff880`015179b5 : 00000000`08000000 00000000`00000000 00000000`00000000 fffff880`03e144d9 : NETIO!MatchValues+0xef
    fffff880`07287650 fffff880`01517845 : fffffa80`06e1c0f0 fffffa80`06d6e160 fffff880`07287878 fffff880`07287fb0 : NETIO!FilterMatch+0x95
    fffff880`072876a0 fffff880`01518ccb : 00000000`00000000 00000000`00000000 fffff880`07287fb0 fffff880`07287860 : NETIO!IndexListClassify+0x69
    fffff880`07287720 fffff880`0163e4d0 : fffff880`07287fb0 fffff880`07287bf8 fffff880`07288930 fffffa80`05e74800 : NETIO!KfdClassify+0xa4e
    fffff880`07287a90 fffff880`0163777e : fffff880`01746690 00000000`00000000 fffffa80`074dc800 00000000`00000000 : tcpip!WfpAleClassify+0x50
    fffff880`07287ad0 fffff880`01636c15 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e
    fffff880`072881e0 fffff880`0163a956 : 00000000`00000000 00000000`00000000 00000000`00000011 00000000`00000000 : tcpip!WfpAleAuthorizeSend+0x325
    fffff880`072884b0 fffff880`0163d6a4 : 00000000`00000000 fffff880`072888e8 fffff880`072888f0 fffff880`0728d000 : tcpip!WfpAleConnectAcceptIndicate+0x106
    fffff880`072885a0 fffff880`01635f59 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000008 : tcpip!ProcessALEForTransportPacket+0x664
    fffff880`07288810 fffff880`01662bf6 : 00000000`00000000 00000000`00000002 fffffa80`052f8900 fffffa80`061d8900 : tcpip!WfpProcessOutTransportStackIndication+0x329
    fffff880`072889e0 fffff880`01667a7e : fffffa80`052f2080 fffff880`01513804 fffff880`0176c9a0 fffffa80`074dc800 : tcpip!IppSendDatagramsCommon+0x526
    fffff880`07288cb0 fffff880`01634cf8 : fffffa80`074dc800 fffffa80`05e74800 fffffa80`05e74800 fffffa80`052f2080 : tcpip!IpNlpSendDatagrams+0x3e
    fffff880`07288cf0 fffff880`0163526d : fffffa80`05336780 fffffa80`08711b60 fffff880`07289640 00000000`00000000 : tcpip!UdpSendMessagesOnPathCreation+0x688
    fffff880`07289070 fffff880`01634ef5 : fffff880`072895a0 00000000`00008900 00000000`00000001 00000000`00000000 : tcpip!UdpSendMessages+0x35d
    fffff880`07289460 fffff800`02aa064a : 00000000`00000000 00000000`00000000 fffffa80`04a3f9a0 00000000`00000000 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
    fffff880`07289490 fffff880`016354b8 : fffff880`01634ee0 fffff880`072895a0 fffffa80`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
    fffff880`07289570 fffff880`0195cf45 : fffffa80`04b2f7b0 fffffa80`03d3ce40 fffffa80`07087010 fffffa80`04fddfde : tcpip!UdpTlProviderSendMessages+0x78
    fffff880`072895f0 fffff880`0195cff2 : 00000000`00000002 fffffa80`04f3ce30 fffffa80`08a31a50 fffffa80`08a318f0 : tdx!TdxSendDatagramTransportAddress+0x2f5
    fffff880`072896d0 fffff880`019861b8 : fffffa80`04ffef68 00000000`00000000 fffffa80`04f3ce30 fffffa80`04ffef68 : tdx!TdxTdiDispatchInternalDeviceControl+0x52
    fffff880`07289700 fffffa80`04ffef68 : 00000000`00000000 fffffa80`04f3ce30 fffffa80`04ffef68 00000000`00000000 : aswTdi+0x11b8 [B][U][COLOR=red](not sure that this is the problem, but it just caught my eye.)[/COLOR][/U][/B]
    fffff880`07289708 00000000`00000000 : fffffa80`04f3ce30 fffffa80`04ffef68 00000000`00000000 00000000`00000000 : 0xfffffa80`04ffef68
     
    STACK_COMMAND: kb
    FOLLOWUP_IP: 
    NETIO!CompareSecurityContexts+6a
    fffff880`01517c5a 448b442470 mov r8d,dword ptr [rsp+70h]
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: NETIO!CompareSecurityContexts+6a
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: NETIO
    IMAGE_NAME: NETIO.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
    FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
    BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
    Followup: MachineOwner
    ---------
    0: kd> lmvm NETIO
    start end module name
    fffff880`01511000 fffff880`01571000 NETIO (pdb symbols) c:\symbols\netio.pdb\4ACD68B3A9824AAAB3C53C0077FC611F2\netio.pdb
    Loaded symbol image file: NETIO.SYS
    Mapped memory image file: c:\symbols\NETIO.SYS\4A5BC18A60000\NETIO.SYS
    Image path: NETIO.SYS
    Image name: NETIO.SYS
    Timestamp: Mon Jul 13 18:21:46 2009 (4A5BC18A)
    CheckSum: 0005F36C
    ImageSize: 00060000
    File version: 6.1.7600.16385
    Product version: 6.1.7600.16385
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.6 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: netio.sys
    OriginalFilename: netio.sys
    ProductVersion: 6.1.7600.16385
    FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription: Network I/O Subsystem
    LegalCopyright: © Microsoft Corporation. All rights reserved.
    
     
    #14 Trouble, Feb 25, 2010
    Last edited: Feb 25, 2010
  15. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    I agree with trouble here, the error was NETIO.SYS crashing and as a component in your Networking subsystem this is likely being caused by interference from Avast, your Avast files are from 2008 and definitely out of date, either update Avast or replace with something like Microsoft Security Essentials.
     

Share This Page

Loading...