BSOD 0x69 IO1 Initizialtion Error - Seems to be the least understood..


  1. Posts : 5
    Windows 7 Ultimate
       #1

    BSOD 0x69 IO1 Initizialtion Error - Seems to be the least understood..


    Hi All,

    Very frustrating BSOD, while not installing anything new, changing drivers or anyghing I started to get BSODs.

    First on one my two on board net cards stopped working, literally would not load the net at all. Therefore I swapped to my other internal net socket and the net worked for a while untill the above BSOD came along and now it will not boot, after CHKDSKs. reg repairs etc.

    The other annoying thing is I can't try system restore as my drive is a U320 SCSI and amazingly Windows startup repair will not recognise my drivers even though the same drivers work within Windows!

    Very frustrating, any advice will be greatly appreciated.

    Attached is the last NETBTLOG and MINIDUMP.

    Thx guys.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard.

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\mv61xx.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mv61xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for mv61xx.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {80000003, 8d6a709e, 843359f0, 0}
    
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : mv61xx.sys ( mv61xx+1c09e )
    
    Followup: MachineOwner
    ---------
    From the bugcheck analisys, we are having two things.

    • stpd.sys: Used by Daemon Tools or Alcohol120%, as a virtual drive emulator driver. Most well knows cause of BSOD in windows7. Uninstall the either program.
    • mv61xx.sys: Marvell Thor Windows Driver. Also a known problem causer, Usually people avoid Marvell drivers, as they are poorly written. You may either update your drivers from Marvell - Support, or uninstall those, use windows drivers only.


    Moreover, you have an obsolitely old display driver installed.
    Code:
     lmvm nvlddmkm
    start    end        module name
    98219000 98bb55a0   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 16 22:37:56 2010 (4CB9DBEC)
        CheckSum:         009A1A8C
        ImageSize:        0099C5A0
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Download the latest drivers from Drivers - Download NVIDIA Drivers.

    Let us know the results.
      My Computer


  3. Posts : 5
    Windows 7 Ultimate
    Thread Starter
       #3

    Hi,

    Thanks a lot for your response.

    As the system is non booting I have been unable to uninstall those drivers unless you know of a way to do this?

    Also I could not find stpd.sys so not sure there?

    I booted into a rescue environment and changed the mv driver file extensions to bak instead of sys so they wouldn't load and I disabled
    the onboard marvel network adapters in the bios so they wouldn't load.

    However the system still won't load have you any advice on what to try??

    Thanks a lot.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4
      My Computer


  5. Posts : 5
    Windows 7 Ultimate
    Thread Starter
       #5

    Thanks again Arc.

    I would have completed the steps outlined in the tutorial already if was able to access my drive.

    My problem is that my drive is a SCSI drive on a adaptec card and windows will not accept any of adaptecs drivers when in startup repair, so I can't SFC scan or Startup Repair which is frustrating.

    So not sure what to try now!
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Can you boot into Safe Mode ? If so, you may uninstall the adaptec drivers in safe mode, from device manager. In the next reboot the generic drivers will be loaded automatically.

    Then you try to boot, or repair the boot error, IMO.
      My Computer


  7. Posts : 5
    Windows 7 Ultimate
    Thread Starter
       #7

    No tried all boot options can't get into the original drive at all

    Not sure where I can go?

    Can I remove entries to them through the registry hive loaded from inside a rescue cd?
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    KC1911 said:
    No tried all boot options can't get into the original drive at all

    Not sure where I can go?

    Can I remove entries to them through the registry hive loaded from inside a rescue cd?
    At first make it sure that the 100 MB hidden system reserved partition is marked as active.
    Partition - Mark as Active

    Follow either the Method two or the method three.

    Then run Startup Repair for three separate times, with restarts in between every single run.

    Startup Repair - Run 3 Separate Times
      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 02:03.
Find Us