Squall Leonhart

i can't say i ever had issues with 391.35, it might be just your unique mining configuration in that case Xixou,

But now Driver is corrupting memory, I've had bsods with aida64 and gpu-shark so far, others have with precision and msi ab Fiery, does AIDA64 refresh sensors when running in the tray but no output panels or lcd's are set up? asking because if nvidia tries to repro the bsod issue on aida64 they'll have to do it on the GPU info or Sensors if the refreshing is paused when the window isn't active.

Blast from the past, but i just found an nvidia txt file covering this issue XD http://download.nvidia.com/open-gpu-doc/gk104-disable-underflow-reporting/1/gk104-disable-underflow-reporting.txt

Fixed with 397.64

I've just done some file drop trickery to get aida64/gpuz to use an older nvapi to stop the leaks, same with the nvidia containers

r397 fixes one thing and breaks everything else on windows 7, any sensoring app you open leaks GDI objects Aida64 included (as of 397.55)

Follow up post since others are reading this "Commit Size" is titled "Page File" in windows XP/9x and certain utilities made by a Unwinder, but it does not reflect the amount of of actual on-disk page file in use.

ooo.... so the lack of an actual register is why my 10-10-10-27 ram shows up as 8-10-10-27 in CPU-Z/PC Wizard and 11-10-10-27 in AIDA64/HWInfo after resume from S3 It's pulling a last known value from somewhere in different ways.

I was reading a review just now from a certain website, and the reviewer has blamed Aida64 for not being compatible with Threadrippers UMA mode on its less than perfect memory bandwidth. This same reviewer went on to bench a bunch of video games in UMA, just because it was the default setting completely ignoring the fact that the NUMA setting is intended for gaming appication. He might have well have been advertising for Intel with the gaming scores. IMO, its time these has beens leave the hardware journalism business if they don't even understand whats going on anymore.

They do, however only the VRAM of the 1080 is returned, this probably comes back to the fact only the primary display driver is listed though, so nothing can be done about that

Windows 7 x64 with latest patches. was running a heavily modded skyrim last night, and video memory up till 4096MB was reported correctly, anything over would start again at 0MB. This might actually be a limitation of windows, i see in Process Explorer the dedicated memory value caps at 4096MB. GPU-Z / Nvidia Inspector must be getting memory usage info from nvapi then :<

Also, AIDA64 doesn't at all show any DirectX Video information for secondary display drivers (devices) I have a 1080 and 1060 in this machine, only the information for the 1080 is shown.

It seems when vram usage passes 4GB, the aida64 values for the used GPU begin showing very low numbers. This i what i see in Aida64, where GPU-Z and Nvidia Inspector show >4.8GB used. Utilization GPU 98% Memory Controller 46% Video Engine 0% Bus Interface 5% Dedicated Memory 609 MB Dynamic Memory 699 MB DirectX Video info shows Direct3D Device Properties Total / Free Video Memory 8192 MB / 3385 MB

Ok, i've got some interesting information on this. The chipset page lists the following of a system currently running the marvel sata, jmicron sata, and nec usb 3, with a geforce 550ti and renesas usb 3 card installed in the bottom 16x slot PCI Express Controller PCI-E 2.0 x2 port #1 In Use @ x1 (Marvell 88SE9123 SATA 6Gb/s Controller) PCI-E 2.0 x2 port #2 In Use @ x1 (NEC uPD720200F1 USB 3.0 Host Controller) PCI-E 2.0 x16 port #3 In Use @ x16 (nVIDIA GeForce GTX 550 Ti Video Adapter, nVIDIA GF116 - High Definition Audio Controller) (top most pci-e 16x 2.0 port) PCI-E 2.0 x16 port #7 Empty PCI Express Controller PCI-E 1.0 x1 port #1 Empty PCI-E 1.0 x1 port #3 In Use @ x1 (Renesas uPD720201 USB 3.0 Host Controller) (bottom most pci-e 16x 2.0 port) PCI-E 1.0 x1 port #5 In Use @ x1 (JMicron JMB363 SATA-II RAID Controller) The location of the added usb 3 card is confirmed by device manager, which shows it running off the ich10 pci-e root port, even though it is in the bottom most 16x 2.0 slot. in my present Rampage II gene setup, i have a XFI soundcard in the second 16x slot, and it is shown as operating off the x58. I am therefore led to believe, that unless a card is placed in the 3rd pci-e 16x slot, the 4th one is not actually able to connect to the x58 root hub.

