Something very similar to that more than once. What I haven't tried yet, and I am going to now, is changing to different RAM sticks that haven't been touched by Windows 10, then blind flash the BIOS. I don't think you can get any more thorough than a blind flash. It forces everything, and the binary file used for blind flashing is an old version without UEFI support, much like the M18xR1 and M17xR3. There are motherboard contacts to "Clear CMOS" and "Clear MEI" and I have bridged those contacts with power to the motherboard as well. That doesn't seem to change anything... at least nothing that I can recognize.
One thing I have wondered... probably does not have any merit, but since this is a random glitch, what if I reinstalled Windows 10 again and see if whatever it messed up if it might somehow straighten out. Maybe whatever it writes to BIOS or EC glitched out, or maybe the ISO itself had an error that Micro$haft has quietly corrected to not call attention to itself. Maybe others affected the same as I have been download the same corrupted ISO and others that were not affect had a different ISO.
I am also wondering if re-flashing the RAM sticks with Thaiphoon Burner might flush out any bugs that could be embedded.
Edit: If anyone has a spare 7970M GPU or a pair for CrossFire they would be willing to let me borrow for a few weeks to see if this problem stays fixed with AMD video cards, send me a PM. I'd be willing to pay for the shipping both ways. I have AMD heat sinks and CrossFire cable, so all I would need is video cards for testing.
-
-
It seems most corruption to the computer BIOS happens during an upgrade rather than a clean install of Windows 10 - or so I've gathered from reading problems related to 10. Something to do with the UEFI tables that CAN be written to and resized by Windows 10.
I'd speculate that it has to have something to due with how Windows 10 saves the activation key from 7/8.1. Just my guess.PC GAMER likes this. -
Apparently its nvidia's and microsoft's fault and they should take responsibility but lets be realistic:they won't.
Our only chance is DELL/Alienware. They should be able to issue a new Bios/UEFI (not necessarily with new features) for the affected models that will perform necessary checks, clear whatever is written and flash the new bios values.PC GAMER likes this. -
I'm on the fence to try instaling W10 again as clean install and make a Image of my running W8.1. I want to check if i can reproduce the issue with the EDID corruption i had, or if it stays good.
I wanted to try installing W10 clean with drivers and use the 355.84 nV ones, and Report back if bricked again or worked.
@Mr. Fox
sorry to hear your EDID gets corrupted over and over and overmakes me sad.
PC GAMER likes this. -
After installing windows 10, the screen stays black on my clevo P157SM-A. There is also no output on hdmi and i cant access the bios. Strange is that i havent even install the nvidia drivers, but the screen stays black.
But i solved the problem when i took out the cmos battery for a few hours. also i had to remove the hard drive where windows 10 is installed and format it on another pc because with this hard drive installed the system freezes on the boot logo and i cant access the boot menu or the bios.
Maybe this can help somebody (and sorry for my bad english!)
PC GAMER likes this. -
If you want to see if it gets fixed, you'll likely need a new license for Windows. As has been said, it happens with upgrades and it most likely has to do with however Microsoft is installing the hardware key with a 7 or 8.1 license. Since this rootkit is already on your system, there may be no fixing it even with a new license. They really made a huge mess of things. -
I flashed the SPD on all of my memory modules and so far everything is holding. It's not long enough to draw any conclusions whether that will even matter.
One observation is that 345.20 drivers (the newest ones I can use that do not throttle) are the only GeForce drivers that do not add multiple monitors in my registry. I've never looked at this before, so I don't know what "normal" looks like. I've had no reason to care.
What I mean by that is, if I clean up with DDU first, with 345.20 the only EDID display references found in my registry are in a sub-key named "Device Parameters" in the following keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\SEC5448
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\SEC5448
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\DISPLAY\SEC5448
If I install newer drivers, I see three monitors under DISPLAY for some reason. One is named Default_Monitor and the other is named DEL1821, which I have never seen before. For Default_Monitor under Device Parameters the EDID was all zeros, SEC5448 has a valid EDID and the DEL1821 EDID is different than the SEC5448. I don't know why this is, or if it is even relevant. There was also reference to DEL1821 in one of the NVIDIA driver databases referenced in the registry with newer drivers installed. I cannot delete these keys and I cannot take permission/ownership of them like I can other protected keys. They are owned by SYSTEM and cannot be overridden or deleted. I even tried RegAssassin from MalwareBytes and it could not change the permissions or delete the keys.
I notice the M18xR1 currently has two (not three) with 345.20 installed. I am wondering if it was "remembered" by Windows and added to the registry when I was running a bricked LCD panel for flashing purposes. The key with all zeros for EDID is actually named "BAD_EDID" LOL. I edited the registry and did a copy/paste of the binary values from the good EDID under SEC5448 and saved it. It was interesting that my permissions allowed me to change the EDID content even those I cannot delete the registry keys or change permissions on them. After several reboots the good values have stuck in the "BAD_EDID" registry key. I am going to use DDU to clean up the M18xR1 and reinstall 345.20 and see if there is only one monitor reference in the registry after doing so.
By the same token, I am wondering if the Default_Monitor with BAD_EDID filled with zeros that I had on the M18xR2 was something Windows remembered and added to the registry earlier before the LCD bricked again. This is all really confusing and I don't really know why it is happening or what is causing it. It almost has to be something Windows 10 did since none of these problems existed before. Windows 10 is the only wildcard. I was running the same drivers (same old folder that is stored on my data drive) under Windows 7 and 8.1 since February with zero issues before installing Windows 10.
Edit: as a visual example, the screen shots below are from the M18xR1, which I have been using for hot-swap flashing with Linux before I got the USB programmer. The first screen shot shows multiple displays in the registry, including the one with the BAD_EDID key that I updated from all zeros to valid EDID. The second screen shot shows just one display with valid EDID after I removed the drivers with DDU and clean installed 345.20 drivers.
Before:
After clean driver install:
Last edited: Sep 22, 2015 -
Did you reinstalled system after EDID override by programmer? Try to install clean and then check if it'll corrupt it again.
Sorry if you already did that because im not up-to-date with this thread. -
PC GAMER likes this.
-
Well the brand new hard drive definitely rules out the presence of something stored there. This is some crazy messed up stuff. Broken to the point of not fixing.
Are you using the snipped cable and it's still bricking? -
-
EDIT: Its early... This is mine.
BAD_EDID is blank (0000 value) -
-
-
Wouldn't fret too much over multiple monitors in the registry; it's normal for gpu-switching systems. One has the display parameters for iGPU and the other for dGPU. Plus, it contains all combinations with internal + external display that have been used at one time. For instance:
- igpu + internal
- dgpu + internal
- igpu + internal + external
- dgpu + internal + external
; you flashed two versions of the 'panel nr. edid' (with different descriptors). Those are just the ascii strings to help id the panel (Dell inventory number is useless) and don't do anything. Only, what broke the display is the change to offset 0x14:
This was the same for all five corrupt edids uploaded so far. It's hardly surprising this bricks the display; 'bit 7 = 0' designates the lcd as a crt monitor. And, obviously, this breaks the checksum along with it, but that's merely a by-product. Question is whether you can have a non-significant change and still have a running display?
You could answer that question, actually;
Code:i2cset 1 0x50 0x7F 0xCC
There are some very nasty rootkits that could do this, surviving even a bios flash. It's possible MS or nvidia have had their code compromised ... or they've made a deliberate change somewhere, only to have that back-fire in certain scenarios. That may turn out to be a good thing, too; if the displays weren't bricked we may never have noticed something seriously fishy was going on.PC GAMER, Mr. Fox, Scerate and 1 other person like this. -
Just reinstalled W10 with UEFI and Secure Boot off, with the new W10 Pro TH1 Refresh ISO. So far everything is fine, installed all Drivers besides nVidia ones so far, new WHQL got released branch r355_00-177. Will try the 355.84 developer Drivers again and i will see if Display get's bricked again.
-
Should i be worried
Sent from my SM-N900K using TapatalkPC GAMER likes this. -
ok finished with installing, using 355.84 like i said before, let's see what happens. So far everything works, fun fact tho i denied Windows Updating via gpedit method, Windows Updates anyway
Attached Files:
ajc9988 likes this. -
-
Scerate likes this.
-
@ Topic
so far i restarted several times, shut down twice and so still working, of course i will try more and report. Installed Drivers + 355.84, installed Updates, disabled Defender and removed OneDrive, will now start ShutUp10 and move my "My Documents" back to my HDD drive and Startup Steam and install Chrome and stuff.Last edited: Sep 22, 2015 -
Only Option to prevent it "permanently" is to get the Enterprise Edition from somewhere....
EDIT: Permanently means you can delay it up to ten years. But IIRC security updates and Hotfixes will be forced on your rig on a monthly basis, regardless of your Settings.Last edited: Sep 22, 2015 -
TomJGX, deadsmiley, PC GAMER and 3 others like this.
-
Give Me Power - What is it?
Give Me Power - Download
It's from the maker of the nVidia DDU program. Basically you open the GMP program, and then use it to open Regedit from within the System32 folder. It then gives Regedit system level privileges to then delete registry keys that otherwise will not delete due to the permission issue.Mr. Fox likes this. -
Keith likes this.
-
So I decided to stick with this rotten disease for now. Cause it seems that it doesn't matter; the LCD's are bricking under Win 10 or lower and your rig is infected anyway as you sadly demonstrated!
But besides that I fortunately had no trouble yet. Great! Lesson learned.... -
CaerCadarn likes this.
-
Now I say that if we want Nvidia to fix this then all we need is just a beautiful video and that's it. More people is better. Just imagine how in the end you see another guy who is telling "And mine too" and his laptop's screen dies, then next jump to another guy and all the same.
And at the very end screen splits on 3 parts where all they (from their apartments with dead laptop on their hands) are telling at once: Nvidia, PLEASE FIX THIS.
Then black screen with text: There are over 3 tenth of people who already got their expensive laptops broken and the problem is that you can't fix it at all unless both change motherboard and fix the screen.
Please don't let them alone. Only TOGETHER we can succeed!
Call 1-800-NVIDIA!, 1-800-ALNWARE and 1-800-MICRSFT to complain about infected Nvidia-based Alienware laptops after Windows 10 upgrade.Last edited: Sep 22, 2015 -
Calling them really bad names is not beneath me.
I mean for it to sound really bad because, guess what? They are really bad, and so are their intentions. The whole purpose is to shock people into thinking. Sometimes you have to bang on the beehive a little bit to stir up the nest. We must never forget things like the evil of the Nazi empire or the psychotic radical perpetrators of 9-11. They were horrible beyond imagination. Micro$loth deserves to be associated with the axis of evil so I use the hyperbole to help people stop long enough to think and begin to connect the dots. I know some seem to go overboard with not liking it and acting as if it offends their tender sensibilities, but I don't care. It's like calling Micro$loth Satan in my mind, so that should only be insensitive to people that are fond of evil and want evil to prosper. I know some people hate hyperbole. I love it. I hate soap operas and romance novels.
-
I don't know if it helps. A few info from my case to take into consideration:
- When i went back to Windows 8.1 i used the factory restore DVD's. After doing that i connected my laptop to the TV. I also had the default_monitor key under Enum/Display so i believe that is normal. Maybe someone can enlighten us more
- Showing the display as PNP09FF is also normal since these are recognized as generic PNP monitors for the simple reason we don't have monitor drivers to install as in most laptops
- Last but not least:I believe the root of the problem is the activation storing process of Windows 10. I say this because when i wanted to try windows 10 i upgraded to my AW17 which had one HDD. Windows 10 was activated normally after the upgrade. After that i placed the HDD in the second bay and installed a brand new SSD in the first bay. Then i did a clean installation of Windows 10 on the new ssd which of course never got activated due to the hardware change. This is the reason why though i believe didn't corrupt my display. I kept using Win10 unactivated with all the updated drivers that would come out for 3 weeks, until i saw this topic.
I hope i shed some light and maybe some expert can make something out of that info.If u need any screenshots from registry let me know.Mr. Fox likes this. -
Robbo99999 Notebook Prophet
@Mr. Fox , any word from NVidia yet in relation to your bricked panels - IIRC you sent them in to NVidia to be investigated, or was it Dell you sent them to?
-
http://www.siliconbeat.com/2015/08/04/windows-10-upgrade-bug-makes-some-pcs-unusable/
So we have:
- Windoofs10/NGreedia Combo are bricking LCD-Screens
- Windoofs10 enables RootKits on BIOS Level
- Windoofs10 refusing to accept changing Hardware/HDD's/SSD's when trying to reinstall it.
- And last but not least: Windoofs10 makes your rightfully owned license poop away at will, probably after a failed upgrade.
So stay tuned for More happy days! -
And, to answer your question... nope, not so much as a peep from NVIDIA other than they cannot comment at this time. Understandably, the folks from Alienware don't know what's wrong yet. They did not create the mess, but stand to lose some money paying to fix an unfixable problem under warranty. So, I know they want it fixed as bad as we do.
Do you reckon there would be any real enthusiasts using Windows 10 today if there had been full and open detailed and highly technical disclosure from Micro$loth about how they were going to molest and abuse us all?Robbo99999 likes this. -
@mr.fox
Does the windows 10 bug effect the 2013 4940mx gtx 880m sli machines as well a friend updated to it ...as i want to buy i am curious what to do ..so far machine is working should i install windows 8.1
Sent from my SM-N900K using Tapatalk -
Daniel1983 likes this.
-
But he has installed it allready ...is it to late so far its working ..should i ask him to install windows 8.1 ...
Hope it wont die on me after i buy it
Sent from my SM-N900K using Tapatalk -
-
I mean, seriously? You're not that stupid, are you?
BAD judgement call man. Because once the problem manifests it can't be fixed (for now). -
I told him to send me some benchmarks etc and re install win 8
Some friends here in pakistan have uograded to windows 10 on there m18 sli machines with no problems since it came out .
Strange whats happening
Sent from my SM-N900K using Tapatalk -
-
I was just asking will re installing not cause an issue
Sent from my SM-N900K using Tapatalk -
-
I wouldn't count on 50% bricking chance and spending so much money, really!
You wanna have my rig? The virus is already on it and till today it runs fine. I'm playing this russian roulette for a while now! -
http://www.howtogeek.com/226308/the...crapware-can-come-back-after-a-clean-install/
https://msdn.microsoft.com/en-US/library/windows/hardware/dn550976
http://download.microsoft.com/downl...27CF905A80/windows-platform-binary-table.docx -
"Response Via Email (Josh) 09/22/2015 02:24 PM
Hey John,
Im working on getting some more details on this now, but the short of it is Dell will be the ones responsible for getting this fixed for you, im just waiting on getting contact over there that you can work with to get replaced. Its not a driver/software issue on our end.
Josh
NVCC"
This is what they sent me when I reopened the ticket with Nvidia (that they had closed out as solved).
They best have some compelling evidence, because that doesn't line up at all with what we've all seen. -
Scerate likes this.
-
-
Just because Dell or AW fixes the problem does not mean it is their fault or even that they are paying. They just become the end point for fixing the issue(s).
-
Interesting point. We'll see.
-
I wrote a few pages back that it will be Dell/Alienware that will clean up microsoft's and nvidia mess.
Lets just hope they will actually Delliver (lol) -
i hope it's a bios that lets us control the damn fans!
PC GAMER likes this.
*** Windows 10 + NVIDIA WHQL Drivers are Killing Alienware and Clevo LCD Panels ***
Discussion in 'Alienware' started by Mr. Fox, Aug 1, 2015.