Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Solved HWinfo BSOD
#1
Hi,

First thanks for your very good program.

HWinfo64 running on Win 7 computer + ASUS Z170A MB works fine EXCEPT when I use a backup program to clone one hard drive to a backup drive,  I get a BSOD with the following error summary:

crash dump file: C:\windows\Minidump
This was probably caused by the following module: iastora.sys (iaStorA+0xEA99C)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFF8800111199C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\iastora.sys

Steps/observations I have taken to troubleshoot:
1.  When I run my backup program without Hwinfo64 running, it runs without any problems, no BSOD.
2.  Updated Intel RST driver/iastora.sys, BSOD problem persisted

3.  Tried Hwinfo64 in Low level I/O access BSOD occurs
4.  Tried Hwinfo64 with drive scans disabled, no BSOD

Would appreciate your help to fix this.

Thanks,
Bill
Reply
#2
Hi Bill,
So the BSOD happens when you have HWiNFO already running (assuming with sensors monitoring the system) and you start the backup tool ? Or does it happen during HWiNFO startup ?
It seems this is a collision between HWiNFO, the backup tool and Intel RST.
A HWiNFO Debug File of the crash might be helpful...
Reply
#3
Hi Martin,
Thanks for your quick reply.
Yes, the BSOD occurs when I have HWInfo already running/sensors monitoring along with Hwinfo gadget.
As luck would have it I was just running a debug to post to you and the problem didn't occur (this is the first time I didn't get the BSOD over the last 10 or so daily backups)
The backup program takes about an hour and the BSOD occurs toward the end of the backup, with the same BSOD mnidump error message each time.
I will attempt to get a debug file if and when it occurs next.
If there is any advice you can offer in the interim, I would appreciate it.

Thank you.
Reply
#4
Since this appears to be a collision between two programs, I can only advise not to use both at the same time.
Another alternative would be that if you run the backup tool, you'll temporary disable (right-click and Disable Monitoring) the SMART sensor in HWiNFO sensors screen until the backup finishes. That might help to avoid the problem.
Reply
#5
Thanks Martin for the good product and the good service.
I'll keep my fingers crossed I don't have to send you a debug file.
Reply
#6
You're welcome.
Reply
#7
Hi Martin,
Unfortunately, the BSOD problem described above persists.  I am attaching the debug file.
Thanks in advance for your assitance.
Bill


Attached Files
.dbg   HWiNFO64.DBG (Size: 2.6 MB / Downloads: 2)
Reply
#8
Is the attached DBG file capturing the BSOD? It doesn't seem so, I can see a normal/successful run there.
Have you tried to disable the SMART sensors in HWiNFO when trying to perform the backup ?
Reply
#9
(02-18-2016, 09:46 AM)Martin Wrote: Is the attached DBG file capturing the BSOD? It doesn't seem so, I can see a normal/successful run there.
Have you tried to disable the SMART sensors in HWiNFO when trying to perform the backup ?

The BSOD occurred and the computer rebooted on its own.  The Debug file was the one created during this process.
I didn't get an opportunity to test the backup with the smart sensors disabled yet.
Reply
#10
But the DBG file doesn't show any signs of a system crash - it shows just a clear termination of HWiNFO without any issues.
If you have HWiNFO configured to autostart with Windows this might be the reason - the DBG was overwritten after the new boot.
Nevertheless, I think the only solution is to disable those sensors. Or ask the backup software vendor to fix the problem on their side. It's not clear which tool is the guilty one as both work without issues standalone.
Reply
#11
(02-18-2016, 02:12 PM)Martin Wrote: But the DBG file doesn't show any signs of a system crash - it shows just a clear termination of HWiNFO without any issues.
If you have HWiNFO configured to autostart with Windows this might be the reason - the DBG was overwritten after the new boot.
Nevertheless, I think the only solution is to disable those sensors. Or ask the backup software vendor to fix the problem on their side. It's not clear which tool is the guilty one as both work without issues standalone.

The BSOD issue is now occurring without the backup program running. 

I disabled autostart so hopefully it captured the event.

I am attaching the latest DBG file which is substantially larger this time.

Thanks
Reply
#12
Sorry, but the file you attached is exactly the same (uncompressed) as the previous DBG file.
Reply
#13
(02-19-2016, 03:10 PM)Martin Wrote: Sorry, but the file you attached is exactly the same (uncompressed) as the previous DBG file.

Sorry my error.  I am trying to attaching the correct file but am getting a message saying
  • The file you attached is too large. The maximum size for that type of file is 5120 kilobytes.
Reply
#14
How large is the file when compressed ? Can you try to upload it somewhere else ?
Reply
#15
1.2gb uncompressed, 7mb compressed
Reply
#16
I can see a lot of failures there when HWiNFO queries the disks for SMART status and especially at the end of the dump (near the BSOD).
This is most probably an indication of a failure in the Intel RST driver and I can't do anything about that. You might try some previous RST version, or hope that Intel will fix this sometime later.
Otherwise I can only suggest to disable polling of the SMART sensors in HWiNFO to avoid such problems.
Reply
#17
Thanks Martin.
Reply
#18
You're welcome.
Reply
#19
(02-19-2016, 04:20 PM)Martin Wrote: I can see a lot of failures there when HWiNFO queries the disks for SMART status and especially at the end of the dump (near the BSOD).
This is most probably an indication of a failure in the Intel RST driver and I can't do anything about that. You might try some previous RST version, or hope that Intel will fix this sometime later.
Otherwise I can only suggest to disable polling of the SMART sensors in HWiNFO to avoid such problems.

Hi Martin,

After trying to troubleshoot this some more, I did disable polling of the SMART sensors as you suggested and no BSOD occur.  Unfortunately with this config I am not able to monitor my HDD temps.

I did notice that when trying Open Hardware Monitor I am able to monitor temps without any BSOD, however I prefer the flexibility of your program, therefore I am wondering whether this info might help you find a solution or a workaround so I can use your program, monitor my HDD's and no BSOD.

And one additional question please, is there anyway to increase the general font side in your gadget any larger than the two choices we are given in the dropdown menu?

Thanks!
Bill
Reply
#20
Hi Bill,
since this problem seems to happen only occasionally, have you performed enough testing using OHM to say that it doesn't cause issues there ?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)