Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Driver Verifier Stop error for HWiNFO AMD64 Kernel Driver
#1
Firstly. out of my depth here Tongue. Secondly thanks for the software. 

I've been trying to track down sources of BSODs and other errors on my all new PC I built. I had the following BSOD opening HWiNFO while running driver verifier:


==================================================
Dump File         : 013118-17093-01.dmp
Crash Time        : 31-Jan-18 11:00:07 PM
Bug Check String  : DRIVER_VERIFIER_DETECTED_VIOLATION
Bug Check Code    : 0x000000c4
Parameter 1       : 00000000`00002000
Parameter 2       : fffff801`5e0210a5
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`4d4d4d4d
Caused By Driver  : HWiNFO64A.SYS
Caused By Address : HWiNFO64A.SYS+10a5
File Description  : HWiNFO AMD64 Kernel Driver
Product Name      : HWiNFO AMD64 Kernel Driver
Company           : REALiX™
File Version      : 8.98
Processor         : x64
Crash Address     : ntoskrnl.exe+1756e0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\013118-17093-01.dmp
Processors Count  : 16
Major Version     : 15
Minor Version     : 16299
Dump File Size    : 1,042,164
Dump File Time    : 31-Jan-18 11:06:02 PM
==================================================

System:

Windows 10 Pro 64-bit
AMD Ryzen 7 1700
32.0GB RAM @ 1199MHz (15-15-15-39) F4-2400C15D-32GFT
MSI B350M MORTAR (MS-7A37)
NVIDIA GeForce GTX 1070 Ti (MSI)


----

Not sure if this is interesting information or helpful at all. Let me know if there is a secure place to send a .dmp file if needed.

I've had so many BSODs on this machine, most if not all are nothing to do with HWiNFO and HWiNFO did not crash when I used it without driver verifier on. I'm still at a complete loss for the faults, so could be suspicious  RAM, or ...any of the new hardware I guess. Or just Windows updates sweeping in and wrecking stuff.
Reply
#2
Thanks for the report. It might be more useful to see the problem from HWiNFO's context, so please attach the HWiNFO Debug File of the BSOD and I will analyze that.
Reply
#3
(01-31-2018, 08:55 PM)Martin Wrote: Thanks for the report. It might be more useful to see the problem from HWiNFO's context, so please attach the HWiNFO Debug File of the BSOD and I will analyze that.

Turned on debug in HWiNFO

Turned on driver verifier again, restarted and opened HWiNFO to cause the BSOD.

I have attached the .dmp file generated by HWiNFO below along with system specs.

cheers.

Might be worth noting I got other BSOD errors loading windows using verifier:
Driver portion must be nonpaged: nvlddmkm.sys
and
Driver overran stack buffer

The computer just doesn't like starting up whether cold or reset after a running for hours.

Checked RAM again with  memtest86  last night, nothings overclocked, everything should be up to date, reseated my memory and graphics. Might have to rebuild the PC with my previous PSU at this rate. Never had so many problems building a PC before lol.


Attached Files
.htm   DESKTOP-N4F8SEI.HTM (Size: 188.7 KB / Downloads: 1)
.dbg   HWiNFO64.DBG (Size: 49.67 KB / Downloads: 2)
Reply
#4
I don't think the BSOD in driver verifier is anyhow related to those other problems.
But if it crashes in "nvlddmkm.sys" (which is the NVIDIA driver), I'd try with a different GPU or drivers...
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)