bios help GA-X58A-UD3R

[Aussie Allan]

   Eeeeeeer .... we don't have remote access to your machine  .....possibly you could post a snip of the error screen it generates and we can have a squizzy then

  Aussie Allan

[gd]

Uploaded with ImageShack.us

you dont need remote but if you do i will let you .
but i could send the file for you to look at .

thanks

[Aussie Allan]

  Possible fix with the extra information provided;

  Windows Update (KB973879) has been causing a “blue screen of death” (stop error) in many computers running Windows Vista 64-bit edition.

  This has been proven to effect Windows 7 installations as well....

    The specific error is:

    A problem has been detected and Windows has been shut down to prevent damage to your computer.
    …
    Technical information:

    *** STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF800020393AA, 0xFFFFFA60021EE7D8, 0xFFFFFA60021EE1b0)

  Link and fix here....http://www.techerator.com/2009/08/fix-windows-vista-64-bit-gets-blue-screen-after-windows-updates/

  If it's not a fix it's a step in the right direction.

  Aussie Allan

[gd]

no allan i dont have that update in my update history .
i could not get hold of my m8 to borrow the card too ;( .

im going to format and put win7 64bit back on the ssd .
when its finished im not going to use my disc's for the drivers , i have got them on my backup hd ready .

no updates until i test it again .
did the screen shot not help ? .

[Aussie Allan]

  Gd

   We all have our forte's ....a screen full of zero's and one's doesn't float my boat.....but getting better!

  Day's end ....you shouldn't be having these problems as your kit seems to be good.....I think what you posted as your next course of action is the way to go

  Just start with the minimum in the system and do it right from the get-go ..... ACHI......SSD......load the drivers one at a time ..... check stability between more drivers ......take notes.....and see where it falls over,.... if it falls over again

  And yes start with the latest Bios! and only use the latest drivers of gigas website ....let me know how you go!

  Aussie Allan

[gd]

  your funny allan .

i have only added the network driver like Dark Mantis suggested .
thats all im going to add , then i will see if it starts up after a couple of hours .

ok just 1 thing to make me smile today ,,,, is it fixable ? will it eventually work or should i be looking to replace something .

thanks

[Aussie Allan]

    ok just 1 thing to make me smile today ,,,, is it fixable ? ........YES! Continue smiling!

   will it eventually work or should i be looking to replace something .  See above!.....I do feel we will have a good result with this post log.....

  But we still have to appease the PC god..........Burn a chicken to make sure !

  Aussie Allan

[Dark Mantis]

Just to point you in the right direction and give you some idea of the problem the BSOD screen that you mentioned has the STOP code 0x7E which equates to 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

[gd]

no luck for me today .
had blue screen again on first boot .

the error type is the same .

only driver in place is the network , everything else is whats installed while main install .

thanks
do you want pic of error log ? .

[gd]

Uploaded with ImageShack.us

[Aussie Allan]

 Gd

  Man  this doing my head in.......Ive just re-read the entire post twice to see what we might have missed.

  Can you tell me what ports you have everything connected too .... including the CD/DVD and what controllers you have active in BIOS

  List what you have IDE or ACHI,ACHI/RAID active with as well.....where missing something!

  Aussie Allan

[gd]

ok iv just done a fresh install using my m8ts gt 340 and it did it with that too ;( .
i have everything in the peripheral area turned off .
except sata controller at the top and i have it set to ACHI mode .
i have the hd in port 0 , my rom in port 3 and when its in i have my backup hd in port 4 .
my cards in the top port and set to 16x
i have the cpu at x21 and the memory running in standard
i updated bios to f8a and its still the same .

if it happening without any drivers installed ,,, it maybe something in the bios im doing .
cos i use 64 bit i have it set to 64 bit in the bios area i set it to both and its the same .

[gd]

i just read it all too .
no1 asked how fare it gets before it blue-screens .

well i get my desktop up and the sound of it booting up , i even can open 1 or 3 folders .
15 20 seconds after the boot-up sound it crashes counts to 100 and reboots , if i let it just try doing a reboot after it will just keep blue screening ,, if i press the on off and turn it off then start it again its fine . maybe replace some lost files .

so its something after boot ,,,, but only just after .

thanks



Uploaded with ImageShack.us

bios f8a



Uploaded with ImageShack.us

everything below hw lan is off



Uploaded with ImageShack.us

[Dark Mantis]

no1 asked how fare it gets before it blue-screens .

well i get my desktop up and the sound of it booting up , i even can open 1 or 3 folders .
15 20 seconds after the boot-up sound it crashes counts to 100 and reboots , if i let it just try doing a reboot after it will just keep blue screening ,, if i press the on off and turn it off then start it again its fine . maybe replace some lost files .

so its something after boot ,,,, but only just after .

You say it happens just after boot but then carry on to say that you can open folders. So do you mean it happens literally just after boot or after loading Windows onto the system ?

If it is after Windows loading try running in safe mode and see if the problem is still there.


Also just to re-iterate something I said earlier that seemed to get lost, or ignored.....

Just to point you in the right direction and give you some idea of the problem the BSOD screen that you mentioned has the STOP code 0x7E which equates to 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

[Aussie Allan]

  1) turn off quick boot ....there's information posted that is lost to you while under quick boot.

  2) if you shoot (Photo) with the screen turned at about 10-20 degrees to the side .....we might be able to see what's on your screen

  3) turn off USB mouse and keyboard function ..... we need to have nothing interfering (more drivers loaded to do nothing)

   MORE INFORMATION

  IRQL_NOT_LESS_OR_EQUAL

The IRQL_NOT_LESS_OR_EQUAL error is caused by a buggy device driver or an actual hardware conflict. If you've recently added new hardware to your system, try removing it and see if the error goes away. Likewise, if you've recently loaded a new device driver

  NTFS_FILE_SYSTEM

An NTFS_FILE_SYSTEM error indicates hard disk corruption. If your system is bootable, run CHKDSK /F on all of your partitions immediately.

  Here is a source that might help you pin down the driver or conflict ...... there's a bit of reading but not half as much as time already spent

  http://technet.microsoft.com/en-us/library/cc750081.aspx  .... with problems like yours.....sometimes connecting the person with the right information can work wonders ..... hope this is true this time!

  Aussie Allan