• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Need help with Dell 7520 SE

FilhoSenhor

FilhoSenhor

New Member
Joined
Sep 21, 2024
Messages
29 (0.12/day)
Location
Brasil
I was researching software to flash both BIOSes of my Dell 7520 SE which has AMD ATI Radeon HD 7730M integrated with Intel Graphics HD 4000. The motherboard had never come across such robust and complex hardware as this notebook and although it is still alive, the 7730M seems to have corrupted the BIOS or was mistakenly changed by the previous owner,
kbw.png
hx4.png
h5m.png

with no history of what really happened and I am faced with problems in the hardware preventing me from running its maximum performance and even continuing to update the system. I have been trying for several days to understand how it works and some means of repair by software or commands, seen and even in Linux it does not recognize it as a graphics accelerator but rather ASIC R600 being R576 in the INF section I believe it has been modified for other more profitable purposes than games, without knowing I am looking to undo it simply to move forward with updating its OS, I realize now that I may have a portable miner and wanting to go back to the graphics, but the reason for writing to you here is that in all this searching I found something that might help in something which is the original download of the Insydeflash BIOS AMD Developer Center on the website of one of its partners Insyde Software which seems to work for both in my search now remains to find the said original BIOS of the 7730M because even without some parameters in GPU-Z it seems to work for a certain purpose still unknown to me. And I will also take a look at the links that I found indicated here and I hope that I can also resolve your doubts and uncertainties you are on the right track do not be afraid just be prudent in reading everything well! Thank you for sharing your experience helped a lot!
 

Attachments

Last edited:
I could be wrong but Insyde is used for motherboard bios and not the graphics card bios.

Do you see an error with device manager for the 7730M? If the device is installed without an error code like 43 you can assume GPU-Z is unable to detect the card properly.
 
VuurVOS said:
I could be wrong but Insyde is used for motherboard bios and not the graphics card bios.

Do you see an error with device manager for the 7730M? If the device is installed without an error code like 43 you can assume GPU-Z is unable to detect the card properly.
Click to expand...
That's right, Insyde is the one who manages the BIOSes of several motherboard manufacturers, but it also has a partnership with AMD, which makes you mistaken, not wrong. If you click on the link, you will verify this correctly


error43.png

Error 43 is present, can you guide me on what to do to resolve it? Thank you for your attention to my search, sir! Yes.
 
Last edited by a moderator:
FilhoSenhor said:
That's right, Insyde is the one who manages the BIOSes of several motherboard manufacturers, but it also has a partnership with AMD, which makes you mistaken, not wrong. If you click on the link, you will verify this correctly


View attachment 364453
Error 43 is present, can you guide me on what to do to resolve it? Thank you for your attention to my search, sir! Yes.
Click to expand...
Can you dump the bios with GPU-Z and share it with us?
 
FilhoSenhor said:
I was researching software to flash both BIOSes of my Dell 7520 SE which has AMD ATI Radeon HD 7730M integrated with Intel Graphics HD 4000. The motherboard had never come across such robust and complex hardware as this notebook and although it is still alive, the 7730M seems to have corrupted the BIOS or was mistakenly changed by the previous owner,
kbw.png
hx4.png
h5m.png

with no history of what really happened and I am faced with problems in the hardware preventing me from running its maximum performance and even continuing to update the system. I have been trying for several days to understand how it works and some means of repair by software or commands, seen and even in Linux it does not recognize it as a graphics accelerator but rather ASIC R600 being R576 in the INF section I believe it has been modified for other more profitable purposes than games, without knowing I am looking to undo it simply to move forward with updating its OS, I realize now that I may have a portable miner and wanting to go back to the graphics, but the reason for writing to you here is that in all this searching I found something that might help in something which is the original download of the Insydeflash BIOS AMD Developer Center on the website of one of its partners Insyde Software which seems to work for both in my search now remains to find the said original BIOS of the 7730M because even without some parameters in GPU-Z it seems to work for a certain purpose still unknown to me. And I will also take a look at the links that I found indicated here and I hope that I can also resolve your doubts and uncertainties you are on the right track do not be afraid just be prudent in reading everything well! Thank you for sharing your experience helped a lot!
Click to expand...
Please get hwinfo64 and lets see what motherboard is in this thing please
 
