bios intel dg41tx

[EdwuarS]

Buenas tardes a toda la comunidad, ¿alguien tiene la BIOS de una placa base Intel DG41TX? Estoy en un proyecto escolar con una de ellas y necesito instalar un Q8300, pero como la BIOS predeterminada no es compatible con el procesador, la placa base Trade estaría muy agradecida si alguien pudiera enviármela. Gracias de antemano.

[AlHill]

Attached:

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[EdwuarS]

It doesn't work, it doesn't update the bios -.-

[AlHill]

What do you mean "it doesn't work"?

Be specfic.  It is the proper bios file for your board.  How are you attempting to update the bios?  Does the board even power on?  Can you get to the bios settings via F2?  Did you use F7 to load the .bio file?  Did you put the .bio file on a usb 2.0 stick and use one of the black usb ports on the rear of the board?

Lots of questions you need to answer.

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[EdwuarS]

Yes, I just did this whole procedure, I put it inside the USB memory with FAT32 format, it restarted in 9 seconds, but the BIOS remained the same.

[AlHill]

Again, answer each of my questions.  I still have no idea what you are doing.  Do you, by inserting the usb stick, expect the bios to simply update?

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[EdwuarS]

ok ok, the motherboard does turn on, yes yes I can enter the bios, the procedure I follow to update the bios is the following: first copy the .bio file to the usb with fat32 format, second I enter the BIOS Flash Update with F7 and select the usb, third I select the .BIO file, after selecting the file it tells me that it will restart in 9 seconds, but nothing happens apart from that.

[AlHill]

Have you tried bios recovery by removing the jumper?

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[EdwuarS]

Thanks for the help friend, it worked by removing the jumper, by F7 as I was trying if it didn't work at all, Thanks and Happy Day.

[AlHill]

@EdwuarS   I am confused.  In one post you say it worked perfectly with the jumper in, and the other post you say it worked by removing the jumper.

Whatever the case, glad you (somehow) got it working.

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[EdwuarS]

My mistake for saying it wrong, it worked by removing the jumper

[n_scott_pearson]

What's happening is that the BIOS is 'forgetting' the update. This is usually caused by the BIOS, after the reboot, having problems completing POST. The most common cause is a failure during memory initialization. If, for example, the BIOS is unable to complete memory initialization, it will hard reset the system and then come back and try using its default memory settings. It is this hard reset that causes the BIOS to 'forget' that it was doing a BIOS Update.

What I suggest you do first is try installing the BIOS Update using the jumper-based BIOS Recovery process. If that doesn't work, try checking whether the issue is with the memory.

To perform a BIOS Recovery, power off the system, insert the flash drive into a USB port on the rear panel of the motherboard, remove the (yellow) BIOS jumper from the board, and then power on the system. It should automatically start the BIOS Recovery process, in this case also upgrading the BIOS. A display of its progress will be produced just like with a regular BIOS update. When it is done (or fails), it will ask you to power off and then restore the BIOS jumper to pins 1-2. If it failed, power off but leave the jumper off the board.

If BIOS Recovery failed, you need to test for a failing DIMM. Power off. Remove one DIMM. Power on and see whether the system will do the BIOS Recovery. If it succeeds, then the DIMM that you removed should be considered suspect. To be absolutely sure, however, you should repeat the process with the other DIMM (i.e., reinstall the DIMM you removed earlier, remove the other DIMM, and then power on). If this succeeds, then the DIMM you currently have removed is bad and should be replaced. If this also fails, however, it points to some other problem with the motherboard or processor (and not the DIMMs).

Hope this helps, it's a rather dense post,

...S

[EdwuarS]

With the jumper, it worked perfectly. Thank you very much for the help. I thought it would be easy, but no... it was annoying.

[n_scott_pearson]

Annoying? You are talking about a board from 2008, almost 18 years ago, so you should have expected issues like this. For *any* motherboard manufacturer's products back then - bringing the BIOS up-to-date in cases where you're skipping many interim updates and levels of technology and security advancement, is *always* going to involve some level of complexity.

Glad to see you got this going, but seriously, the whining only reflects badly on you.

Good day,

...S

[n_scott_pearson]

I'd also like to add a (long-winded) suggestion.

When using the jumper-based BIOS Recovery process, a default set of memory initialization parameters are utilized. When using the F7 method, however, the configured set of parameters (typically XMP settings) are utilized. The fact that you saw the issue when attempting to use the F7 method, but not when using the jumper-based BIOS Recovery method, points to there being an issue with memory initialization. Issues with memory initialization like this points to there being an issue with the configuration parameters - or worse, failing memory. Now, when I say failing memory, I don't necessarily mean that the memory itself is failing. Let's analyze the issues with aging systems.

Every component used in a system - capacitors, resistors, ICs, etc. - generates some amount of electrical noise. As these components age, they all produce even more electrical noise. The motherboard's design includes components to fight the affects of electrical noise on the Memory Bus signals used to transfer data to and from memory. These bus components can only do so much, however. As the system ages and its components generate more noise, a point can be reached where the memory controllers in the processor and on memory cards cannot distinguish valid data signaling from this noise. The operations that fail are retried, but a point is reached where the controllers give up and the Memory Bus(es) hang.

As I mentioned, during memory initialization, the BIOS watches for Memory Bus hangs and, if one should occur, the BIOS initiates a system reset and, when it next attempts memory initialization, it utilizes lower (default) settings. Now, what you have seen with F7 failing and Recovery succeeding is telling me that there is a problem with the configured memory initialization parameters (i.e., they have become unattainable) or that there is a pending problem with the memory itself. I suggest that you change the configuration to utilize only the lowest settings offered (likely disabling XMP). If you then see any memory issues, you will know that the time has been reached where you either attempt memory replacement or just plain retire the system.

Hope this helps,

...S