Overclock.net banner
12,701 - 12,720 of 13,002 Posts
@shabann - Where did you read Q45 only support X3 Xeon? I believe you, only wanted to read about it myself to see details about why if it says. I assumed some E Xeon support too

Here is updated BIOS for you, with 2015 microcode for the CPU you mentioned CPUID 10676 - http://www.cpu-world.com/CPUs/Xeon/Intel-Xeon X3323 - EU80584KJ060J - AT80584KJ060J.html
Image


Run winphlash, backup your original BIOS, then flash new modified BIOS ($image5C.usf) included
Hey, thanks again for the modded BIOS, but I can't install it for some reason. The original latest BIOS gets installed without any problems, but when I try to install this modded BIOS I get BSOD with error code 0x0000007f . I tried modding the original BIOS but honestly I don't know how to do it. Can you help me again?

Thanks
 
BSOD error code 0x7f means your SATA settings are not the same as you set previously. You did mean BIOS flash was fine, but once you tried to load windows you get the BSOD correct? If yes, then this is the issue.
Load optimal or optimized defaults, then set either AHCI or IDE, whichever you used before. If IDE, you want AHCI really, let me know if it ends up being IDE and I can help you edit registry in windows to allow any setting to boot.

Actually, here is what you edit in windows, then you can use any of the SATA settings (but AHCI is the optimal setting)

Enable switching between all IDE/AHCI/RAID modes by changing "Start" Values in these keys to 0 - this is in the registry, change with regedit.
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci\Start
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Pciide\Start  
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV\Start
 
BSOD error code 0x7f means your SATA settings are not the same as you set previously. You did mean BIOS flash was fine, but once you tried to load windows you get the BSOD correct? If yes, then this is the issue.
Load optimal or optimized defaults, then set either AHCI or IDE, whichever you used before. If IDE, you want AHCI really, let me know if it ends up being IDE and I can help you edit registry in windows to allow any setting to boot.

Actually, here is what you edit in windows, then you can use any of the SATA settings (but AHCI is the optimal setting)

Enable switching between all IDE/AHCI/RAID modes by changing "Start" Values in these keys to 0 - this is in the registry, change with regedit.
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci\Start
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Pciide\Start  
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV\Start
But the original BIOS file gets flashed successfully. I get BSOD when BIOS finished backing up and it freezes before "Flashing BIOS" in WinPhlash then shuts down and shows this error. This only happens in Win 7 32 bit, cuz for some reason WinPhlash doesn't want to work in Win 10 64 bit or Win 7 64 bit, it shows different errors. I use 2 harddisks, one has Windows 7 64 bit and the other has Windows 10 64 bit, but I got another harddisk only to install Win7 32bit so I could use WinPhlash. I get same erros (but different errors with different WinPhlash versions) in 64bits and I get BSOD on Win7 32bit. Should I do those changes in registry or should I try to install Win 7 32bit with only one harddisk plugged?

Thanks for your help once again
 
Sounds like a winphlash problem, but it may be due to the edited file? In the original unedited flash, does it reboot to flash the BIOS or reboot after flashing BIOS?

And yes, maybe for less possible issues, try with only one disk and win7 installed. That way you rule out win10, and or dual boot setups as any part of the cause.

Do you have bitlocker enabled? Can you send me the log after one of these attempts? I mean the PHLASH.LOG.
Please delete the current one, try flash again and send me that log, that way it's only one clean logged attempt.

This BIOS contained two BIOS images, maybe I only sent wrong one back to you? Only try one more flash attempt, with the stock winplash and the above registry change (And then two below settings changes)
Then if still error, please wait until I can check some things before trying again.

