Minidump

  1. #1
    tommy2k8 is offline Full Member

    Minidump

    My client has got a Vista computer that is 3 months old; it kept getting Bue Screen of Death, flashed the BIOS and updated Windows, none worked. Then I downloaded the Windows Debugging Tools to read a minidump which I couldn't do because I didn't have the right permissions, so I set them, and it still didn't work.
    I haven't got the right symbols to read the minidump? Can someone read it for me?
    Attached Files


  2. #2
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    You can find a list of general 7E errors here:

    Troubleshooting Windows STOP Messages

    0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


    The faulted driver in your case is Ndisuio.sys

    ndisuio.sys is a process belonging to the NDIS User Mode I/O (NDISUIO) NDIS protocol driver which offers support for wireless devices such as Bluetooth and the like.


    As to the symbol library:

    Did you load the debugger and the WIZ from this post:

    HERE

  3. #3
    tommy2k8 is offline Full Member
    I did, but I couldb't read the dump myself, even when I downloaded the symbols, as I got a 'win32 0n5 error. Access is denied' even when I changed the permissions!

  4. #4
    peterdiva is offline Full Member
    Uninstall Comodo Firewall and see if the crashes stop. Inspect.sys belongs to Comodo.

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    88afbad4 877120b0 85d9fbf8 85eead98 00000000 ndisuio+0x2f7c
    88afbb08 87704d7d 00d9f398 85eead98 00000000 ndis+0xc70b0
    88afbb38 87704801 00000001 85d9f398 00000001 ndis+0xb9d7d
    88afbcb8 8764c51e 853950e8 00000000 00000000 ndis+0xb9801
    88afbcd4 877172c4 853950e8 85eead98 00000000 ndis+0x151e
    88afbd20 8bb47a98 003950e8 88afbd50 00000001 ndis+0xcc2c4
    88afbd48 8bb4e69c 856fb718 00000000 851a3008 inspect+0x2a98
    88afbd60 8bb4f5fe 852ca348 00000000 85380590 inspect+0x969c
    88afbd7c 81dafbad 00000000 88af0680 00000000 inspect+0xa5fe
    88afbdc0 81c9a346 8bb4f59a 00000000 00000000 nt+0x1afbad
    00000000 00000000 00000000 00000000 00000000 nt+0x9a346

  5. #5
    tommy2k8 is offline Full Member
    Booted the computer into Safe Mode
    Used Last Known Good Configuration
    Tried System Restore
    Tried a system repair

    Not successful, as the system continuously gets stuck in a restart loop


    I backed up the files he asked to be backed up, from Windows using the Linux System Rescue CD
    I backed up his pictures and his enails

    I performed a Sorface Analysis with TuffTest, nothing was found

    With the Vista DVD, the system attempted a repair
    The system said it had corrected errors, but didn't say what they were
    I tried to boot the system up in normal and safe mode, but it still wouldn't boot

    From the Vista DVD, I perfomed a rebuiild
    The first thing that I needed was a product key. After looking on the computer and on the DVD
    I couldn't find one, so this has to be entered later
    I continued without a product key
    I chose a Custom Install
    The system went through the process of installing Windows, before asking me to set the time, date
    and enter the regional settings
    The installation was complete

    Windows then checked the computer's performance

    Everything was fine, until the whole computer froze

    I did another rebuild, installing the third-party software again, and the updates. This seemed to do the trick for a couple of hours, although I got another Blue Screen of Death later on reporting a driver gobbling up memory

    I entered the make and model of the motherboard into Google, and found a BIOS update. I downloaded this, flashed the BIOS, and hoped that it worked.

    Ron took it home on Friday 20, only to turn it on on the Saturday to be greeted with another BSOD. Unfortunately, the computer restarted quickly so he couldn't note down the error message.

    He brought it back on Wednesday 25, I had a look at the Event Log, that only told me Windows had recovered from a serious error.
    I then installed SP1, in the hope the errors would go away. However, I turned it on this morning (26th) and I got another BSOD. Don came round and put another power supply in.

    I downloaded the Windows Debugging Tools

+ Reply to Thread