Low quality post by eidairaman1
Guess he bailed
 
Last edited by a moderator:
eidairaman1 said:
Please get hwinfo64 and lets see what motherboard is in this thing please
Click to expand...
Oh yes, it helped in MB and this is: DELL 0DNMM8. But what a well done little program brother, I enjoyed reading everything up until EC, I also got an update on the website which I believe had some effect on this.
HWiNFO.png
HWiNFO1.png
 
Last edited:
FilhoSenhor said:
I'm not saying that it doesn't work for me, HWiNfO read it, but not even AMD flashwin reads it:

View attachment 366294
Click to expand...
It is soldered on the motherboard and not an MXM card:

Try to downgrade/upgrade the motherboard bios since that will likely contain a part for the vga. If that doesnt work, it is broken.
 
VuurVOS said:
It is soldered on the motherboard and not an MXM card:

Try to downgrade/upgrade the motherboard bios since that will likely contain a part for the vga. If that doesnt work, it is broken.
Click to expand...
But how can it be broken if it is detected by Windows and HWiNFO? even error 43 disappears when deactivating and activating it again in the device manager, it runs games and everything else, what I think is that either they forced it to work as an ASIC and stopped reading it or it really is some protection that was activated at some point, everything I see Seeing it leads me to believe that the problem is software, not hardware!
 
FilhoSenhor said:
But how can it be broken if it is detected by Windows and HWiNFO? even error 43 disappears when deactivating and activating it again in the device manager, it runs games and everything else, what I think is that either they forced it to work as an ASIC and stopped reading it or it really is some protection that was activated at some point, everything I see Seeing it leads me to believe that the problem is software, not hardware!
Click to expand...
Software reading is no guarantee it is correct. Also error 43 often points to a hardware failure.
 
FilhoSenhor said:
But how can it be broken if it is detected by Windows and HWiNFO? even error 43 disappears when deactivating and activating it again in the device manager, it runs games and everything else, what I think is that either they forced it to work as an ASIC and stopped reading it or it really is some protection that was activated at some point, everything I see Seeing it leads me to believe that the problem is software, not hardware!
Click to expand...
Put Win 7 on it
 
Hello,

Have you installed the original Dell drivers for the unit? I've found with the Inspiron 7520 SE in particular (tested across 3 or 4 different units) that they don't take very kindly to the Windows Update inbox drivers, and commonly have BSODs. This may be causing your Code 43's here. If it doesn't work with the Dell drivers though I'd consider it a faulty GPU. But please give those a shot first. I hope that this helps!
 
VuurVOS said:
Software reading is no guarantee it is correct. Also error 43 often points to a hardware failure.
Click to expand...
I understand, even so I believe it is a problem related to the motherboard's BIOS which is not allowing reading for some reason or configuration, as there is no battery it is preventing the update naturally, I am looking for forced ways since I got the .fd file from BIOS or almost buying another card, but there is no guarantee that it will work or solve it, the strangest thing is that the atiflash says that it is not a VBIOS on the adapter but a SIF which makes me think that it was changed in some way, I tested some versions of GPU-Z that still did some more reading than the current version but without success in extracting the BIOS, I have it in text extracted by CPU-z, is there any use? Grateful!

sps063info.gifsps063sensor.gifsps078info.gifsps078sensor.gifsps260info.gifsps260sensor.gif
eidairaman1 said:
Put Win 7 on it
Click to expand...
The original system on it is Windows 8, Win7 was the first one I installed and it doesn't allow updating the BIOS with the manufacturer's file, which only works on Wim8 and doesn't work on Win10! Can you be more specific in your help?
 

Attachments

racecar56 said:
Hello,