both are connected to the JMB chip presently, one connected to the rear esata port, and another connected on the case esata port. both of these will be going internal when my new build is ready.

JMB363, 1 esata, 1 internal sata, and a pata port for 2 devices.

All im doing is selecting the MX300 after the MX200 and vice versa and the smart fields come back wrong, some of them duplicated or missing. This could just be a Jmicron glitch, or one that only occurs when used with MSAHCI drivers, jmicron drivers are slower and buggy, and don't work with SSD tools well at all.

it hasn't, im guessing it might be the controller doing it

The MX200 is the first in the list

I see you have added the mx300 in the new beta I am seeing some odd GUI behaviour though when switching between the two ssd's though involving the smart fields If i select a HDD and then the MX200 or MX300 i see this mx200 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 15201 OK: Always passes 0C Power Cycle Count 0 100 100 84 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 95 95 178 OK: Always passes AE Unexpected Power Loss Count 0 100 100 76 OK: Always passes B4 Unused Reserve (Spare) NAND Blocks 0 0 0 2586 OK: Always passes B7 SATA Interface Downshift 0 100 100 15 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 63 49 51, 24, 37 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 4695 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 95 95 5 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes F6 Total Host Sector Writes 0 100 100 22.84 TB OK: Always passes F7 Host Program Page Count 0 100 100 1533394129 OK: Always passes F8 FTL Program Page Count 0 100 100 282356913 OK: Always passes mx300 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 154 OK: Always passes 0C Power Cycle Count 0 100 100 8 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 100 100 3 OK: Always passes AE Unexpected Power Loss Count 0 100 100 5 OK: Always passes B4 Unused Reserve (Spare) NAND Blocks 0 0 0 1936 OK: Always passes B7 SATA Interface Downshift 0 100 100 0 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 67 51 49, 27, 33 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 0 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 100 100 0 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes F6 Total Host Sector Writes 0 100 100 860.07 GB OK: Always passes F7 Host Program Page Count 0 100 100 56394814 OK: Always passes F8 FTL Program Page Count 0 100 100 16334715 OK: Always passes However, if i switch from SSD to SSD, it will do this mx200 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 15201 OK: Always passes 0C Power Cycle Count 0 100 100 84 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 95 95 178 OK: Always passes AE Unexpected Power Loss Count 0 100 100 76 OK: Always passes B4 Host Program Page Count 0 100 100 1533394129 OK: Always passes B7 SATA Interface Downshift 0 100 100 15 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 63 49 51, 24, 37 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 4695 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 95 95 5 OK: Value is normal CE Host Program Page Count 0 100 100 56394814 OK: Always passes D2 FTL Program Page Count 0 100 100 282357425 OK: Always passes F6 Total Host Sector Writes 0 100 100 22.84 TB OK: Always passes F7 Host Program Page Count 0 100 100 1533394129 OK: Always passes F8 FTL Program Page Count 0 100 100 282357425 OK: Always passes mx300 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 154 OK: Always passes 0C Power Cycle Count 0 100 100 8 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 100 100 3 OK: Always passes AE Unexpected Power Loss Count 0 100 100 5 OK: Always passes B4 Host Program Page Count 0 100 100 1533394129 OK: Always passes B7 SATA Interface Downshift 0 100 100 0 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 67 51 49, 27, 33 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 0 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 100 100 0 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 FTL Program Page Count 0 100 100 282357489 OK: Always passes F6 Host Program Page Count 0 100 100 56394814 OK: Always passes F7 Unused Reserve (Spare) NAND Blocks 0 0 0 1936 OK: Always passes F8 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes

