Recent content by Diceman_2037

hi res screenshots and and the component vendors page

i think this senile old goof needs to retire and stop causing alarm over nothing, the components in the area are rated to 150c.

Incorrect, with the very final firmware updates made available for these parts, they support UASP on the Microsoft stack uPD720200 on 3.0.3.4 uPD720201 & uPD720202 on 2.0.2.6. That is contrary to Asmedia draft spec 1042 parts that appear not to support it.

The firmware does not fix the issue, it works around it by restricting it to 64MB pending investigation and fix.

The level of the trapped charge drops over time leading to a slower reading of data (as part of it reconstructs from ECC bits). When this occurs the C5 counter flips and refreshes data in blocks of 1GB by copying it to another part of the drive, upon completion the pending redirect counter...

checked on the 500GB i put in a qosmio for the first time in a long while and theres only 31% of life left lmao 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...

Issue has been around since late 2019 but wasn't too visible until late 2020 and on, nvidia got a lot of crap for it because its on nvidia parts that the issue is high profile, its worsened more since chromium devs went and used directcomposition for more and more aspects of the canvas...

This sounds like the black checkerboarding bug that has just been fixed in Windows Canary and Beta rings.

Be really great if Toms Hardware didn't regurgitate unsubstantiated claims. 23h2 (10.22631.xxxx) Does NOT have any indication of supporting WDDM 3.2, and SM 6.8 has not even hit feature milestones yet.

False, stop spreading misinformation

You'd have a point if it affected games at all.

The fix won't be in drivers till R540, standard QA for KMD changes is 3-6 months.

No it cannot! this Partition is still used on a converted disk.

It looks like M3CR046 has a bug where the SSD can fail to boot if restarted while the Pending sector count is flagging garbage collection duties.

Drivers do not cause WHEA errors, they only allow for already unstable hardware to reach a state where the hardware crashes and reports one.