GoNz0 Posted October 12, 2015 Share Posted October 12, 2015 hi, I have done a fresh install to rule out anything else but opening Aida64 then trying to access sensor information results in a BSOD, this is via the sensor tab or the stability test with the following BSOD logged. Fingers crossed you have enough info to pint me in the right direction as I am reluctant to do a trial and error as this is a server. Thanks. This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)Error: DPC_WATCHDOG_VIOLATIONfile path: C:\Windows\system32\ntoskrnl.exeproduct: Microsoft® Windows® Operating Systemcompany: Microsoft Corporationdescription: NT Kernel & SystemBug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. This was probably caused by the following module: libsa.sys (libsa!DllUnload+0x34D30)Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)Error: DPC_WATCHDOG_VIOLATIONfile path: C:\Windows\system32\drivers\libsa.sysproduct: Windows ® Win 7 DDK drivercompany: Windows ® Win 7 DDK providerdescription: HP SmartArray DLLBug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.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: libsa.sys (HP SmartArray DLL, Windows ® Win 7 DDK provider).Google query: Windows ® Win 7 DDK provider DPC_WATCHDOG_VIOLATION isasensordump.txt smbusdump_full.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted October 12, 2015 Share Posted October 12, 2015 Since the BSoD seems to be happening in the HP SmartArray kernel driver, I suppose the issue is related to the RAID array enumeration module of AIDA64. Please try to disable the two RAID-related options in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. Quote Link to comment Share on other sites More sharing options...
GoNz0 Posted October 13, 2015 Author Share Posted October 13, 2015 Nope, same BSOD Quote Link to comment Share on other sites More sharing options...
Fiery Posted October 16, 2015 Share Posted October 16, 2015 Thank you. We need to narrow this down a bit more. Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Let me know if it causes a BSoD. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Let me know if it causes a BSoD. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Physical Drives Dump. Let me know if it causes a BSoD. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Let me know if it causes a BSoD. Thank you in advance Quote Link to comment Share on other sites More sharing options...
GoNz0 Posted November 15, 2015 Author Share Posted November 15, 2015 It did it on the Raid dump now I finally decided to risk it after accidentally clicking on sensors again Quote Link to comment Share on other sites More sharing options...
GoNz0 Posted November 28, 2015 Author Share Posted November 28, 2015 Hi, any news on this ? Quote Link to comment Share on other sites More sharing options...
Fiery Posted November 28, 2015 Share Posted November 28, 2015 I'm afraid without trial and error, we won't be able to solve this The AIDA64 sensor code is over 100,000 lines long, and without a hint on where the issue may be, it's very hard to find it without trying several tests on the machine in question. It would be quite easy if the machine was here, in our labs, or if you were able to run several more tests that may cause a crash or BSoD. With a server it's always a headache to find the root cause of such issues Quote Link to comment Share on other sites More sharing options...
GoNz0 Posted December 3, 2015 Author Share Posted December 3, 2015 It seems they have a custom raid firmware on the intel sata controller as it is fine in AHCI mode, oh well Quote Link to comment Share on other sites More sharing options...
Fiery Posted December 4, 2015 Share Posted December 4, 2015 It seems they have a custom raid firmware on the intel sata controller as it is fine in AHCI mode, oh well Thank you for letting us know about the resolution. However, when you disable both RAID SMART support and RAID member enumeration, AIDA64 is not supposed to be affected by potential issues about the RAID firmware. So it's still a weird issue, a real "head-scratcher" for us Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.