Since I couldn't run winplash, what options do you see as part of the flashing choices before you hit flash, and can you edit/uncheck any?
If you can uncheck, please uncheck VCPU or anything that says - Install processor patches, and uncheck Clear CMOS (Unless you've already done the above registry edit and rebooted previously)
 
Sounds like a winphlash problem, but it may be due to the edited file? In the original unedited flash, does it reboot to flash the BIOS or reboot after flashing BIOS?

And yes, maybe for less possible issues, try with only one disk and win7 installed. That way you rule out win10, and or dual boot setups as any part of the cause.

Do you have bitlocker enabled? Can you send me the log after one of these attempts? I mean the PHLASH.LOG.
Please delete the current one, try flash again and send me that log, that way it's only one clean logged attempt.

This BIOS contained two BIOS images, maybe I only sent wrong one back to you? Only try one more flash attempt, with the stock winplash and the above registry change (And then two below settings changes)
Then if still error, please wait until I can check some things before trying again.

Since I couldn't run winplash, what options do you see as part of the flashing choices before you hit flash, and can you edit/uncheck any?
If you can uncheck, please uncheck VCPU or anything that says - Install processor patches, and uncheck Clear CMOS (Unless you've already done the above registry edit and rebooted previously)
OK, I tried with only one harddisk plugged and Windows 7 32bit installed. I'm not sure about BitLocker, but the original flash file gets installed successfully in WinPhlash (all bars fill up) and then after "Flashing BIOS" gets a tick, the PC reboots and the BIOS gets flashed successfully. I'll upload the log file in a bit, but I have a request for you. Can you take the original BIOS file and replace a single (not needed) CPU microcode with the X3323 microcode, because I read somewhere that the microcodes should be replaced, not added (maybe it's wrong). I reset the BIOS settings to default and tried again, but same error. As I said I'll upload the log file but first I'll try with the registry edits. Thanks again!
 
PHLASH.LOG :
--- Log started: 08/12/18 10:30:58
Initializing...
Log file : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\PHLASH.LOG
Settings file : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\PHLASH.INI (found)
Executable : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\winphlash.exe
Version : 1.6.9.7 Build : WinPhlash
Date : 8/12/2018
Resource file : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\PHLASHLC.DLL (loaded)
Help file : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\WINPHLASH.HLP
App name : Phoenix WinPhlash
OS Information : Windows NT 6.1.7600 - supported
isNT_AUTHORITY_SYSTEM_account: MobiPhone. => False.
gVBL_Flag = False(0h).

[08/12/18 10:31:05]
Preparation stage

Processing parameters...
Image file : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\$image5C.usf
Backup file : C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\bios.bak

Loading new BIOS image file...
Opening file C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\$image5C.usf...
Allocating 1579174 bytes...
Reading 32768 bytes from the file starting at 0...
Reading 32768 bytes from the file starting at 32768...
Reading 32768 bytes from the file starting at 65536...
Reading 32768 bytes from the file starting at 98304...
Reading 32768 bytes from the file starting at 131072...
Reading 32768 bytes from the file starting at 163840...
Reading 32768 bytes from the file starting at 196608...
Reading 32768 bytes from the file starting at 229376...
Reading 32768 bytes from the file starting at 262144...
Reading 32768 bytes from the file starting at 294912...
Reading 32768 bytes from the file starting at 327680...
Reading 32768 bytes from the file starting at 360448...
Reading 32768 bytes from the file starting at 393216...
Reading 32768 bytes from the file starting at 425984...
Reading 32768 bytes from the file starting at 458752...
Reading 32768 bytes from the file starting at 491520...
Reading 32768 bytes from the file starting at 524288...
Reading 32768 bytes from the file starting at 557056...
Reading 32768 bytes from the file starting at 589824...
Reading 32768 bytes from the file starting at 622592...
Reading 32768 bytes from the file starting at 655360...
Reading 32768 bytes from the file starting at 688128...
Reading 32768 bytes from the file starting at 720896...
Reading 32768 bytes from the file starting at 753664...
Reading 32768 bytes from the file starting at 786432...
Reading 32768 bytes from the file starting at 819200...
Reading 32768 bytes from the file starting at 851968...
Reading 32768 bytes from the file starting at 884736...
Reading 32768 bytes from the file starting at 917504...
Reading 32768 bytes from the file starting at 950272...
Reading 32768 bytes from the file starting at 983040...
Reading 32768 bytes from the file starting at 1015808...
Reading 32768 bytes from the file starting at 1048576...
Reading 32768 bytes from the file starting at 1081344...
Reading 32768 bytes from the file starting at 1114112...
Reading 32768 bytes from the file starting at 1146880...
Reading 32768 bytes from the file starting at 1179648...
Reading 32768 bytes from the file starting at 1212416...
Reading 32768 bytes from the file starting at 1245184...
Reading 32768 bytes from the file starting at 1277952...
Reading 32768 bytes from the file starting at 1310720...
Reading 32768 bytes from the file starting at 1343488...
Reading 32768 bytes from the file starting at 1376256...
Reading 32768 bytes from the file starting at 1409024...
Reading 32768 bytes from the file starting at 1441792...
Reading 32768 bytes from the file starting at 1474560...
Reading 32768 bytes from the file starting at 1507328...
Reading 32768 bytes from the file starting at 1540096...
Reading 6310 bytes from the file starting at 1572864...

Looking for interface descriptors and code...
cbSearch= 8192 (0x00002000)
cbSearch= 8192 (0x00002000)
BIOS image size is : 1572864 (0x00180000)
Descriptors and code size is: 6283 (0x0000188B)

Verifying interface descriptors and code...
Allocating 6428 bytes for interface data and code...
Copying interface data and code...
Looking for the part table structure...
Part table contains 2 device(s)...
Looking for part descriptor...
Looking for part descriptor...
Looking for the text descriptor table structure...
Looking for Text descriptor...
Device name : SPI_DESC_4M (000400FF)
Version label: ALPHA
Block info : 1024X4K
Looking for Text descriptor...
Device name : SPI_DESC_4M_PP (000400FE)
Version label: ALPHA
Block info : 1024X4K
Looking for the platform descriptor ...
Looking for the keyboard table ...
Looking for the IBM table...
IBM signature found.
Looking for the nic descriptor ...
NIC descriptor signature "ZFNIC" wasn't found
Verifying the block table ...
4GB flash area is 172000h bytes: FFE8E000h-FFFFFFFFh

Combine flags from the platform descriptor with flags from UI or command line
Platform descriptor flags : 40022024
UI or command line flags : 488201A3
UI or command line masks : 00000000
Effective flags : 488201A3
DMI update mode : 2
Stage completed

[08/12/18 10:31:10]
Analysis stage

Loading and initializing driver...
Installing and loading Windows NT driver: C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\PHLASHNT.SYS
Initializing driver...

m_pbThisBase : 1c118e0h
m_dwSize : 191ch
m_dwSizeFlashInt : 188bh
m_dwSizeRomImage : 180000h
m_dw4GBStart : ffe8e000h
m_dw4GBSize : 172000h
m_bPartCount : 2h
m_pPartTable : 1c12874h
m_pDeviceTable : 1c11971h
m_pPartDescr : 1c11901h
m_pTextDescr : 1c11929h
m_pPlatform : 1c11981h
m_pBlockTbl : 1c119f9h
m_pFixupTbl : 0h
m_pKeyboardTbl : 0h
m_pIBM : 1c119ceh
m_pNIC : 0h
m_dwPassword : 0h
m_pSLPTable : 0h
Read system BIOS to analysis
gEscdSaveMode = 1 gSetupVarVolSaveMode=0 gUefiVarVolSaveMode=0.
checkFfsValid ...

checkFfsValid(1a10020h, 180000h, 1)
gFfsModuleAddressMaxium=1fffffh
volumedir location=fe5effe0h.
It's non-FFS type bios.
getBcpSysInfo(1a10020, 180000) ... O.K.
getBcpDmiInfo(1a10020h, 180000h, 168040h) ...
dmi[0]=30b7h, 16b0f7h => LENOVO
dmi[1]=30d3h, 16b113h => LENOVO
dmi[2]=30efh, 16b12fh => NONE
dmi[3]=310bh, 16b14bh => NONE
dmi[4]=2ffeh, 16b03eh => LENOVO
dmi[5]=301ah, 16b05ah => INVALID
dmi[6]=3036h, 16b076h => ThinkCentre XXXX
dmi[7]=3052h, 16b092h => INVALID
dmi[8]=315fh, 16b19fh => LENOVO
dmi[9]=317bh, 16b1bbh => NONE
dmi[10]=3197h, 16b1d7h => NONE
dmi[11]=31b3h, 16b1f3h =>
dmi[12]=30a5h, 16b0e5h => FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
dmi[13]=31cfh, 16b20fh => BB:xxxxx O.K.
BcpNvs ver:0.2
gEscdStartImage=0h, gEscdSizeImage= 2000h.

Vol recorder ...
Vol[0] ' ESCD': ( 0h, 2000h)
Vol[1] ' SETUP': ( 0h, 0h)
Vol[2] ' UEFIV': ( 0h, 0h)
Vol[3] ' DMIV': ( 0h, 0h)
checkFfsValid(2850020h, 180000h, 0)
gFfsModuleAddressMaxium=1fffffh
volumedir location=fd7affe0h.
It's non-FFS type bios.
getBcpSysInfo(2850020, 180000) ... O.K.
getBcpDmiInfo(2850020h, 180000h, 168040h) ...
dmi[0]=30b7h, 16b0f7h => LENOVO
dmi[1]=30d3h, 16b113h => LENOVO
dmi[2]=30efh, 16b12fh => NONE
dmi[3]=310bh, 16b14bh => NONE
dmi[4]=2ffeh, 16b03eh => LENOVO
dmi[5]=301ah, 16b05ah => 6209A95
dmi[6]=3036h, 16b076h => ThinkCentre M58p
dmi[7]=3052h, 16b092h => S4MA711
dmi[8]=315fh, 16b19fh => LENOVO
dmi[9]=317bh, 16b1bbh => NONE
dmi[10]=3197h, 16b1d7h => NONE
dmi[11]=31b3h, 16b1f3h => ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
dmi[12]=30a5h, 16b0e5h => 00 CE C6 1C 46 A9 DF 11 B9 35 94 A7 19 E8 08 46
dmi[13]=31cfh, 16b20fh => BB:xxxxx O.K.
BcpNvs ver:0.2
gEscdStartRom=0h, gEscdSizeRom= 2000h.

Vol recorder ...
Vol[0] ' ESCD': ( 0h, 2000h)
Vol[1] ' SETUP': ( 0h, 0h)
Vol[2] ' UEFIV': ( 0h, 0h)
Vol[3] ' DMIV': ( 0h, 0h)checkFfsValid completed

Totoal PartlyBiosUpdate = 0

Get BIOS information from image file...

PhlashGetBiosInfo ... copyNewImageDmiInfo BCPSYS information:
Version : 3.3
Size : 131
Date : 5/7/2012
Time : 11:22:50
Part number: 5CKT77AUSè(KT7)
OemVer :
BCPDMI information:
Version : 2.11
Size : 40
OEM strings: 1
OEM strings: BB:xxxxx
New BIOS :191ch, 188bh, 180000h, ffe8e000h, 172000h, 2h

Get BIOS information from system...
copyOldImageDmiInfo BCPSYS information:
Version : 3.3
Size : 131
Date : 5/7/2012
Time : 11:22:50
Part number: 5CKT77AUSè(KT7)
OemVer :
BCPDMI information:
Version : 2.11
Size : 40
OEM strings: 1
OEM strings: BB:xxxxx
BIOS image is not Axx swapped
Old BIOS :191ch, 188bh, 180000h, ffe8e000h, 172000h, 2h
Stage completed

[08/12/18 10:31:32]
Get BIOS information from image file...

PhlashGetBiosInfo ... copyNewImageDmiInfo BCPSYS information:
Version : 3.3
Size : 131
Date : 5/7/2012
Time : 11:22:50
Part number: 5CKT77AUSè(KT7)
OemVer :
BCPDMI information:
Version : 2.11
Size : 40
OEM strings: 1
OEM strings: BB:xxxxx
New BIOS :191ch, 188bh, 180000h, ffe8e000h, 172000h, 2h

[08/12/18 10:31:33]
Combine flags from the platform descriptor with flags from UI or command line
Platform descriptor flags : 40022024
UI or command line flags : 488201A3
UI or command line masks : 01D121A6
Effective flags : 488201A3
DMI update mode : 2

[08/12/18 10:32:24]
Read system BIOS stage
Skipped: ROM read already.
Stage completed

[08/12/18 10:32:24]
Saving system BIOS backup file...
Creating file C:\Users\MobiPhone\Desktop\5cjy77usa-Mod\bios.bak...
Writing 32768 bytes to the file starting at 0...
Writing 32768 bytes to the file starting at 32768...
Writing 32768 bytes to the file starting at 65536...
Writing 32768 bytes to the file starting at 98304...
Writing 32768 bytes to the file starting at 131072...
Writing 32768 bytes to the file starting at 163840...
Writing 32768 bytes to the file starting at 196608...
Writing 32768 bytes to the file starting at 229376...
Writing 32768 bytes to the file starting at 262144...
Writing 32768 bytes to the file starting at 294912...
Writing 32768 bytes to the file starting at 327680...
Writing 32768 bytes to the file starting at 360448...
Writing 32768 bytes to the file starting at 393216...
Writing 32768 bytes to the file starting at 425984...
Writing 32768 bytes to the file starting at 458752...
Writing 32768 bytes to the file starting at 491520...
Writing 32768 bytes to the file starting at 524288...
Writing 32768 bytes to the file starting at 557056...
Writing 32768 bytes to the file starting at 589824...
Writing 32768 bytes to the file starting at 622592...
Writing 32768 bytes to the file starting at 655360...
Writing 32768 bytes to the file starting at 688128...
Writing 32768 bytes to the file starting at 720896...
Writing 32768 bytes to the file starting at 753664...
Writing 32768 bytes to the file starting at 786432...
Writing 32768 bytes to the file starting at 819200...
Writing 32768 bytes to the file starting at 851968...
Writing 32768 bytes to the file starting at 884736...
Writing 32768 bytes to the file starting at 917504...
Writing 32768 bytes to the file starting at 950272...
Writing 32768 bytes to the file starting at 983040...
Writing 32768 bytes to the file starting at 1015808...
Writing 32768 bytes to the file starting at 1048576...
Writing 32768 bytes to the file starting at 1081344...
Writing 32768 bytes to the file starting at 1114112...
Writing 32768 bytes to the file starting at 1146880...
Writing 32768 bytes to the file starting at 1179648...
Writing 32768 bytes to the file starting at 1212416...
Writing 32768 bytes to the file starting at 1245184...
Writing 32768 bytes to the file starting at 1277952...
Writing 32768 bytes to the file starting at 1310720...
Writing 32768 bytes to the file starting at 1343488...
Writing 32768 bytes to the file starting at 1376256...
Writing 32768 bytes to the file starting at 1409024...
Writing 32768 bytes to the file starting at 1441792...
Writing 32768 bytes to the file starting at 1474560...
Writing 32768 bytes to the file starting at 1507328...
Writing 32768 bytes to the file starting at 1540096...
Writing 6283 bytes to the file starting at 1572864...
Stage completed

[08/12/18 10:32:27]
Flashing new BIOS stage

Verifying BIOS checksum...
Check if BIOS part numbers are the same
Passed Ok

[08/12/18 10:32:27]SLP process begin
SLP case 4:Normal process.

[08/12/18 10:32:27]theIbm.checkIBM() ...

[08/12/18 10:32:28]CheckIbmPassword() ...
Start IBM Query Pap
After this the screen freezes and I get BSOD (0x7f)

Thanks once again!
 
First, on your first post, I replaced all the microcodes, adding is fine if you know how to do it. But outside of knowing what you are doing, in general yes you want to replace a microcode not add to the pile leaving old in and adding new

Did you make the registry changes above before running the flash attempt that provided the above log? If not, make those edits and try again before anything mentioned below.


The main thing about this BIOS style and flasher is that the microcodes are also separate outside of the BIOS, that's why I mentioned to uncheck the VCPU/Install processor patches, because that is not needed since I put them in the BIOS.
I should have mentioned that in advance but didn't think about it.

From your log I see checksum and BIOS check passes OK. At the end it stalls or dies on password check, do you have any passwords set for the BIOS or the hard drive? If yes, disable those for now before flashing and then put back later.
This may be misleading, since we can't see next stage that might be what really causes the issue and not the IBM pass check thing.
And I checked that, it's a BIOS signature which is there and correct, so this probably does not refer to bitlocker or BIOS/HDD pass, but disable these anyway if you want.

Everything looks good up to this point, all checks pass, all BIOS verification measures OK, etc. No issue with the BIOS, something in the settings is causing this.
First, please try again unchecking the two things I mentioned above, VCPU/Processor patches (This is the main issue I believe, since these would conflict with what I put in the BIOS), and Clear CMOS.
Now also uncheck "Flash only if BIOS version is newer than system" Then try to flash again.

Then if that fails, do again but this time before flash open phlash.ini file and in the bottom section (Main) update mode to 0 instead of 2 (This is update BIOS only, preserve DMI - while 2 = update both from BIOS file)
Also, if we're at this stage, lets go ahead and remove the DetectBitLocker=1 command too, by changing this to 0 - only do this once you had disabled any BIOS and or hard drive password you might have set.

If that fails too, edit phlash.ini once again and set user mode at bottom section to ffffffff instead of 2

Also, anytime you can remove all the CPU microcode updates from the main folder too if you want, since these are not meant to be used and we're specifically telling the program to not use them right now too.
These are the .PAT and .HSH files, as seen here - https://i.imgur.com/HoIDVx5.png
Along with the 1kb rspfile (This is command file that loads the above)
 
First, on your first post, I replaced all the microcodes, adding is fine if you know how to do it. But outside of knowing what you are doing, in general yes you want to replace a microcode not add to the pile leaving old in and adding new

Did you make the registry changes above before running the flash attempt that provided the above log? If not, make those edits and try again before anything mentioned below.


The main thing about this BIOS style and flasher is that the microcodes are also separate outside of the BIOS, that's why I mentioned to uncheck the VCPU/Install processor patches, because that is not needed since I put them in the BIOS.
I should have mentioned that in advance but didn't think about it.

From your log I see checksum and BIOS check passes OK. At the end it stalls or dies on password check, do you have any passwords set for the BIOS or the hard drive? If yes, disable those for now before flashing and then put back later.
This may be misleading, since we can't see next stage that might be what really causes the issue and not the IBM pass check thing.
And I checked that, it's a BIOS signature which is there and correct, so this probably does not refer to bitlocker or BIOS/HDD pass, but disable these anyway if you want.

Everything looks good up to this point, all checks pass, all BIOS verification measures OK, etc. No issue with the BIOS, something in the settings is causing this.
First, please try again unchecking the two things I mentioned above, VCPU/Processor patches (This is the main issue I believe, since these would conflict with what I put in the BIOS), and Clear CMOS.
Now also uncheck "Flash only if BIOS version is newer than system" Then try to flash again.

Then if that fails, do again but this time before flash open phlash.ini file and in the bottom section (Main) update mode to 0 instead of 2 (This is update BIOS only, preserve DMI - while 2 = update both from BIOS file)
Also, if we're at this stage, lets go ahead and remove the DetectBitLocker=1 command too, by changing this to 0 - only do this once you had disabled any BIOS and or hard drive password you might have set.

If that fails too, edit phlash.ini once again and set user mode at bottom section to ffffffff instead of 2

Also, anytime you can remove all the CPU microcode updates from the main folder too if you want, since these are not meant to be used and we're specifically telling the program to not use them right now too.
These are the .PAT and .HSH files, as seen here - https://i.imgur.com/HoIDVx5.png
Along with the 1kb rspfile (This is command file that loads the above)
Okay, once again, thanks for your help. I did the registry edits before last reply (only iaStorV had the start value to 3 - I changed it to 0, the others had it 0) but I'm sorry I forgot to mention it. I reset the BIOS to default settings, then disabled everything that had to do with passwords in BIOS. Then I disabled CPU Virtualization (I thought this had to do something with VCPU that you are telling me). After that I did the changes in Phlash.ini, "Flash only if BIOS version is newer than system" was already disabled since I flashed the latest BIOS successfully. User mode was already fffffff, but I still get the same BSOD.

I'm having trouble finding the VCPU/Processor patches option, I checked WinPhlash settings and BIOS settings (I thought CPU Virtualization had something to do with that so I disabled it), I also googled that but I couldn't find anything. In the meantime I am going to try and mod the original BIOS to only add X3323 microcode until you reply to me.

Thanks for your help dude, you're really trying hard to fix my problem, you are a beast.
 
Nothing to do with virtualization, so no need to look further about that. I am sorry it's still not flashed :D

Please show me an image of what you see on the advanced options window before you hit flash (Never mind, I was able to view it in XP). Also, are you using the package I uploaded?
User mode should not already be ffffffff, at least it's not in the phlash.ini in the package I uploaded (In what I uploaded it's set to =2), that's the only reason I am asking (I am not sure which is best to use, only put that as suggestion to try later)

The VCPU option I thought would be shown in the main advanced options window before you flash, if it's not, good (see above) I only wanted you to uncheck it if it was there. Please delete the microcode files I showed you an image of, and the rspfile, then try the flash again.
Also be sure to uncheck "Flash only if the BIOS version is different, and flash only if the BIOS version is newer"

If you want only 10676 updated I can do that (it's already there, but only two platforms - needs three CPUID's to cover all for this mod), but I believe you will have same issue. Either this is due to some check, which it looks like it checks a lot and all passed, or the microcode update files I mentioned.
And the updates are like this, one microcode now covers the two microcodes in your BIOS, so if I only put in one I would remove two. If I put all three, I remove two and increase count by one. So either way you cannot have same count of microcodes in the past, or you wont cover all platforms for this CPUID and we are not sure which platform you need for your board + this CPU since it doesn't belong on your board (That is why all are often added, to cover all platforms.)

Please test with all those and rspfile removed and then if still no luck I will send BIOS with only 10676 updated

And easier test would be this, to see if you can flash modified BIOS or not, update a single microcode not dealing with your CPU, such as 6F2. Then see if you can flash, if not we know this is the issue, something with modifying BIOS breaks update method.
If you want to test this way before anything else, I will make BIOS like that for you shortly. I think we should do this, because if it wont flash then we know the modification is an issue somehow.

You may need to order a CH341A flash programmer, they are only $3 Please before you do that, take some images of your motherboard so I can see the BIOS, this way you get the correct adapter or cables to go with the flash programmer.


*Edit! OK, I found the problem, those .pat and .hsh files may be used no matter what (You verify please by deleting them and see if same error, or new error)
I think I have found solution, but it will take me some time to do a new mod again. I need to find Lenovo BIOS with the updated files already in it, or at least all the platforms already in it for the 10676 CPUID (ie one that supports your CPU by default)
That way I can get the matching .hsh file for the .pat file (actual microcode). Once all that matches what I put in BIOS, even if I redo it and only update the 10676 I need these.


So wait a little bit while I work on this, if you find compatible Lenovo system for your CPU please post links to BIOS download, thanks!
I found bladecenter HS12 is compatible with that CPU, but you have to sign in to IBM to download any files :mad:


I think we can flash current BIOS as-is, by itself, outside of all those files, from DOS using new winphlash or phlash16 I have both non-Lenovo.
The problem as it is now is due to the flasher, it's method, and the contents involved, going away from that works OK in many instances.
Do you want to try that? If yes, I will upload tomorrow and post instructions etc.
 
Nothing to do with virtualization, so no need to look further about that. I am sorry it's still not flashed :D

Please show me an image of what you see on the advanced options window before you hit flash (Never mind, I was able to view it in XP). Also, are you using the package I uploaded?
User mode should not already be ffffffff, at least it's not in the phlash.ini in the package I uploaded (In what I uploaded it's set to =2), that's the only reason I am asking (I am not sure which is best to use, only put that as suggestion to try later)

The VCPU option I thought would be shown in the main advanced options window before you flash, if it's not, good (see above) I only wanted you to uncheck it if it was there. Please delete the microcode files I showed you an image of, and the rspfile, then try the flash again.
Also be sure to uncheck "Flash only if the BIOS version is different, and flash only if the BIOS version is newer"

If you want only 10676 updated I can do that (it's already there, but only two platforms - needs three CPUID's to cover all for this mod), but I believe you will have same issue. Either this is due to some check, which it looks like it checks a lot and all passed, or the microcode update files I mentioned.
And the updates are like this, one microcode now covers the two microcodes in your BIOS, so if I only put in one I would remove two. If I put all three, I remove two and increase count by one. So either way you cannot have same count of microcodes in the past, or you wont cover all platforms for this CPUID and we are not sure which platform you need for your board + this CPU since it doesn't belong on your board (That is why all are often added, to cover all platforms.)

Please test with all those and rspfile removed and then if still no luck I will send BIOS with only 10676 updated

And easier test would be this, to see if you can flash modified BIOS or not, update a single microcode not dealing with your CPU, such as 6F2. Then see if you can flash, if not we know this is the issue, something with modifying BIOS breaks update method.
If you want to test this way before anything else, I will make BIOS like that for you shortly. I think we should do this, because if it wont flash then we know the modification is an issue somehow.

You may need to order a CH341A flash programmer, they are only $3 Please before you do that, take some images of your motherboard so I can see the BIOS, this way you get the correct adapter or cables to go with the flash programmer.


*Edit! OK, I found the problem, those .pat and .hsh files may be used no matter what (You verify please by deleting them and see if same error, or new error)
I think I have found solution, but it will take me some time to do a new mod again. I need to find Lenovo BIOS with the updated files already in it, or at least all the platforms already in it for the 10676 CPUID (ie one that supports your CPU by default)
That way I can get the matching .hsh file for the .pat file (actual microcode). Once all that matches what I put in BIOS, even if I redo it and only update the 10676 I need these.


So wait a little bit while I work on this, if you find compatible Lenovo system for your CPU please post links to BIOS download, thanks!
Okay, I think its time for some change of plans. I recently got a Core 2 Quad Q9300 CPU so I might use it instead of the X3323, but I need to know if the Q9300 is "plug and play". I tried updating the BIOS using DOS and the beeps are reaaally scary (the update failed but the PC still boots - I don't know what error it showed), so I think I might give up the plan for the M58p xeon mod. Can you please tell me if I can only install the Q9300 in the socket and boot the Lenovo M58p, and also how do I install the Xeon X3323 on Intel DP43TF motherboard. If I need to update the BIOSes, can you please help me do that? You've been great help, thanks once again :) .
 
See above, I made some edits. Yes, Q9300 should be drop-in plug and play in the M58P
For the Intel and that CPU, you will also need to do a BIOS mod, but it's much easier, however can only be done if you have CH341A flash programmer and SOIC8 text clip jumper cable.
This is due to you have to dump current BIOS, send to me to update, then you program back with flash programmer.


Due to Intel's BIOS packaging structure, and signature hashes etc, you cannot modify their BIOS and flash in, mods can only be done with flash programmer.


Here is package for you, includes BIOS file only and new DOS and Windows (Non-Lenovo Phlash apps)
https://www.sendspace.com/file/rygsnv


For DOS use this >> PHLASH16 /MODE=2 /R=3 /S /X /FORCE biosfile.rom


For windows which you can try first if you want, should work, you already know the above mentioned items to check/uncheck in advanced options
Don't add any other files to the folders when updating. If windows one fails, or some error edit the phlash.ini to this

[UI]
Advanced=1
;FlashOnlyEnable=1
;EnableLog=0
StartScreen=0
Confirmation=0
;LOGO=demo_1.bmp
;DetectBitLocker=1
;SaveEscdMode=1


[Main]
RetryCount=3
UpdateMode=2
FormatVersion=2
UpdateFlags=488221a7
UserFlags=8021a4
UserMask=d121a4
PSIFlags=40022024
UserMode=2
BackupFile=bios.bak
ImageFile=$image5C.usf
 
See above, I made some edits. Yes, Q9300 should be drop-in plug and play in the M58P
For the Intel and that CPU, you will also need to do a BIOS mod, but it's much easier, however can only be done if you have CH341A flash programmer and SOIC8 text clip jumper cable.
This is due to you have to dump current BIOS, send to me to update, then you program back with flash programmer.


Due to Intel's BIOS packaging structure, and signature hashes etc, you cannot modify their BIOS and flash in, mods can only be done with flash programmer.


Here is package for you, includes BIOS file only and new DOS and Windows (Non-Lenovo Phlash apps)
https://www.sendspace.com/file/rygsnv


For DOS use this >> PHLASH16 /MODE=2 /R=3 /S /X /FORCE biosfile.rom


For windows which you can try first if you want, should work, you already know the above mentioned items to check/uncheck in advanced options
Don't add any other files to the folders when updating. If windows one fails, or some error edit the phlash.ini to this

[UI]
Advanced=1
;FlashOnlyEnable=1
;EnableLog=0
StartScreen=0
Confirmation=0
;LOGO=demo_1.bmp
;DetectBitLocker=1
;SaveEscdMode=1


[Main]
RetryCount=3
UpdateMode=2
FormatVersion=2
UpdateFlags=488221a7
UserFlags=8021a4
UserMask=d121a4
PSIFlags=40022024
UserMode=2
BackupFile=bios.bak
ImageFile=$image5C.usf
Kinda got mixed up, is this new file for Lenovo M58p X3323 modded BIOS file, or for the intel. Judging by the $image5C.usf , it seems like its the new modded BIOS you made for the Lenovo. Since Intel board require extra parts, I'll try to make X3323 work with the Lenovo, because it takes almost 2 months to get products ordered online.

Thanks dude!
 
Slow down little bit then :D I said Intel is not possible until you have CH341A flash programmer and SOIC8 text clip cable, then you send me backed up BIOS using programmer I edit it and then you program it back to the board.


In the end, you may need programmer for either board, go ahead and order one now since they are so cheap, then they will be here before you know it.

In case you still aren't sure, yes that is new BIOS and 2 x new flashing tools for the Lenovo board. Please read it all carefully so no mistakes are made.
And if you are scared, you can remove the DOS /force flag when/if you have to flash in DOS, but I bet new winphlash and included BIOS will get you flashed in windows


Also, please throw away previous BIOS file, I found invalid header in file, so that may be part of why it failed too! New BIOS doe not have this, and should flash fine using the above non-Lenovo specific phlash tools
 
Slow down little bit then :D I said Intel is not possible until you have CH341A flash programmer and SOIC8 text clip cable, then you send me backed up BIOS using programmer I edit it and then you program it back to the board.


In the end, you may need programmer for either board, go ahead and order one now since they are so cheap, then they will be here before you know it.

In case you still aren't sure, yes that is new BIOS and 2 x new flashing tools for the Lenovo board. Please read it all carefully so no mistakes are made.
And if you are scared, you can remove the DOS /force flag when/if you have to flash in DOS, but I bet new winphlash and included BIOS will get you flashed in windows


Also, please throw away previous BIOS file, I found invalid header in file, so that may be part of why it failed too! New BIOS doe not have this, and should flash fine using the above non-Lenovo specific phlash tools
Oh no, it's stuck like this.. What do I do?
Image


Cursor and clock are frozen..
 
I'm wondering what would be needed to push the updated microcodes into the BIOS file for a Gigabyte GA-EP45-DS4P?

I'm looking at putting a Xeon L5430 into it. I would appreciate any help, the system currently is home to a EP43-DS3L and a older stepping X3350, but it has always been a moody chip, and the L is 50W compared to 95W for the X. I'm concerned about the microcode because the bios dates/official support lists are similar, and I've never been able to get the EP43 to report the CPU temp properly, cores read properly but, the bios reported temps are always 30'C too low, so I can't use the auto fan control.

It's perfectly capable for what the wife needs and uses it for, and dropping the 650 Ti for an MSI Aero 560, will see some pretty decent power savings. I guess it's a bit of a side grade for her. heh
 
@gamefoo21 - I can update and add any microcodes to your EP45-DS4P, what is the stepping on your X3350 so I can be sure the correct microcode is added.
And please confirm which CPU too L5430 or the X3350, I think you meant the L5430

@shabann - sorry for the scary flash freeze, and leaving you out here with no reply! I wonder why DOS worked but Windows stalled out on you?
It must have been one of the flags in DOS made it work and that one wasn't used in the windows flash process.

So I can know in the future with similar boards if anyone needs, what flags did you end up using in DOS? Thanks!
And you're welcome, sorry it took so long and was such a stressful process! :D


Cool it's finally working now! :thumb:
 
@gamefoo21 - I can update and add any microcodes to your EP45-DS4P, what is the stepping on your X3350 so I can be sure the correct microcode is added.
And please confirm which CPU too L5430 or the X3350, I think you meant the L5430
Yeah the main chip is going to be the L5430 which is an E0. The current chip in her EP43 and I guess backup CPU, is the X3350 and it's a C1 stepping.

I thank you so much for the help, it's hugely appreciated. Do you mind letting me know how wildly out of date the stock micro-codes are?
 
12,701 - 12,720 of 13,002 Posts