Jump to content

danger007

Registered User (Promoted)
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

6 Neutral

About danger007

  • Rank
    Settling In

Profile Information

  • Location
    USA
  • Interests
    Computers, gaming

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

    Well I know who should demand a partial payment for every user helped, TechInferno and Svl7. Dell/AW should have to share a % of all their warranty contracts they sell. Since they don't provide much support *cough* anyways, why shouldn't those who do the tinkering and carry the support burden that Dell/AW should be doing not be rewarded by Dell\AW. Heck why not give these experts the models, source code, bios data, etc., they could then outsource to a new way, tech forum experts. Once again thanks to svl7 for the bios mods. Thank you also to all the members to Tech Inferno who without many of us would be starring at a blank screen. For those who want to get the best out of the parts that might be limited by companies like Dell\AW this is your place to come. The drivers are very reliable and are often referenced by many sites. I don't think they would always be mentioned if the drivers weren't top shelf. This is what I would have expected Dell to provide with my Alienware M17x R4, after all I pad a premium and it should be for just the alien logo or fancy looking case.
  1. danger007

    Fighting the heat in notebooks

    I knew that but I wanted to make sure the other method showing a line of thermal paste was correct since I followed that for my initial pasting (I didn't order the pricey thermal paste until I knew the GPU would work in my Aw M17x R4 (I know it should but didn't want to spend it on the paste that can't be returned). In regards to cover, that is true. I know I asked Coolermaster since I have their HAF-X case about adding better dust filters to the outside, but they said the point of the HAF is High Air Flow, you just have to clean the grills more often and putting things on the back would reduce the flow of heat out of the case.
  2. danger007

    Fighting the heat in notebooks

    @Mr. Fox Instead of creating new topic, will continue the topic about heat. I have a 680m that I want to properly get thermal pads and paste for. It seems the top 2 choices for the GPU Thermal Paste (TIM) is Artic Mx-4 and Gelid GC Extreme (saw IC Diamond 7 but also saw warnings with use). I know the difference between the two is minimal +/- 1-3 C (I don't plan on any massive overlock, I might bump up the clocks by 50mhz at most if at all) however I am sure the generic stuff included with the card wasn't really great. I saw that @killerii shows just putting a pea size drop on the CPU, but does that apply to the GPU. I don't remember whose video I watched (want to say Eurocom but could be wrong) where they show dragging the tip so you apply a thin line down the middle of the GPU. Which is right, a pea or a thin line? Finally the pads is what has me worried. I have seen mentioned pads needed range from .5, 1 and 2mm (as mentioned or hinted to in all the various post here on techinferno. Obviously by looking at the card itself you can see the memory is very low, so I would assume 2mm on those, .5 on the highest parts (those odd colored squares with the little chips in between) and 2mm on the outside edge of the card. I see that the FujiPoly is majorly expensive. I have "sticky" fingers as I had issues with putting the pads on. So I wasted some pads. So I am have seen Laird, 3M as options for pads, any others advised (I saw the instructions for putting actual heatsinks on each part, but that is probably beyond my capabilities at this time (parts so small compared to laptop). My 680m, running the Uningine Valley Benchmark with: AWM17x R4, with original 3pipe 100w Heat Sink and proper x bracket DX11 High Quality Tesselation Normal Stereo/MultiMon - disabled AA off Full screen with system resolution (system is 1920x1080 I would think). I got a score 1011, min/max 7.5/90.9, fps 40.1 the card hit 66c and no higher (please note it is MSI 4gb in a AW M17x R4 and it has only been in the system for a week - so I know the thermal paste and pads aren't at their peak efficiency yet). Any advice would be of great help.
  3. danger007

    [GUIDE] NVIDIA VBIOS flashing

    I will say that in almost ALL, keyword almost all bios/video bios updates dos is the preferred method. Remember all those services, all those devices, your security software, possible printer drivers, constant updates from social media, and any software that is loading at startup adds layers that the update must travel around and through. It could get corrupted at any stage and you will not know till your system is bricked. Even going back several years, while companies produce in some cases produce both a windows and a dos version of a firmware or bios update, in most cases people have problems when doing it through windows. Dos there is no startup tasks, no device drives loading, no security software or anything else loaded except what is need for dos to load on that bootable media. That is why they are stressing the Dos and not the Windows method. If you look at ATI (I think this site or one of the others) say the same thing for AMD/ATI cards, use the dos version do not use the windows version. While you might have success, remember just how Windows OS install has issues that seems to be on a case by case basis or system type or if it is upgrade over an old OS, incompat software/drivers/devices, that is the danger as well of seeing one person having success, you can't duplicate their windows environment. You ask how if you have for example you are running Windows 7 64bit Service Pack 1, just like me why aren't we the same, well i probably don't have the same motherboard, or the same video card, security software, social media apps active (in my case I don't load them), different NIC, different USB controller, different CPU, heck different memory clocked at different speeds, might not have all Windows updates, might have to have downloaded other updates from Windows UPdate that you don't, etc. etc. DOS is just simpler. Sure your CPU/Memory affects performance along with Hard Drive however dos is dos more or less on any machine, I am speculating on this that most dos versions (like the choices you have in rufus to use, differ in that they aren't microsoft dos or they have added commands or more ability to be modified - as I said I am guessing on this point, that differences then don't impact the update. WHICH NVFLASH VERSION DO I HAVE? *Dos version will only come with nvrflash.exe and cwsdpmi.exe *Windows version will come with nvflash.exe and nvflsh32.sys and nvflsh64.sys as the last two files are for running in windows. The Windows version does drop to dos (at least the few times I have tried the windows version) but it is not running in the same dos environment as the pure boot from USB with Dos.
  4. danger007

    M17X R3, win10 or win7 till the end ?

    Something to add, but it affects the future of laptops and desktops. Microsoft has essentially stated now that it will support Intel GPU's 6xxx at least to 2018 instead of the earlier 2016 cutoff. However they are still remaining steadfast on the Caby Bay (7xxx series - spelling might be off), will not work in Windows 7 and most mobo makers are saying they aren't going to bother to develop drivers for Win 7 and Intel 7xxx (since it is such an old os, despite the fact that Win 10 still doesn't have nearly 1/2 of the current Win 7 domination of the current OS (including Mac, Linux). However the Win 10 is not proving to be the Win 7 killer it was going to be. MS has no choice however to try and clean up the bloated code starting with Win 10. There is still code there from the Dos Version of Windows (2 I think). They have stated they are worried because the people who wrote some of that code and forward through the other Win OS versions, are either retiring or have past away, leaving current coders with problems of how to remove the old code where still present and bring it forward. Another thing I remembered they stated when XP died (EOL) that any patches/fixes/updates put out for any OS above XP (don't think they ever mentioned Win ME) would more than likely expose errors that would probably be present or appear partial in XP code and therefore since they are not doing anything for XP anymore but virus/firewall (defender) updates and hence it would then be probably easy to take the current issue for OS above xp and use that to hack xp. So I am assuming same thing with Win 7 when it reaches EOL. I would REALLY SUGGEST AND ENCOURAGE if you have a spare or old hard drive (obviously laptop for laptop and laptop/desktop for desktop) claim your free copy of Windows 10 with your AW license. Don't worry about using it, just get it claimed so you don't have to pay for it, remember 6 days left and if others wait till the last minute, then the time it will take to download will be as bad as those first days of release, SLOWWWWWWWW!
  5. danger007

    MSI GT70 ONE 4GB 680M which bios ?

    Is there a way to run the new drivers OC but at stock speed if you don't want to overclock? I am not doubting the Ocing of the msi 4gb/2gb, I am just one of those who prefer stock (for warranty purposes or heat reasons) - and no I am not anti-ocing, I like to see how well a part (generally) does without the need for Liquid-Nit, a 10 ton copper heatsink, 10 ft tall heatsink, as that will speak to the quality of the product and if it is being pushed to near max at stock speed.
  6. Well new update. Under the advice of responses here and 2 other sites, I finally tossed in the towel on the AMD and went fishing for a Nvidia 680m. Yes there are more powerful cards but this one was designed to work with the M17xR4, so modded anything needed (as long as the card is the true Nvidia 680m 2GB model for Alienware M17xr4 or Dell). Since I only have a 30 days return on it (no restocking) I decided to get it into my system and do the normal clearing the bios/cmos and then starting the install of the nvidia drivers. However when in Optimus mode, the 680m refused to load (windows error code 43) no matter which of the 3 official drivers from Dell I tried. Okay lets go with the good old, manual selection of graphics. Instead of Red lines on the screen I get all these ---- mashed together in 5 or 6 layers at a time all across the screen, but unlike the AMD lines, these don't affect me being able to see what I am doing or typing. So back to day 1, back in early May 2016 again. No dgpu only igpu working. However it is much more stable than trying to troubleshoot the AMD. Things I notice no matter if in normal mode/igpu, normal mode/dgpu (remember with AMD I could not get into windows, only with the Igpu) or safe mode, the Nvidia shows error code 43. When I boot normal/igpu, I run gpu-z. Unlike the AMD, I cannot get a bios version and several other settings, almost as if they aren't there. Oh I bought the video card from comp_eve on Amazon marketplace since that I felt was slightly safer than ebay or craigs list. What am I not seeing or doing? I ran the extended ePSA test and every time it errors on the video card when it is set to Nvidia as primary, with a memory validation error. I tested moving the memory (system/ram) around the 2 slots and no difference. Help!
  7. Hello again. Well I gave up on saving windows install and working on fresh copy. However with fresh copy, once amd drivers install, system will freeze up at the windows 7 box (I call it that, it glows and glimmers). I then have to go into safe mode, ddu and restart. I have every driver on system up to date. Tried Leshcast 14.4, 14.12, 15.7, 16.2.1, no luck. Upon reading elsewhere I noticed that my system has one of those nvram bios, where taking out battery isn't enough. What has bothered me is that on the first screen of the bios (Main), when you go to entries for Integrated Graphics and Discrete Graphics 1, they use to say Intel Hd 4000 and AMD 7970m, respectively, now just Integrated Graphics Intel Ivy Bridge and Discrete Graphics AMD Gfx. Even if I remove the graphics (amd) card, I can't get the bios (a13) to say Intel HD 4000 (or some combination of those words). I does detect and name the CPU type on the main page. So this is why I am starting to wonder if I have a bad nvram or corrupted data in the nvram (as all of this occured when my SSD install of Win764sp1 froze in game about 3 weeks ago - yes I am a determined type). Now I cannot find a guide that is exactly for the M17xR4. There are guides that say to short out the Cmos Clr location. Others call for the RTCLS to be shorted. Still others say look for a password bridge. Yet still others say move a jumper or pin (which I don't think laptops have because of being moved around). So I guess the question is, how do I get the bios screen main page show Integrated Graphics Intel HD 4000 and the Discrete Graphics 1 to show AMD 7970m (this also is a possible way it was shown, since I haven't seen it since I can't give the exact name it used but close to what I just called it, you will know you have a 4000 and 7970m in your system). As mentioned stuck at A13 bios, they flashed bios during repair to A12, so can't go backwards without major risk). Everything else is being listed with its proper name in the main page (ssd, optical, cpu, etc.). That is when I jumped on the NVRam issue in terms of not truely clearing the bios (with the old fashion way of pulling the cmos battery, laptop main battery and ac adapter, power on once, then go back and replace battery, etc.). Note after rebooting with amd driver in win installed, first attempt at system repair says "bad driver" but second and on just say no reason. I have even disabled the hdmi audio and other audio from Intel in device manager to make sure the AMD driver for audio isn't clashing with intel/Microsoft version. (Intel driver v 10.18.10.3958) Please put me out of my misery over this.
  8. Well new snag on the Windows 10 test install on that older drive. It doesn't like the monitor. Assigns it a Generic PnP but says it isn't correct and when I search the Windows Update site it says the driver I have is the best. Hmm. I tried using DDU, then installing Intel's most current Win 10 driver for the Hd 4000, and then the 16.3.5 AMD. Computer will just crash to error of Thread Stuck in Device Driver. Can't find anything that comes remotely close to solving this issue.
  9. I had been originally informed it was a sata 3/mini pci capable. It was only after buying and looking up more information that I found the screen I saw when I bought and what the sales person at Dell/Alienware incorrectly listed that msata as Sata iii when it was only Sata ii. I found out also I wasn't the only one who got duped on that. However it is supposedly a limitation of the HM77 chipset used with the Ivy Bridge CPU and supposedly they could have made it sata III but it would have meant they would have to alter how many USB 3.0 ports could be on the system (of course to me, they should have just put a third party chip on to handle extra 3.0 ports but oh well). While I lose the performance of the Sata III, it still is more than twice the peformance of the SATA III Mech. HDD. Also was the only upgrade option left for me. I already had 1 750gb and 1 1TB 7200rpm drives in my system using the HDD Slot 0 and 1 for 2.5". No one currently makes a 2tb 7200rpm 2.5" for laptops and probably never will. Not a RAID setup either. I just install a great deal of stuff, some of it is redundant in terms of software, and of course games take up a hefty amount of space. So that is why I had no choice but to go with the msata version over the 2.5" of the Samsung 850. Another reason is that I always do my drives in pairs. If I use a 3tb for my desktop to boot, I won't use it unless I have a 3tb spare to use as a clone (so that is why the 750 is still in the system, I haven't decided if buying 2 1tb HDD just to gain 250gb more space is very cost effective and why I had counted out the Samsung 850 in 2.5" format, after I give up nearly 200GB for OP I would really have gained nothing in terms of space. The day I bought my Samsung, they annouced a 2TB version but it was close to $800 or $999 MSRP and when I found out I was initially bummed out, but then I thought between the sata ii port issue, the cost and the warranty/150tb data limit I would not bother. I could have gone with a Seagate 2tb 5400rpm, but I have had issues with Seagate drives and I had a 5400 on my previous laptop (of course that was a PATA not SATA) I swore never again to use 5400 as an every day use, just storing data/backups/clones. Reviews seemed to backup at least to me that a 5400 would be a bad choice for a gaming laptop. I did further research on the registry. I looked at the clone of the SSD and my desktop drive as well as my test drive (I use it to test software before it is allowed on my desktop, don't like being a unpaid and unknowingly a beta tester) and discovered that all copies of the reg on my SSD inside my laptop appear to be too full of excess entries to fix, so I now admit defeat on saving the current install. So based on what you have suggested this is the plan I am going to schedule for: 1. Take the 750GB that I mentioned above which was an old clone of the system from late 2015 and try to install Windows 10 on it. Then use that as a way to find out for sure if the AMD is working. Since that drive was messed up as well when I tried to use it to help fix the current install, no loss in the try then. 2. Clone/Ghost via Acronic onto the SSD the Jan 2015 version of the system and then just apply the updates between then and now. - What I have to decide here is whether to attempt to apply an updated vbios that I found on another site that starts with Tech, since I don't know if I really have earned the right yet to download from here (I have the promotion, but I haven't been able to really help anyone else yet, which is why I say I haven't earned) and then A13 or A13 and then the vbios. I know I would need to do these last two after the clone is working on the SSD, since it was done under the A12 bios and 015.017 vbios. 3. If clone/ghost fails to work, I will then go for a clean install as you recommended. The question then becomes update the system and video card bios. Of course which one first A13 or vbios and should they be done before I start the install, so I don't run into issues of the past with the different bios from dell (between I think the A09 and A11 or A10 - it hosed my system back then so I had to restart). I also will need to decide on the exact drivers for the Intel iGPU, MEI, Gb Ethernet and any other drivers that are newer than what Dell provides.
  10. In regards to A13 being on the Windows 8.1 page, do you think there is something in the bios code that could create more problems, since it isn't on the Win 7 page? Also if I do try to update the vbios, is it already included in the A13 bios or should the vbios be updated before the A13 sort of like once you get past a certain bios A8 or A9 that if you have A10,11,12 it is very difficult to drop back to older bios to get the unlocked version on. In regards to Win 10, after I read that post about Win 10 and Nvidia and Panels going bye-bye I am curious to see if AMD is having same issue or if both companies having same issue and since AMD does have the commanding lead in number of users, that they are underreported. How about I give you my computer and I can have your M17x R4, then problem solved - just kidding need to find some humor in this nightmare. The clean install could be my last desperate step. I only have 1 Samsung 850 Evo 1Tb msata, of course couldn't do two in the system since the only other port in the system is used by the Intel Centrino/Bluetooth combo mini-pci card and I haven't heard if anyone was able to convert it to a msata slot, without using an unlocked or locked bios. Of course if I got a Samsung 2.5" Evo instead of msata that would allow the clone. Now the clone of the SSD I have on a Mechanical HDD from Jan 2016, I am just starting to debate if I might consider falling back to that version, wouldn't have too much to reinstall. I still think something in the startup of the registry or the uefi/bootmgr/bootrec/bcd/bcd00000000 is out of whack somewhere and I just can't see it. I do however think I found an explanation to the repeated Did not Load Driver notices in the ntbtlog. I compared the registries by loading hives, exporting them and then comparing. From the Reg on the clone that I assume is still good, it might list the cpu once. While under the current reg on the current drive I am trying to fix, the registry in almost each of those drivers being listed as not loaded, they show up in almost a 1:1 correlation to the number of did not load drivers. One thing that has me worried in Norton. I know they have a way of getting in front of a system restore if you don't turn off a setting Norton Product Tampering and ruining the restore. Saw it all through xp, vista, and 7. While it might protect against someone trying to undo Norton, it has in all my cases that I have encountered screwed up system restores. I now wish I had allocated enough space on the SSD for at least 1-2 more system restore points. Of course the problem would remain that if Norton is hampering the restore effort, it would end up with same results. All I do remember is that when I did have the system in normal mode on an older clone from 2015, I noticed the BCD0000000 key in HKLM was missing. Since that is built off of the stuff on the system reserved 100mb UEFI and they registry works together with it (supposedly can't edit the bcd0000000 registry key) so I don't know if with it missing that even if I got the bootmanger/uefi stuff all sorted out, would it rebuild that key or not. It is just like I put out one fire and think I learned what not to do and then another fire is burning elsewhere showing I didn't find the solution I thought, and it repeats over and over. Sorry sounding like gibberish now, 5am right now, better stop before I give away my social security number, address, bank pin and password!
  11. danger007

    M17X R3, win10 or win7 till the end ?

    I don't know if I would after reading the article at the beginning of this forum, in the owners lounge, issue with Nvidia and panels. Go to page 19, top article plus the link they provided. It is from 2015 Nov, but it would leave me thinking twice until a year with no problems.
  12. Now this is scary. I remember a few years back, there was Starforce protection and everyone said it was destroying optical drives, a boycott was called for any game using it, magazines would now put what kind of protection the game had, and the company challenged anyone to prove their software did damage to hardware, and lets not get into software. The net was as active as it is now so it was really hard to find out what the true story was on Starforce. In the end, Steam came along and most companies saw Steam as an easier way to protect.
  13. In terms of physically removing it, no. In terms of killing the drivers, I have not deleted but instead renamed each and every amd/ati directory with a _disable at the end (since I might need to have them so didn't delete). Went into the registry (well loaded the 5 hives) and yanked out the key amd/ati entries in the various software areas (but I didn't do a total removal from the sections that could be drivers, since there could be several drivers that are needed otherwise, but with an AMD product in it, I don't know as well what I can zap in the registry for them (I make a backup of every entry I do remove or alter, once again in case they need to be restored). I also did run the ePSA bios test from Dell and the thorough test on the 7970m and it passed 3 different times with no errors. What I am thinking happened in terms of the bios just seeing ivy bridge and ati gfx is that once the drivers are working in windows normal they will send or update the bios (meaning using the dell drivers as the base and then upgrade to current intel and amd drives and not use the leshcat drivers since they don't appear to be updated anymore). I have thought about reflashing the bios or flashing it up to A13 (but the fact that the A13 is not on the official driver page leaves me concerned as towards the stability of the bios, since I can't trust Dell and won't be their beta tester . I just wish the Nvidia MXM laptop video cards like that nice 980 you have weren't so expensive. I figured I would much rather put it towards a new laptop with it in, so I am stuck more or less with the AMD (lesson learned). However I think this laptop will still be around for a long time. If I can save myself from reinstalling, it could be back up and gaming, I mean doing productivity work. The other theory I have about the AMD, is that in safe mode it isn't suppose to load any drivers other than what is needed to run the Windows barely. So if I am not wrong, the VGA driver (generic) should be the driver coming up. I know that in safemode as it list out the drivers it is loading if I rename amdkmpfd.sys so it isn't there, then I get a 0x07b error, and the last driver it shows loading is classpnp.sys. If I allow the amdkmpfd.sys to load, then it shows as the last driver to load before it switches to the black screen. Most if not all of my boot logging attempts always fail at hal.inf (and like others on the internet, tons of other drivers fail or load and then a few entries down fail, things like battery.inf, the cpu.inf and on,) I went through that and couldn't really pick out the issue and there are few things mentioned about hal.inf fixing, which again I am assuming probably has something to do with the bootmanager/bootloader/uefi stuff under diskpart and bcd. Thank you however for your suggestion/solution you offered. I want to hold out on actual physical removal to the very end if I can. In regards also to your suggestion, I sadly can't identify the bios version, but I am sure it is a non-uefi compat. version so I have my computer set to load legacy drivers in the bios. If dell knows there is an issue I wish they would release them instead of hoping we will just buy a new alienware - ha ha. UPDATE: Sat, May 28, 2016 10pm, I went ahead and removed the AMD 7970m from the system (was surprised how easy it was and I removed it with heat sink on to avoid having to deal with re-pasting), no luck, system still failed to boot into safe mode or normal mode, once again a black screen and free roaming mouse cursor. UPDATE 2: The vbios sticker, appears to be 015.017.000.000.042717
  14. Well I have now banged my head against this wall for a week. Here is the basics of my system, all other parts are standard: Alienware M17xR4 (delivery date May 2012) Intel 3720QM processor w/Intel HD 4000 iGPU AMD 7970m 015.017.000.000.042717 (if I read the right sticker) Samsung 850 Evo SSD msata 1TB (removed other 2 Mechanical HDD's to simplify troubleshooting 8 GB Ram Windows 7 64bit service pack 1 - installed fresh not a factory install, manually installed drivers myself (Winupdate last run in Feb 2016, then ran it on May 17, 2016 with a restore point being created before the windows update started, windows failure May 19, 2016 approx 10pm local time for me) System Bios: A12 Overclocking Notes: No overclocking attempted, ever. All parts are running at system spec settings Driver notes: AMD are Leshcat drivers 15.7 WHQL Unifl. IntelRST 11.x - version required with Dell drivers for Alienware OSD, Respawn, and other related software, all drivers where possible were most current on site or by maker of product, i.e. Intel Management Interface) Trouble started: While I was playing a game a week ago, the computer froze, no mouse movements, alt-f4 would not close the program, no keyboard response. It was typical as this game has issues with the switchable graphics and only sees the Intel HD4000, even though in the AMD CCC I set it Max Perform (main reason for running Leshcast drivers since Dell and AMD had old versions and/or drivers that were having issues or had the CCC lock some programs into one performance category or another and user couldn't change). Inital Action Taken: So when I rebooted nothing showed up. So I did my normal routine, windows recovery environment off Windows 7 Sp1 64bit retail disc. Nothing happened. sfc /scannow wouldn't run, chkdsk with the various / settings found nothing. I thought this was strange never had this issue before. So I figure well lets go into safe mode and find out what is going on. It just went to a blank screen with a mouse cursor I could move but no shortcut keys brought anything but sticky keys up. After spending hours trying different things, I started to get the 0x07b error. So I did something I don't like, system restore. The only restore point I had was just before a Windows Update was done. Now everything started to go wrong. I would find one solution, but it would not work. Possible Mistakes: I deleted the prefetch directory and removed the Panther directory, in hopes of resetting the prefetch setup. Trying to learn how to put back together the Windows Boot Manager/BCD. I can't confirm if the BCD has been configured in the registry or not since I am only able to load the 5 hive keys in the c:\windows\system32\config and the date on the registry backups were almost 2 hours after the problems started, so they have been of little use. No additional restore points, just the one that I already tried and of course that leaves me with nothing. Reading to many forums Some of the Solutions attempted: rename amd drivers and oem file safe mode safe mode w/networking windows system repair x3 sfc /scannow - won't allow rebuilt the bcd, uefi partition correctly labeled adjust entries in reg to remove amd/ati (but made backups before deletion of the keys) removed all drives but the SSD and no usb devices ran Norton Tool (ISO) for scanning for viruses/malware - results clean as a whistle (and that was with SSD + 2 HDD). Other Notes: I have seen about 5 different errors show up in the Windows RE, but they change frequently, I get the Boot Status Indicates that the OS booted Successfully. I even put in an older clone of this computer, it was from around August 2015. It got into Windows normal mode. I looked around in the SSD for some sort of errors, bad files, etc. Then I made the mistake of seeing if I could boot again into Normal mode on this clone. Opps! Now it won't boot. I can off and on get into safe mode on the clone (not the ssd). Finally it went to the black screen with mouse cursor. I gave up and removed it as it obviously wasn't of much use now. The Alienware model physical installation location of the Msata part is not at all easy to get too, as it all but requires a system tear down almost down to just the frame holding the motherboard. When I had access to safe mode/normal (fyi, I do not have either ways to access Windows) I had Samsung Magician 4.7 software check the status of the SSD and no issues. A new issues that started to appear was in the bios of the laptop. It no longer called the discrete graphics AMD 7970m and Intel HD 4000, now calls them ATI gfx and Ivy Bridge, respectively. I eventually got Windows RE command Bootrec /scanos to say there was a windows install. Now it says there isn't, so it sounds like the BCD/UEFI Boot manager/etc is again wrong. Where am I now on this problem: I just don't know what else to do. I want to try and avoid a reinstall as it can take a long time with all the software and *cough* games I install. Didn't bother contacting alienware as it is really Dell support and someone reading a script that tells them to have me reinstall immediately, so pointless. I can use the help at this point. I have way too many websites/forums, etc. bookmarked it could take years to clear all of them. So I feel I have reached that point that this problem is beyond my knowledge or expertise or lack their of. UPDATE: MAY 28, 2016, Sat, 10pm, as noted below I removed the GPU to verify it wasn't the 7970m, while out I think I came across the sticker that shows the bios version of the video card, it was the only sticker that had a proper looking vbios, 015.017.000.000.042717
×

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.