its not your fault It just HP/Compaq has always been a awkward brand. I have managed to fix most of the glitches it causes. It seems to be mainly the laptop side, i have a couple of HP/Compaq desktops and they don't give the same errors.
My post was a reply to the post from @mxman2k Sometimes, systems return unexpected values (lazy or incorrect implementations by manufacturers). Fixing those edge cases in QT/MRP can not be done proactively, they need to occur first. Which they did, and @mxman2k is looking into the matter.
two methods so far i could use (once i worked out how to parse the results to determine what is what)... wmic process get processid,parentprocessid,executablepath or tasklist /v /fo csv the wmic way looks to be more likely as i can use a FOR /F loop and parse for specific processes such as explorer, powershell,othershells etc, it's just making the magic happen.
I would appreciate SN (HDD/SSD), MAC (LAN) and computer UUID on QT report. Do you planning this feature?
I was thinking of the MAC address ages ago, will have to investigate it because if more than one adaptor it may confuse things. I will look into what is the 'in-use' adaptor to check. System UUID Will see what can be obtained. HDD/SSD serial, if i can get that info i will have a play and see what i can do.
Something like this for network adaptor information? Code: =============================================[ Network Adaptor Information ]============================================= MAC Address Adaptor Name Adaptor 1 - 00:50:56:C0:00:01 VMware Virtual Ethernet Adapter for VMnet1 Adaptor 2 - DD:AB:4A:6E:A1:35 Realtek PCIe GBE Family Controller Adaptor 3 - 00:50:56:C0:00:08 VMware Virtual Ethernet Adapter for VMnet8
OK now have MAC and System Drive Serial Numbers... For security reasons I will remove those from the saved report. They will show on the Display output. Getting the drive serial number was easy, but i had to re-write part of the QT because it shifted the results around and gave some very odd results
@Elilama I have been looking through the code of the QT to work out where in the memory checking it was returning that 4 not expected error... If you can run the QT on that PC/Laptop under Pshell as you was when the error occurred, if you look in TEMP folder - ie CD %TEMP% and find the QTLog.log and post that it would help me find where it was crashing out. Thanks
[START] Set Date/Time Vars Completed. [START] Setting up program variables. [START] Sysnative Reg. [OSARC] OS Architecture - [x64] {via AR:3} [EDCHK] Parsed Edition Section Completed. [Result: EDReg-Professional, EDWMIC-Professional, EDCBS-Professional, EDCOMP-Enterprise] [EDCHK] RS4 Flag1 set. [EDCHK] RS4 Flag2 set. [EDCHK] OS Build Number: [17134] [EDCHK] RS4+ Detected - Ignore License Switch Check due to changes m$ have made. [GUIMY] GUI Mode. [HVCHK] HyperVisorPresent: [FALSE] [DCCHK] PartOfDomain: [FALSE] [PCCHK] PCSystemType: [2] [DSKOS] Query BootDisk/OS Install Date Section... [OSIDT] OS Install Date: 08/06/2018 10:14:21 {Localized Date Format} [DSKOS] DriveModel: SAMSUNG MZNTE256HMHP-000H1 [DSKOS] Drive Health Status: OK - The disk appears to be functioning normally. [DSKOS] Query BootDisk/OS Install Date Section Completed. [GFXAI] Query Graphics Adaptor... [GFXAI] Query Graphics Adaptor Completed. Results: [Pri: Intel{R} HD Graphics 5500], [Bits: 32], [Resol: 1920x1080] , [2nd: None Detected] [GFXAI] WMIC Screen Resolution: [1920 x 1080 pixels] [GFXAI] WMIC Video AdapterRAM: [1024 MB for 1 video adapter, {May not be accurate, if onboard/shared memory type}] [EVCHK] Environment Check {Win:10} {Kernel:10.0} {Bits: 64 Bit} [EVCHK] Environment Check {SkuCode:0x00000030h} {SKUText:Windows 10 Pro} [VMDET] VM detection... [VMDET] No Running Virtual Machine Detected. [VMDET] Check done for VM detection. [OSLNG] OS Language Check. [NETFW] .Net Framework Check. [PSNFG] Checked .Net, PShell, Generic Tools. [MSDM1] Check for MSDM Table validation... [MSDM1] Check for MSDM Table validation Completed. [RCPSH] Recheck PShell Versions... [RCPSH] PShell Versions detected section completed. [SCAN1] Scanning OS/BIOS/DMI/GPU Name... [SCAN1] OS/BIOS/DMI/GPU Section Completed. [SLICT] Detecting SLIC Table Validity... [SLICT] Possible Emulation Detected. [SLICT] SLIC Table Validation Check Completed. [MEMQU] Memory Query... [MEMQU] Extra Memory Checks. [MEMQU] Memory Banks Information [1:4096MB 2:4096MB]
Thanks I was looking at the memorybanks part as i was guessing it was either in that area or the part just after as it seems like some HP's not like the memory being intensively queried.
Yeah i was right, the InDepthSlotInfo routine is where it aborts... I might have to do a bit of tweaking in that if HP/Compaq is detected to skip that routine to prevent the crash.
which model is the laptop/pc where it aborts on the memory as the QT not checked that side at the time of the crash. I can hopefully pre-check for that specific model and if it present to skip the in-depth check. What i have found is that HP/Compaq have some very odd memory organization, some memory devices are 'tagged' as System ROM, or just a space, i have a voided database but i only found System ROM so far in my HP SFF desktop. When you have time if you could run this command line either in a CMD or PS prompt, i don't think it needs admin rights but won't hurt. Code: wmic memorychip get DeviceLocator /value and post the results. I am guessing that HP may have another variant which i need to add to the void database as those such as System ROM do not return correct values as they are 'locked' which causes the abort message. It must be in Bank 4 (or it could be Bank 3) as i have to check from 0 upward as not all makers start at 0 *sigh*. Many thanks for your feedback, this helps sort these glitches out to make the QT a better program.