daily BSOD, iastor.sys, error 0x1000007E

Page 1 of 2 12 LastLast

  1. Posts : 9
    64 bit windows 7 Home Premium Windows 7 Service Pack 1, 6.1, build: 7601
       #1

    daily BSOD, iastor.sys, error 0x1000007E


    Dear All,

    I hope to find someadvice on an BSOD issue which I have been having for the last few months and which I tried to solve several times but nothing so far helped.
    The issue is driving me crazy.. So I decided yesterday to reinstall to factory settings via the boot option and the recovery partition on the hard disk (I did not use the CD drive, As funny enough my CD DVD drive does not "feel"disks inside anymore". I dont know if this is even a related issue to the BSOD.) but i do not care so much about the cd drive anyway.)

    I attached the requested zip file in attachment.
    The BSOD message indicates

    This was probably caused by the following module: iastor.sys (iaStor+0x496B0)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880010896B0, 0xFFFFF88003BD6508, 0xFFFFF88003BD5D60)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\windows\system32\drivers\iastor.sys
    product: Intel Rapid Storage Technology driver
    company: Intel Corporation


    Your assistance would be much appreciated.

    Regards

    Willem
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Hi Willem J,

    Welcome to the 7forums :)

    Please check HP for driver updates for your chipset drivers or Intel drivers.
    Please do NOT use the installed Intel program, but use the support page of HP.
      My Computer


  3. Posts : 9
    64 bit windows 7 Home Premium Windows 7 Service Pack 1, 6.1, build: 7601
    Thread Starter
       #3

    Hey axel,

    I already used hp website to reinstall drivers for chipset and iastor however did help for the boss's.

    Regards
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4




    Diagnostic Test

     DRIVER VERIFIER


       Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

       Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computer


  5. Posts : 9
    64 bit windows 7 Home Premium Windows 7 Service Pack 1, 6.1, build: 7601
    Thread Starter
       #5

    Axe0,

    Just followed verifier approach, I got immediately a boss after rebooting the machine.
    Tried twice to start up normally. Twice a boss.

    Eventually started up now using system restore.
    Now mousepad is also disabled...
      My Computer


  6. Posts : 9
    64 bit windows 7 Home Premium Windows 7 Service Pack 1, 6.1, build: 7601
    Thread Starter
       #6

    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\windows\Minidump

    Crash dumps are enabled on your computer.

    On Wed 5-10-2016 6:13:23 GMT your computer crashed
    crash dump file: C:\windows\Minidump\100516-11169-01.dmp
    This was probably caused by the following module: pxhlpa64.sys (PxHlpa64+0x3074)
    Bugcheck code: 0xC9 (0x228, 0xFFFFF880017A6074, 0xFFFFF98005F1ED80, 0x0)
    Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
    file path: C:\windows\system32\drivers\pxhlpa64.sys
    product: PxHelp64
    company: Rovi Corporation
    description: Px Engine Device Driver for 64-bit Windows
    Bug check description: This is the bug check code for all Driver Verifier
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: pxhlpa64.sys (Px Engine Device Driver for 64-bit Windows, Rovi Corporation).
    Google query: Rovi Corporation DRIVER_VERIFIER_IOMANAGER_VIOLATION



    On Wed 5-10-2016 6:13:23 GMT your computer crashed
    crash dump file: C:\windows\memory.dmp
    This was probably caused by the following module: dtsoftbus01.sys (dtsoftbus01+0x13F2)
    Bugcheck code: 0xC9 (0x228, 0xFFFFF880017A6074, 0xFFFFF98005F1ED80, 0x0)
    Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
    file path: C:\windows\system32\drivers\dtsoftbus01.sys
    product: DAEMON Tools Lite
    company: DT Soft Ltd
    description: DAEMON Tools Virtual Bus Driver
    Bug check description: This is the bug check code for all Driver Verifier
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: dtsoftbus01.sys (DAEMON Tools Virtual Bus Driver, DT Soft Ltd).
    Google query: DT Soft Ltd DRIVER_VERIFIER_IOMANAGER_VIOLATION



    On Tue 4-10-2016 16:40:46 GMT your computer crashed
    crash dump file: C:\windows\Minidump\100416-21621-01.dmp
    This was probably caused by the following module: iastora.sys (0xFFFFF88001679F08)
    Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF88001679F08)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\windows\system32\drivers\iastora.sys
    product: Intel Rapid Storage Technology driver
    company: Intel Corporation
    description: Intel Rapid Storage Technology driver - x64
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
      My Computer


  7. Posts : 7,050
    Windows 10 Pro
       #7

    When posting about crashes, follow the BSOD Posting Instructions
      My Computer


  8. Posts : 9
    64 bit windows 7 Home Premium Windows 7 Service Pack 1, 6.1, build: 7601
    Thread Starter
       #8

    Hey Axe,

    I just uploaded the last zip file according to the BSOD post instructions.

    In the mean while I tried today the following to resolve the iastor.sys bsod.

    -Reinstall to factory settings
    -after reboot I got the message that the system had experienced an unexpected shutdown.
    -Upon checking the bug check I found out that the iastor.sys was probably causing he bsod.
    -downloaded and installed the Intel Chipset Installation Utility and Driver from HP site.
    -downloaded and installed the Intel Rapid Storage Technology Driver from the HP site.

    So far no BSOD for the last few hours.

    What is this iastore technology actually doing and is it really needed?
    I understand it has to do something with the HARD disk when using RAID settings.
    Would replacing the HArd drive into an SSD drive help solving the BSOD issue?

    Regards

    Willem
      My Computer


  9. Posts : 7,050
    Windows 10 Pro
       #9

    The Intel Rapid Storage Technology drivers are for many the chipset drivers, for some the RAID controller drivers, in your case a part of the chipset drivers.

    Would replacing the HArd drive into an SSD drive help solving the BSOD issue?
    With this Intel driver it wouldn't, because it is part of the chipset and the chipset is part of your motherboard.
      My Computer


  10. Posts : 9
    64 bit windows 7 Home Premium Windows 7 Service Pack 1, 6.1, build: 7601
    Thread Starter
       #10

    Hey,

    Just Got a new BSOD error, again related to iastor.sys (new bsod files in attachement)

    - Updateding the chipset driver and Iastore driver were not helping
    - Getting a new harddisk is not the solution, correct?

    Can we assume that the motherboard is faulty?
    Does some-one know another possible solution?

    Regards

    Willem
      My Computer


 
Page 1 of 2 12 LastLast

  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 06:38.
Find Us