Athlon64 + Asus K8VSE mobo question

  • Thread starter Thread starter Bulls Hit
  • Start date Start date
B

Bulls Hit

Well-known member
My friend has just had this rig built for his daw. He's got 1 gig ram and a 160GB Barracuda.

When he boots, it just sits on the Asus logo screen for about a minute. There's no disk activity happening. Eventually the Windows panel comes up and off she goes.

Is this normal? I'm not familiar with amd and those dodgy via chipsets. My P4P800 mobo sits on the Asus screen for about 3 seconds, then it's off.

Is there some bios setting he should be using?
 
Bulls Hit said:
My friend has just had this rig built for his daw. He's got 1 gig ram and a 160GB Barracuda.

When he boots, it just sits on the Asus logo screen for about a minute. There's no disk activity happening. Eventually the Windows panel comes up and off she goes.

Is this normal? I'm not familiar with amd and those dodgy via chipsets. My P4P800 mobo sits on the Asus screen for about 3 seconds, then it's off.

Is there some bios setting he should be using?
Click to expand...

There hasn't been anything "dodgy" about Via chipsets for quite awhile now. My Asus A7V600 is on the Asus screen for a split second then off she goes.

There's probably something wrong with his board, or memory.
 
Polaris20 said:
There's probably something wrong with his board, or memory.
Click to expand...

So you reckon it's either the board or the ram but not the chipset?

I'm not sure. He's also running an Audiophile 2496
 
He could check in the BIOS for a quick POST or quick boot option, that bypasses some of the initial system checks prior to boot.
 
Bulls Hit said:
So you reckon it's either the board or the ram but not the chipset?

I'm not sure. He's also running an Audiophile 2496
Click to expand...

I highly doubt the chipset would cause it to do that. On the other hand I've seen some weird $hit happen upon boot up when you use cheap dodgy RAM.
 
Bulls Hit said:
My friend has just had this rig built for his daw. He's got 1 gig ram and a 160GB Barracuda.
When he boots, it just sits on the Asus logo screen for about a minute. There's no disk activity happening. Eventually the Windows panel comes up and off she goes.
Is this normal? I'm not familiar with amd and those dodgy via chipsets. My P4P800 mobo sits on the Asus screen for about 3 seconds, then it's off. Is there some bios setting he should be using?
Click to expand...

I have the same MBO (K8V SE Deluxe) this MBO has many revisions and problems.

I have full functionality but every 10th time I get message : "Overclocking failed"

Do I need to mention I couldn't care less for overclocking or to even consider the same :(

Some suggest it is of thermal issue some problematic BIOS.

In either way Asus is dead silent about this.

Try to check every connection because this board will stop at any problem (very picky) check your memory and if that fails this the best place on web to get your problem solved : >>> http://forums.pcper.com/forumdisplay.php?f=8 <<<
 
Bulls Hit said:
My friend has just had this rig built for his daw. He's got 1 gig ram and a 160GB Barracuda.

When he boots, it just sits on the Asus logo screen for about a minute. There's no disk activity happening. Eventually the Windows panel comes up and off she goes.

Is this normal? I'm not familiar with amd and those dodgy via chipsets. My P4P800 mobo sits on the Asus screen for about 3 seconds, then it's off.

Is there some bios setting he should be using?
Click to expand...

1. Switch off boot logo 'Full screen logo show'
2. Change option in BIOS to 'Fast boot' or 'Quick boot', as suggested above
3. Switch off the POST reporter

There are other bot optimisers as well, but these should shave that time right off.
 
Sangram said:
1. Switch off boot logo 'Full screen logo show'2. Change option in BIOS to 'Fast boot' or 'Quick boot', as suggested above 3. Switch off the POST reporter

There are other bot optimisers as well, but these should shave that time right off.
Click to expand...

Sangram allready posted this note I wanted to add to my earlier post. Thanks ;)

However, 3 seconds is longer then
regular logo interval :(
 
Anthony, thanks for that link, looks good.

Sangram thanks for those tips. I'll try them on my machine as well
 
You must log in or register to reply here.
Back
Top