[SOLVED] H510M S2H, new CPU & Ram - various problems

Mar 5, 2022
3
1
15
Hi all, I am in need of help after hitting various problems with a PC I am trying to put together. I am using:
- Gigabyte H510M S2H motherboard
- i3 10100 CPU
- Kingston Fury Beast ram. 2 x 8GB dimms.
All bought new last week.

Probs are:
  1. Single beep on startup. Using either or both dimms makes no difference. Surely there can't be a problem with both??
  2. CPU should support on board graphics but although BIOS shows up OK using VGA or DIV-X port, anything after exiting BIOS just produces a black screen with what appears to be a non blinking cursor on the left of the screen, about 4 rows from the top.
Whether "internal Graphics" setting in BIOS is set to auto or enabled makes no difference.
If I put in my old graphics card, that seems to work fine.
CPU clearly shows up in BIOS as model 10100 - no F suffix.
3. If I try to load Windows 7 from CD, it gets to "starting Windows" then gives the BSOD with an error stating that the BIOS in this system is not fully ACPI compliant.
If I try a Windows Repair disc - same problem. If I try to boot off old hdd I get same BSOD & same message.

Have tried new PSU & DVD drive but makes no difference.

Have tried setting BIOS to factory defaults & to optimised settings - no difference.
Have enabled CSM & tried both UEFI & Legacy settings.
BIOS shows everything to be as I would expect.

Is this a defective mbd thinking it has a DRAM issue??? Or is there a simple BIOS setting that will make all these problems go away?

Help would be much appreciated!
 
Solution
Quick update - problems now solved.
Supplier thought memory could be too fast - 3200MHz. Changed to 2333Hz but made no difference to problems.
Changed to an MSI mobo & it was all good after that.
Not sure, but think the graphics problem might have been down to me not understanding that UEFI only worked properly with the on chip graphics while legacy only worked with old graphics card.

BTW, with mew mobo was able to load Win7 with no BSOD, but once loaded couldn't use it because it didn't see the USB or network ports & the mobo's drivers weren't compatible with Win7 - so got a copy of Win 10 & went with that.
Quick update - problems now solved.
Supplier thought memory could be too fast - 3200MHz. Changed to 2333Hz but made no difference to problems.
Changed to an MSI mobo & it was all good after that.
Not sure, but think the graphics problem might have been down to me not understanding that UEFI only worked properly with the on chip graphics while legacy only worked with old graphics card.

BTW, with mew mobo was able to load Win7 with no BSOD, but once loaded couldn't use it because it didn't see the USB or network ports & the mobo's drivers weren't compatible with Win7 - so got a copy of Win 10 & went with that.
 
Last edited:
  • Like
Reactions: egda23
Solution

TRENDING THREADS