Here you go Fiery. smartdump.txt

I recently picked up an MX300 and a number of smart fields are listed as <Vendor - specific>. These fields don't seem much unchanged from the mx200, From the MX200 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Hours Count 0 100 100 15047 OK: Always passes 0C Power Cycle Count 0 100 100 83 OK: Always passes AB Program Fail Count 0 100 100 0 OK: Always passes AC Erase Fail Count 0 100 100 0 OK: Always passes AD Wear Leveling Count 0 95 95 177 OK: Always passes AE Unexpected Power Loss Count 0 100 100 75 OK: Always passes B4 Unused Reserve (Spare) NAND Blocks 0 0 0 2586 OK: Always passes B7 SATA Interface Downshift 0 100 100 15 OK: Always passes B8 Error Correction Count 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Enclosure Temperature 0 62 49 51, 24, 38 OK: Always passes C4 Re-allocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 SMART Off-line Scan Uncorrectable Error Count 0 100 100 0 OK: Always passes C7 Ultra DMA CRC Error Rate 0 100 100 4695 OK: Always passes CA Percentage Of The Rated Lifetime Used 1 95 95 5 OK: Value is normal CE Write Error Rate 0 100 100 0 OK: Always passes D2 Successful RAIN Recovery Count 0 100 100 0 OK: Always passes F6 Total Host Sector Writes 0 100 100 22.77 TB OK: Always passes F7 Host Program Page Count 0 100 100 1528632514 OK: Always passes F8 FTL Program Page Count 0 100 100 281716231 OK: Always passes From the MX300 ID Attribute Description Threshold Value Worst Data Status 01 Raw Read Error Rate 0 100 100 0 OK: Always passes 05 Reallocated Sector Count 10 100 100 0 OK: Value is normal 09 Power-On Time Count 0 100 100 1 OK: Always passes 0C Power Cycle Count 0 100 100 8 OK: Always passes AB <vendor-specific> 0 100 100 0 OK: Always passes AC <vendor-specific> 0 100 100 0 OK: Always passes AD <vendor-specific> 0 100 100 1 OK: Always passes AE <vendor-specific> 0 100 100 5 OK: Always passes B4 Host Program Page Count 0 100 100 1528632514 OK: Always passes B7 <vendor-specific> 0 100 100 0 OK: Always passes B8 End-to-End Error 0 100 100 0 OK: Always passes BB Reported Uncorrectable Errors 0 100 100 0 OK: Always passes C2 Temperature 0 60 60 40, 27, 40 OK: Always passes C4 Reallocation Event Count 0 100 100 0 OK: Always passes C5 Current Pending Sector Count 0 100 100 0 OK: Always passes C6 Offline Uncorrectable Sector Count 0 100 100 0 OK: Always passes C7 Ultra ATA CRC Error Rate 0 100 100 0 OK: Always passes CA Data Address Mark Errors 1 100 100 0 OK: Value is normal CE Flying Height 0 100 100 0 OK: Always passes < this field is named wrong for some reason, its the same as the writer error rate field on the mx200. D2 FTL Program Page Count 0 100 100 281716279 OK: Always passes F6 <vendor-specific> 0 100 100 8116072 OK: Always passes F7 <vendor-specific> 0 0 0 1936 OK: Always passes F8 Ramp Load Value 0 100 100 0 OK: Always passes

I would like to be able to hide the LCD items for sensors not currently detected or reporting values. I have a portable hdd that i watch the temp of on my g510 lcd, which reports HD4N/A, with the N/A actually overlapping the name of the sensor, this updates to the temperature of the drive when it is plugged in, but having the n/a visible in the first place is an eyesore.

There is a reason the XMP profile sets 1.65v 1.54v is not sufficient!

Yes, this (reportedly) has only recently been introduced with R337. I can honestly see Alexi(Unwinder) refusing to fix this.... and thered be no fix for d3doverrider anyway >.> Adding aida64 and gpu caps viewer to the list of profiles and turning detection/hooking off works around the issue.