BSOD first time from cold boot, 1000007e


  1. Posts : 3
    Windows 7 Professional x64
       #1

    BSOD first time from cold boot, 1000007e


    Hello,

    I've just turned on my Desktop today and got my first blue screen since building this computer (built in 2012).

    I'm more of a hardware guy than software... but know my way around registry etc. So thought it be best if I post here, as I'm sure someone in here will have allot better understanding of trouble shooting these BSOD's!

    I have attached the Zip file as requested in the 'Posting Instructions' so hope I've done all okay.

    Many thanks in advanced to anyhow is able to give me an in-sight as to what could have caused this BSOD.

    Regards,

    Makem.
      My Computer


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

    The crash dump blames Creative 20X2 HAL Driver.
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff880090ae485, fffff880031a7828, fffff880031a7080}
    
    Probably caused by : ha20x22k.sys ( ha20x22k+8f485 )
    
    Followup: MachineOwner
    ---------
    You should search for an updated driver for your X-Fi from Creative Worldwide Support .

    On another note, free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept then restart.

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

    Report us for any further BSOD after doing those.
      My Computer


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

    Hi Arc,

    Thanks for your reply and instructions!

    I've done what you asked;

    You should search for an updated driver for your X-Fi from Creative Worldwide Support.
    I wasn't entirely sure which driver I needed from their site. as they had multiple drivers for the X-Fi Titanium Fatal1ty Pro so I dl'd: "Sound Blaster X-Fi Titanium Fatal1ty Professional Series (SB0886)" and installed.

    Also cleared those start ups as you suggested, removed Deamon tools and ran the "SPTDinst-x64" program however it was grey.

    No blue screen what I restarted the last time, so maybe that sorted it.

    I'll post back if I get any other issues.

    Thanks again Arc! Life saver. :)

    I'll mark as solved as no BSOD yet

    Regards,

    Makem
      My Computer


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

    You are welcome, mate. :) Let us know for any further BSOD.
      My Computer


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

    Hi Arc,

    Sadly it BSOD again this morning.

    It's odd because it doesn't seem to do it when I restart the computer. Only when I shut it down, turn the power off at the wall; then turn it back on and then the PC. Not sure why it only happens when I do this..

    Anyhow, as before I re-ran the log gathering tool as stated in the 'Posting Instructions' (I deleted the old dump file as didn't want you to get confused as to which one to take a look at)

    Thanks again Arc for all your help man.

    Regards,

    Makem
      My Computer


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

    It is still the same thing.

    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff880068d6485, fffff880031a7828, fffff880031a7080}
    
    Probably caused by : ha20x22k.sys ( ha20x22k+8f485 )
    
    Followup: MachineOwner
    ---------
    If the device itself is not failing/broken, I think it would be the best that you inform this issue to Creative. Ask them which exact driver is needed for your device.
      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 21:54.
Find Us