I do not have fast boot set.
I do have another drive where I have Windows already on another spec installed. Can I just connect the drive via a sata cable or do I need to reinstall Windows on it?
I have an old laptop with the specs you can see here.(CPU:i5-3210M|GPU:Nvidia Geforce GT 645M| RAM: 2x4GB) The 1TB has Linux on it and a 256GB SSD with Windows I needed for a program. It is quite old and my question is wether I can “hotswap” the drive or wether the driver installed on it might cause a problem
You could try uninstalling any Medion and any other third party drivers that are on the drive while it is still in the notebook and just leave Windows on the device, your desktop will then hopefully just see things as if it were a first time install.
NB: been so long that I cannot recall if the present SSD is the SATA or M2 type so will mention both scenarios, if a SATA device disconnect it and if possible use a new SATA cable with the replacement device and make sure that you do not use the same SATA port that the present device is connected to, if your SSD is the M2 type just remove it from the MB.
So I had an m2 ssd and and removed it connecting with the other windows install on the ssd working in another spec.
Starting up it gave me the message starting automatic repair and throw me into the troubleshoot screen. Normally I would have clicked startup repair but I wanted your input. I am thinking that the windows install expects something from the other setup and the startup repair might fix that. I did not uninstall any drives as I looked at the device manager seeing only basic drivers and the chipset + GPU drivers from windows update.
NB: On Tuesday and Thursday next week I need to use windows on the other spec.So I am going to install it back on Monday I think
I did not uninstall any drives as I looked at the device manager seeing only basic drivers and the chipset + GPU drivers from windows update.
Any drivers from the other computer have to be uninstalled or Windows will try and load them and it was most likely the incompatible chipset drivers that tripped Windows up when it tried to load them.
So I should uninstall drivers while the system is running. So with DDU we used earlier I would uninstall the GPU driver and Intel HD Graphics. Do I need to uninstall any driver not named Windows Basic X?
Only drivers that need to be removed are the chipset, any add on GPU drivers+ the Intel HD drivers, the latter only because your other comp is an AMD platform.
Use DDU for any add on video card drivers the others can be done in Device Manager.
Ok I found the Intel Drivers and the GPU drivers. But I have no clue about the chipset drivers. Are they the drivers listed under Processors?
I have marked the drivers I think I need to uninstall
[ATTACH type=“full”]6601[/ATTACH]
We are looking for Intel Chipset drivers, info on Medion computers is hard to find and any support even more difficult to find so we will have identify the drivers ourselves.
Download and run DriverView which you can get from here
Save the results to text and attach to your next reply for us if you will.
There are other Intel drivers present but you may get away with just uninstalling the two identified below, I suggest that you save these drivers to a thumbdrive ready for reinstall when you are done.
You mention needing access to this drive a couple of days next week, do you want to put your thread on hold until after that.
[COLOR=rgb(184, 49, 47)]Driver Name : Smb_driver_Intel.sys
Address : 00000000[ICODE]84A10000 End Address : 00000000[/ICODE]84A1E000
Size : 0x0000e000
Load Count : 1
Index : 120
File Type : Driver
Description : Synaptics SMBus Driver
Version : 19.0.19.1
Company : Synaptics Incorporated
Product Name : Synaptics SMBus Driver
Modified Date : 08/01/2016 00:15:28
Created Date : 02/06/2020 17:02:55
Filename : C:\Windows\system32\DRIVERS\Smb_driver_Intel.sys
File Attributes : A
Service Name : SmbDrvI
Service Display Name:
Digital Signature :
[COLOR=rgb(184, 49, 47)]Driver Name : TeeDriverW8x64.sys
Address : 00000000[ICODE]842B0000 End Address : 00000000[/ICODE]842E0000
Size : 0x00030000
Load Count : 1
Index : 105
File Type : System Driver
Description : Intel(R) Management Engine Interface
Version : 11.0.0.1172
Company : Intel Corporation
Product Name : Intel(R) Management Engine Interface
Modified Date : 14/10/2015 23:26:42
Created Date : 14/10/2015 23:26:42
Filename : C:\Windows\System32\drivers\TeeDriverW8x64.sys
File Attributes : A
Service Name : MEIx64
Service Display Name: @oem3.inf,%TEE_SvcDesc%;Intel(R) Management Engine Interface
Digital Signature :[/COLOR][/COLOR]
My problem is that I need windows partition for a program every week on Tuesday and Thursday. As far as I know the program does not run under wine or other compatibility layers for .Net. So I there is no use to keep the thread on hold.
Can I use DIsm for the backup like this on an stick?
The easiest thing to do would be to back up all Intel drivers on the drive then delete them, fit the drive in the other computer then power up with your fingers crossed that it boots into Windows and allows you to install the chipset and GPU drivers.
It is only a temporary measure, M2 type SSDs are a good idea when they work ok but I`m afraid that they cause too many problems for me to ever invest in one, depending on how many M2 slots a MB has the SSD will either share resources with the CPU or bandwidth with the GPU and the latter is of particular note for causing issues, seen many folk that have been convinced that their GPU drivers were bad and all along it was their M2 SSD device that was tripping the PCI-E slots up.
So after I removed the Intel HD 4000, the SMB BUS, Intel Management System, GPU with DDU with a backup before. I connected the drive and turned the power on.
It booted up normal and let me to the login screen. Then I clicked to get my user and type the password. Then it greeted me with a bluescreen CRITICAL_PROCESS_DIED. After the reboot I could log in. Seeing the Desktop another bluescreen CRITIC… . Then it went to the recovery Screen. I did nothing and restarted. Got in short another bluescreen and after the 4th try I got into the Desktop after the Screen froze(after pwd type in). It came back and I plugged in the USB for the chipset drivers. After some crashes of the Desktopmanager and explorer I could start the installer only to see it crash as always when I tried it earlier (prev thread) at the hardware detection. Then I opened an elevated command prompt and copied the 3 minidumps to the usb (attached now as zip). After that I started the device manager and selected the driver folder for every yellow mark mostly PCI installing the drivers manual. After I got all installed the system seemed more stable. I do not remember clearly wether I ran MTB before the manual install or after but I ran it and attached a log with all checkboxes ( I feared a crash).
Overall we now have access to the system and not stuck in a install corrupted while it configured.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Tweet
Comment