Resolved BIOS Utility on Startup

Recently I added more memory to my computer. When I restarted the machine the BIOS appeared and confirmed that the memory was recognised (see attachment). I then pressed F1 to continue and it booted into Windows. No problem.

However, every time I've started the computer since then the same BIOS screen appears and I have to press F1 to boot into Windows again. Is there something I need to do stop this BIOS screen appearing at startup every time? Thanks.

 

Well, I'm not sure, but is there some kind of cover switch that could be triggering this event?

Maybe some of the others can be of more help here.

 

Apart from the BIOS screen appearing every time at startup everything else works perfectly. The system does have a security feature which warns when the cover has been removed. It's securely back in place now.

 

Thanks for helping out, Pete.

I've never had to deal with a chassis intrusion warning before, so this is valuable information for me in case the need arises.

 

Thanks, Pete. I did actually try Google first, but obviously didn't choose the best words in the search. I also used the 'search' option in these forums. I'll follow the instructions you've given and report back tomorrow.

Many thanks.

 

All you may need to do is to go into the BIOS, save your changes (the memory upgrade) and exit.

 

That's what I did, Spyware, but the BIOS page continued to appear on boot-up.

 

I'm happy to report that the following (thanks to Pete) worked:

Restart the system. As soon as the first logo screen appears, immediately press the F2 key, or the DEL key if you have a desktop, to enter the BIOS.

Press the RIGHT ARROW key until BIOS Security Features or Integrated Peripherals is selected, and choose one of the following options.

If you have selected the BIOS Security Features tab:
Use the DOWN ARROW key to navigate to Chassis Opened Warning and press the ENTER key.

Use the RIGHT or the LEFT ARROW key to select Disabled and press ENTER.

Press the F10 key to save changes and restart the system.

All is well now. Thank you everyone for your input.

 

Good to hear Pete's suggestion resolved the problem for you. Thanks for letting us know.