• 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.

Post 88 code on DFI DK x58...WTF?

PaulieG

PaulieG

Joined
Feb 19, 2007
Messages
12,453 (1.87/day)
Location
Yankee lost in the Mountains of East TN
System Specs
Processor 5800x(2)/5700g/5600x/5600g/2700x/1700x/1700
Motherboard MSI B550 Carbon (2)/ MSI z490 Unify/Asus Strix B550-F/MSI B450 Tomahawk (3)
Cooling EK AIO 360 (2)/EK AIO 240, Arctic Cooling Freezer II 280/EVGA CLC 280/Noctua D15/Cryorig M9(2)
Memory 32 GB Ballistix Elite/32 GB TridentZ/16GB Mushkin Redline Black/16 GB Dominator
Video Card(s) Asus Strix RTX3060/EVGA 970(2)/Asus 750 ti/Old Quadros
Storage Samsung 970 EVO M.2 NVMe 500GB/WD Black M.2 NVMe 500GB/Adata 500gb NVMe
Display(s) Acer 1080p 22"/ (3) Samsung 22" 1080p
Case (2) Lian Li Lancool II Mesh/Corsair 4000D /Phanteks Eclipse 500a/Be Quiet Pure Base 500/Bones of HAF
Power Supply EVGA Supernova 850G(2)/EVGA Supernova GT 650w/Phantek Amps 750w/Seasonic Focus 750w
Mouse Generic Black wireless (5)
Keyboard Generic Black wireless (5)
Software Win 10/Ubuntu
Hey guys. I'm having some issues with my DFI DK x58. Certainly not as severe as fits, but annoying still. For some reason, despite the fact that I can get a 4.0ghz overclock OCCT stable, when I turn the rig on after the power has been off awhile, I get a post 88 code. It's one of those undefined, "your bios is screwed" codes. Thing is, if I reset the cmos, all is fine again. WTF guys? Any ideas?
I should mention that this is happening at every stable overclock, from 3.6-4.0.
 
according to what i read on newegg reviews of dfi boards, code 88 = RMA
 
LittleLizard said:
according to what i read on newegg reviews of dfi boards, code 88 = RMA
Click to expand...

No offense, but that's newegg. If I was post 88 all of the time, then I would say the bios is corrupt, but it's only happening after I've powered down for awhile, and like I said, if I clear cmos it's fine again.

Fitseries3 said:
bios update?
Click to expand...

Yeah, I need to, but I don't own a floppy, and I can't get the USB drive procedure to work.
 
he seems right tho paulie check my link.
 
update. it solved a fw minor shit things like that from what i've read.
 
I have to agree with fits as an update may be the fix. it shows as FUBAR'd bios or the plain need to RMA as issues. So possibly flashing corrects the issue. Whats the worst, the flash fails and you have to RMA anyways?
 
sneekypeet said:
I have to agree with fits as an update may be the fix. it shows as FUBAR'd bios or the plain need to RMA as issues. So possibly flashing corrects the issue. Whats the worst, the flash fails and you have to RMA anyways?
Click to expand...

Yeah, I already had the list of post codes, but I've received post 88 codes on other DFI boards, which were usually solved with tweaking. I'd love to flash the board, but I'm running Vista 64 bit, and I don't have a floppy. The USB drive procedure did not work. Maybe I'll see if Logan has updated the Tmods bios CD.
 
That's sad to hear. I had the same issue with an Asus P5K Deluxe (no LCD readout obviously). It would be fine as long as it was running or hot booting but if it sat for a while it would need a CMOS CLR to boot. Eventually it got to where it would only boot with a CMOS CLR and all settings to default.

Could it be a bad battery? A stretch but if you have one you could borrow from another board it's an easy thing to test.
 
Winflash found at DFI in with the bios .zip has never failed me. set clocks to default in bios, then boot and flash....it turns off and tries to start. power it down move the cmos and return it then boot.

If you arent familiar hit me up I can walk ya through it
 
sneekypeet said:
Winflash found at DFI in with the bios .zip has never failed me. set clocks to default in bios, then boot and flash....it turns off and tries to start. power it down move the cmos and return it then boot.

If you arent familiar hit me up I can walk ya through it
Click to expand...

I was going to try winflash, but I read that DFI strongly discourages Winflash with Vista 64 and x58 boards.

From DFI Global:

"NOTE: users with VISTA 32 bit or VISTA 64 bit should NOT use Winflash 1.92 to flash bios but should use a USB stick. You can Click HERE to view instructions for flashing bios with Usb stick when your operating system is VISTA 32 bit or VISTA 64 bit."
 
Paulieg said:
I was going to try winflash, but I read that DFI strongly discourages Winflash with Vista 64 and x58 boards.
Click to expand...

Not aware of that! Havent done any homework on the X58 versions!
 
sneekypeet said:
Not aware of that! Havent done any homework on the X58 versions!
Click to expand...

I revised my last post with a note from the bios section for my board. Apparently this is regarding any chipset, if you are running vista. Sneeky, are you running Vista?
 
DONT USE WINFLASH.

use a flashdrive.

the ZIP file has awdflash and the bios in it.
 
It says that on all the pages tho.. It's useless with out the flash, and it's still gonna be useless if it's bricked from a bad flash..
 
Paulieg said:
I revised my last post with a note from the bios section for my board. Apparently this is regarding any chipset, if you are running vista. Sneeky, are you running Vista?
Click to expand...

I flash in any OS...flashed my DK P35 not to long ago! Only bricked my Blood Iron this route and the bios was modded and I saw it crash another board the day b4. *sorta knew it was bad, just wanted to be positive*

No offesne to anyone but most window flash failures are a bad bios mod or the misuse of winflash itself!
 
Fitseries3 said:
DONT USE WINFLASH.

use a flashdrive.

the ZIP file has awdflash and the bios in it.
Click to expand...

Yeah, I tried the awdflash, but it didn't work. Maybe I did something wrong? Someone with a tutorial on awdflash? I've always used a floppy, or a utility like Asus has.

sneekypeet said:
I flash in any OS...flashed my DK P35 not to long ago! Only bricked my Blood Iron this route and the bios was modded and I saw it crash another board the day b4. *sorta knew it was bad, just wanted to be positive*

No offesne to anyone but most window flash failures are a bad bios mod or the misuse of winflash itself!
Click to expand...


Have you used winflash in Vista 64 bit?
 
powered down for awhile? maybe bad batt? try swapping from another board see if you still get the issue. if you need help flashing i can help look below.
 

Attachments

You need winflash. awdflash is a dos program if I'm not mistaken.
 
Solaris17 said:
powered down for awhile? maybe bad batt? try swapping from another board see if you still get the issue. if you need help flashing i can help look below.
Click to expand...

I'm going to try this again. With the HP USB program, in the box for "using dos system files located at", what drive do I point it to?

ShadowFold said:
You need winflash. awdflash is a dos program if I'm not mistaken.
Click to expand...

See the posts above regarding DFI's stance on winflash.
 
Paulieg said:
I'm going to try this again. With the HP USB program, in the box for "using dos system files located at", what drive do I point it to?



See the posts above regarding DFI's stance on winflash.
Click to expand...

point to the files that i included in the zip. those are the boot files :)
 
Solaris17 said:
point to the files that i included in the zip. those are the boot files :)
Click to expand...

I keep getting this:

bioshp.png
 
You must log in or register to reply here.
Back
Top