Overclock.net › Forums › Intel › Intel Motherboards › Intel BIOS › BIOS issue help. Possible CMOS not clearing?
New Posts  All Forums:Forum Nav:

BIOS issue help. Possible CMOS not clearing?

post #1 of 5
Thread Starter 
Hey folks,

I've recently installed a new SSD and fresh installed Win 10 Pro in a computer that has seen many components and operating systems over the years. I'm getting occasional blue screens indicating that the computer can't access the drive -- "a required device cannot be accessed" or "critical system error."

Working theory: Occasionally, while running through various BIOS boot options I get an error message that mentions an Ubuntu file that cannot be found. I haven't had Ubuntu on this computer for years (several hard drives ago - when it dual-booted Ubuntu and Vista). Is it possible that my CMOS is not clearing fully when I fully unplug, remove battery, and hold power button for many minutes? On reboot it makes me press F1 to restore BIOS settings.

I have now tried this with multiple drives -- same problem (but only after about a week of usage). I feel like the problem has to be either CMOS related or perhaps something with the SATA port itself (At first this problem happened on my SATA 6G, but it is now happening on the 3G too.)

I've also tried reflashing BIOS, restoring default BIOS settings, etc ... no luck. Sometimes after a battery removal reset it works for a while -- then the problem comes back. Almost like there is a choice that gets reset when I refresh the settings but then changes back on me to cause the problem.

Any ideas? Thanks in advance.

Specs:
Windows 10 Pro 64bit (previously ran Win8, Vista, Ubuntu)
Crucial MX200 1tb
ASUS P8H77-M LE LGA 1155 Intel H77
Intel i3 3225
AMD HD 6950 2gb

Probably not relevant but just in case: I had an older crucial SSD that worked fine to start. I upgraded to a SanDisk. Problems started. Returned the SanDisk (assuming it was the problem) and got another Crucial. Problem reemerged after about 2 weeks of use.
post #2 of 5
Quote:
Originally Posted by deadlockedworld View Post

Occasionally, while running through various BIOS boot options I get an error message that mentions an Ubuntu file that cannot be found. I haven't had Ubuntu on this computer for years

Any ideas? Thanks in advance.

Specs:
Windows 10 Pro 64bit (previously ran Win8, Vista, Ubuntu)
got another Crucial. Problem reemerged after about 2 weeks of use.

I assume all the drives you are using now have been reformatted for this build. There are no drives present that may have had other OS's or programs on them and have not been reformatted?

When you dual booted Ubuntu you used a non windows boot loader. That boot loader modified the boot sector of whatever drive was the boot drive when it was installed. If you later do a windows install thge installer can't see what the previous (noin windows boot loader did to the boot sector and windows install goes on it's merry way. So, you have two programs, neither of which knows what the other is doing (or did) to the boot sector. That's why I asked the above.

.
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
post #3 of 5
Thread Starter 
Thanks so much for the reply! This is really helpful.

I have all other drives disconnected for the new build ... except one. Its a storage drive that has not been used as a boot drive -- but now that you say this, I wonder if I naively tried to install a different OS on each drive years ago, then deleted all the files from the drive and forgot.

Would this conflict also cause blue screens during operation (not just during startup)? The crashes have been inconsistent -- sometimes they have happened during a game, although they are mostly at startup. It seems weird to me that each time I would manage to get entirely through the many restarts of the windows installation, only to have the conflict happen later after the install and all the programs are working.

If this is the problem, do I need to do anything to my current boot drive, or can I just extract files and reformat the potential problem drive?

Thanks again!
post #4 of 5
Well, the other thing I thought about was a virus,

And, no, I don't think there's a "conflict".

Perhaps there's something "weird" starting up with Windows????

Try this:

In the 'Run' Box type wbemtest.
You will get a box. Click on connect.
There will be root/default......
change this to root/cimv2
hit the 'Enter' key on your keyboard.
The box that comes up will have a bunch of buttons.....
click on Enum Classes
Select recursive (below) and click OK
You will get a large listing of items....
go down that list to Win32_StartupCommand
double click it.
Then click on the Instances button to the right.

The listing you get shows what is starting when you start your system.
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
post #5 of 5
Thread Starter 
Thanks everyone. This was very helpful.

Just to close the loop on this -- it must have been the drive. I did a new download of windows, disconnected the nonessential drive, reset the CMOS again, disabled the compatibility support module on the new drive (running in full UEFI mode) and reinstalled everything. Its working great. I'm not going to plug the old drive back in during startup.

This makes me realize that I need to disable CSM in all of my boot drives. Its much faster now.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel BIOS
Overclock.net › Forums › Intel › Intel Motherboards › Intel BIOS › BIOS issue help. Possible CMOS not clearing?