Have you installed the original Dell drivers for the unit? I've found with the Inspiron 7520 SE in particular (tested across 3 or 4 different units) that they don't take very kindly to the Windows Update inbox drivers, and commonly have BSODs. This may be causing your Code 43's here. If it doesn't work with the Dell drivers though I'd consider it a faulty GPU. But please give those a shot first. I hope that this helps!
Click to expand...
I understand, I first installed the original ones, then I updated them to the ones from the update, but even with the originals, 43 was there or 28 if I'm not mistaken, there was a moment when the code was different, I remember, but, your contribution is quite valid! I will do a new formatting soon, with more attention to this!
Thank you for participating!
 
FilhoSenhor said:
I understand, I first installed the original ones, then I updated them to the ones from the update, but even with the originals, 43 was there or 28 if I'm not mistaken, there was a moment when the code was different, I remember, but, your contribution is quite valid! I will do a new formatting soon, with more attention to this!
Thank you for participating!
Click to expand...
Got it. I'd say if you do a format of the hard drive, install original Dell display drivers for both the Intel & AMD cards, and still have issues, I'd strongly suspect the GPU is failing. A BIOS flash certainly is a good idea before we diagnose the board as failed though, so I'd try the above BIOS force flashing instructions that VuurVOS provided, and outside of that, I'd just figure the thing's probably bust unfortunately.

EDIT: Concerning the error shown - double-check that you got a good download of the file. A corrupted download will cause that.
 
racecar56 said:
Got it. I'd say if you do a format of the hard drive, install original Dell display drivers for both the Intel & AMD cards, and still have issues, I'd strongly suspect the GPU is failing. A BIOS flash certainly is a good idea before we diagnose the board as failed though, so I'd try the above BIOS force flashing instructions that VuurVOS provided, and outside of that, I'd just figure the thing's probably bust unfortunately.

EDIT: Concerning the error shown - double-check that you got a good download of the file. A corrupted download will cause that.
Click to expand...
That's right, even without being able to flash the BIOS, I can't declare that it's the faulty board, the problem is a block in the fw, I don't believe I'll be able to solve this because what's causing this is well hidden, possibly in the UEFI, but I don't have it. How do I know if it really is without changing all my work material and whatever it is, it came with the media, the worst part is that my knowledge is little about many things and a large part of it is due to observation and testing, but I will continue to look for an alternative way because The OS manufacturer or administrator has no interest in it working, I will probably be forced to compile everything from the BIOS to the OS in open source to solve this. I don't even know where to start nowadays.
 
FilhoSenhor said:
That's right, even without being able to flash the BIOS, I can't declare that it's the faulty board, the problem is a block in the fw, I don't believe I'll be able to solve this because what's causing this is well hidden, possibly in the UEFI, but I don't have it. How do I know if it really is without changing all my work material and whatever it is, it came with the media, the worst part is that my knowledge is little about many things and a large part of it is due to observation and testing, but I will continue to look for an alternative way because The OS manufacturer or administrator has no interest in it working, I will probably be forced to compile everything from the BIOS to the OS in open source to solve this. I don't even know where to start nowadays.
Click to expand...
Did you try to force a flash from a fresh Windows installation with the bios file located in c:\ instead of c:\windows\system32?
 
https://winraid.level1techs.com/t/tool-h20eze-insyde-easy-bios-editor/33332/7
I found this information from Insyde's .fd editor but still studying everything! If anyone understands the subject well and wants to help, I would be grateful, I want to get to the root of the problem and clear up any doubts.

VuurVOS said:
Did you try to force a flash from a fresh Windows installation with the bios file located in c:\ instead of c:\windows\system32?
Click to expand...
Extract extracts it without the forceit command, but it does not install even with /nopause /forceit and /forcetype, Also note that even the installer doesn't read the BIOS very strangely, which reinforces my theory that there is some lock preventing it.


noit.png
 
Last edited:
You must log in or register to reply here.
Back
Top