St1000dm010-2ep102 Driver Update

0 views

Skip to first unread message

Zita Lifland

unread,

Aug 5, 2024, 7:15:45 AM8/5/24

to enscarebdo

Itried to install the chipset drivers after the graphics drivers and I couldn't. It said that the drivers were already updated. I had to uninstall everything and install the chipset drivers first and the graphics drivers second.

Today after opening windows, I encountered a problem where the screen became too big i also have no restore points and i couldnt roll back the drivers nor the old resolution ( 1440x 1024). Now it is stuck at 1024x764.

Thank you for posting in the communities. I can see you posted that the driver update made the change; may I please know what specific driver version caused the change? Usually, this issue occurs when the system is not using the recommended resolution, were you able to check the Display Settings of your system and check for other resolutions? You may also post here the SSU logs of your system so I can become more familiar with your configuration. You may download it at this link: -system-support-utility-for-windows.html. Additionally, if you are using an external monitor, please share the monitor model and cable port used. I will be waiting for your reply.

Would you prefer if we continue our conversation by email for the SSU logs? We do need it as we need to check for errors and identify if your system is in optimal configuration. Kindly please let me know if you would like to consider this option. Thank you

Regarding your inquiry on booting into safe mode in windows 11, you may use this link from Microsoft. Based on the log as well, you are using the Microsoft Basic Display Adapter, did you recently clean install your driver? Please send us a screenshot of your display settings as well as the model of your monitor so we can check other possible options. I will be waiting for your reply.

I hope everything is well in your system. As we have not heard a response from you in the past days, we will proceed in closing this case. Should you need further assistance, feel free to create a new post and we will be there to assist you.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

I upgraded my kernel5.19 >> 6.0.2 and nvidia drivernvidia-open 520.56.06-3 yesterday and since then my computer is unusable. Rebooting after the upgrade, system crashes around 10 secs after reaching graphical user interface. After the system crash the computer REFUSES to boot at all ! After force rebooting, I can't even get into the BIOS, and the VGA debug LED stays lit on my motherboard. Turning off power and coming back later to boot it works, but same error occours, again. Even the TTY is laggy after this update !

Here the logs for the gpu :

Can Some one please help me figure this out ? I don't think that my GPU or My Motherboard are malfunctioning, because I can properly boot into manjaro live iso with GUI working. I've also tried the standard nvidia driver and the same error occurs.

Okay ! I installed the lts kernel and nvidia driver, and updated the systemd-boot entry, this time the GUI did not crash but the inconsistent boot behaviour remained, sometimes when I reboot from the gui normally, the computer gets stuck with the vga led on, I have to cut power to boot it again.

Sometimes I can only boot into my system by first entering the bios, then selecting "exit without saving", which then triggers the arch boot process.

As of now I have cleared the cmos battery and it seems to work fine. Hopefully this will be fixed soon.

Do you have a complete system journal for such boot?

Are there any error messages on screen while rebooting?

Does this also happen if you only boot the multi-user.target (2nd link below) and/or w/ "nomodeset" (the parameter will effectively prevent any GUI session, but your GUI target might be stubborn and crash to eternity, so pair it w/ the mutli-user.target) and "systemctl reboot" from there?

Update: System is running normally after replacing the latest linux kernel and driver with linux-lts and nvidia-lts.

One thing that I do want to note is that using the nvidia-dkms or nvidia-open-dkms seems to work just fine with the latest 6.0 linux kernel, probably because the dkms is designed to adapt to your kernel, so for now I have upgraded to linux 6.0 with the nvidia-dkms driver and it seem to be working just fine. I'm planning to move to amd gpu in the long run. Marking this issue as solved !

TLDR: Just use nvidia-dkms or nvidia-open-dkms if you're facing issues with the current nvidia driver. Or as a last resort you can use the linux-lts and nvidia-lts/nvidia-open-lts variants until the issue is fixed. Or just use an AMD gpu instead

I've been experiencing frequent BSODs in the past few months occurring at random times. I tried updating my drivers, doing a memtest SFC & CHKDSK scans which did not fix the problem or showed things were normal and there were no file corruptions.

7)Open administrative command prompt and type or copy and paste:chkdsk /b /vRun these chkdsk switches on all disk drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b/ v E:, etc.These chkdsk switches can take significant time to run so plan to run the switches on the Windows drive overnight while sleeping.C:\WINDOWS\system32>chkdsk /b /vThe type of the file system is NTFS.Cannot lock current drive.Chkdsk cannot run because the volume is in use by anotherprocess. Would you like to schedule this volume to bechecked the next time the system restarts? (Y/N)Type: YReboot as needed.%%%%%%%%%%

9)Run Memtest86 (free version) for two tests of four passes each (total eight passes) one error is a test fail and testing can be aborted.Take pictures > post images or share links into this thread using one drive, drop box, or google driveMemtest86 has a feature to create text / html reports.If possible, include the reports with the images in the share links.%%%%%%%%%%

When the above post was created it was spaced with multiple spaces between each steps.When post your answer was clicked the website rearranged the post to where it was no longer readable.I'd spent a lot of time creating the post.I'm sorry that it was not easy to read.A thread was opened in another thread to ask for website help.

You can scan for driver updates automatically and install them manually with the free version of the Seagate Hard Disk Drive Driver Update Utility, or complete all necessary driver updates automatically using the premium version.

Click the Update button next to your driver. The correct version will be downloaded and installed automatically. Or, you can click the Update All button at the bottom to automatically download and install the correct version of all the drivers that are missing or out-of-date on your system.

To find the latest driver, including Windows 11 drivers, choose from our list of most popular Seagate Hard Disk Drive downloads or search our driver archive for the driver that fits your specific Seagate hard disk drive model and your PC's operating system.

After downloading your driver update, you will need to install it. Driver updates come in a variety of file formats with different file extensions. For example, you may have downloaded an EXE, INF, ZIP, or SYS file. Each file type has a slightly different installation procedure to follow. Visit our Driver Support Page to watch helpful step-by-step videos on how to install drivers based on their file extension.

I'm running Zoom on Linux (Ubuntu 20.04.4 LTS) on an older Dell-XPS-L322X machine. When I try to use the Mic test, I can SEE that the volume indicator in the Test Window indicating the rise and fall of the sound. However, i never HEAR the playback of my "testing 1-2-3" although if I continue on and connect with another user, sound and video both work.

I suspect this is either a programming error in Zoom or the Ubuntu audio driver, but I can't solve in nor have I found others with same problem. (Yes, I've removed and reinstalled both the OS and Zoom.)

I just happen to have that drive and a PC which is in the middle of repair. I placed the drive inside, connected the cables, and powered it on. BIOS (this is an Intel board) saw the drive, with the SATA type set at AHCI from before. I exited BIOS and was prompted to install an OS. So there is nothing wrong with that type of drive per se. This drive was connected to a SATA 6 Gbit/s port. My drive has no jumper.

Can you boot to something other than the hard drive, like a CD/DVD or Flash stick to try and install Windows? This way you can see if the drive is recognized by the Windows installation or if it needs a set of drivers from the computer/motherboard manufacturer.