XXHighEnd - The Ultra HighEnd Audio Player
February 05, 2016, 10:52:21 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Dec. 31, 2012 : XXHighEnd + Phasure NOS1 DAC receive 6moons Blue Moon Award !
** "Lonely at the very top" **
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 2 3 4 5 6 7 [8] 9 10
 on: January 31, 2016, 02:23:04 pm 
Started by michaeljeger - Last post by boleary
Michael, when you boot into your backup image, how much RAM shows up? (Though you probably know: Program Manager/System: to check RAM) I couldn't boot into any RAM OS the other day so I put my old W8 Disk in and booted, checked RAM and saw that only 12 gigs were being recognized. I was very worried that one of my 4 gig sticks had failed, or, worse, that I had a MB problem. I then removed and reseated all four RAM sticks and 16 gigs was recognized again. Have no clue what happened but all is working now.

 on: January 31, 2016, 02:16:53 pm 
Started by michaeljeger - Last post by PeterSt

Thank you for tall the answers.

Re-install boot-loader?

No no, that is actually fine. Just (still) leave all alone for now.

But just thinking ... yes
Since you can actually normally boot, I should be able to dive into your PC by means of Teamviewer, right ?

Best would be :
- Disconnect Internet (Ethernet) cable;
- Boot into TRIAL;
- Prevent Windows Updates (RicghtClick Stiop button in XXHE etc.;
- Connect Internet and install Teamviewer;
- Tell me about it by email (ID and Password).

From there we will proceed, which hopefully will not be too long-winded for you because it will require reboots to see whether things helped. Also notice that after each reboot you need to send the Teamviewer password again (it changes).

You can initiate that now if you want.
Meanwhile tell me whether it is correct that the longer part of copying the OS to RAM (the "2 minute" part) is indeed not started (so the part where you see that number increasing up to its at 13000). It can also be that it goes wrong after this 2 minute long process, but this is not what I expect. I need to know though, as I can't test this kind of thing through Teamviewer ...

Thanks !

 on: January 31, 2016, 01:42:00 pm 
Started by michaeljeger - Last post by michaeljeger
Hi Peter

I went back to to old bios version 1.5 but still the same problem.
At this point my only conclusion is that the Bios actually wrote something to the disk, since it happened right after reboot when bios update was done.

It is really strange, all other partitions boot fine just the RAM option seems broken.

Re-install boot-loader?

And yes as you are suggesting..... I boot from the Stop-button (Boot into).

I will keep looking but to be honest, I am a little concerned that I will not find a solution for this.

and yes, the repair options are all greyed out.

REgards, Michael

 on: January 31, 2016, 01:23:03 pm 
Started by michaeljeger - Last post by PeterSt
Hi Michael,

Regarding your question at the end :

Maybe but I can not imagine how. HOWEVER :
I recall that a few years ago I wrote something about an observation regarding this and multi-boot. It went something like "so stuff from the BIOS is stored on disk !". ... I did not even attempt to find this back (seems undoable), so who knows ...

It would be great if you can undo this, and even more great if you can copy the behavior so we can learn what actually is happening. But I don't expect you to deliberately be destructive. And so for this moment I can only hope you can get it going again.

Still it is really strange.

If you rightclick the Stop button in XXHighEnd and invoke the Boot Into (Menu), I suppose that none of the (RAM) Boots show a checkmark in the Repair column ? (if some do, please do not touch anything and tell me first, ok ?)


 on: January 31, 2016, 01:05:20 pm 
Started by michaeljeger - Last post by michaeljeger
Hi Peter
Regarding your questions:
1. I had the feeling the GFX Card is running too hot so I decided to give it shot updating the the latest bios.
2. No
3. Do not know any more
4. I will try to get to a older version
5. I did not try to repair anything so far. However, for some reason I had to again start from a backup image for 586.0 because it would not boot anymore, but that was for a different reason. The error basically came before the login screen with some error, that the system needs to reboot.
After reverting back to a backup image, I can boot 586.0 again.

One other thing..... before I did the firmware-upgrade, I was last booting 586.0 from RAM. Could it be related, that the RAM option is not working anymore?

Regards, Michael

 on: January 31, 2016, 10:19:42 am 
Started by michaeljeger - Last post by PeterSt
Hi Michael,

I just have been reading "Google" for the past 90 minutes, but I did not find anything useful.

I don't think that any firmware upgrade is touching a disk's contents and I thus also think that that did not happen, although the messages imply that easily. So ...

So at this moment it seems more likely that the firmware is flawed, which btw is still quite easy for ASRock and X99(M), as it seems (Google).

1. What is the reason that you updated the firmware in the first place ?

2. Did you apply anything which we generally put in the chapter of "Warez" ?

3. What is the firmware version you updated to and what is the version you you used prior to this (without the issue) ?

4. Can't you go back to that older version ?
Point is : when not and we need to try other things, chances are fair that we will be "destructive" and then nothing is going to work any more.

5. Regarding the latter : did you try to attempt any repair option yourself ? (don't !)

Please answer all the questions. Not answering them in full / correctly will virtually kill your system in the first place.

Best regards,

 on: January 31, 2016, 01:01:47 am 
Started by michaeljeger - Last post by AlainGr
Hi Michael,

"GrLdr" seems to relate to Linux "Grub Loader". It seems to have disappeared for an unknown reason.

Now what to do... Peter should help as soon as he will read this...



 on: January 31, 2016, 12:27:58 am 
Started by michaeljeger - Last post by michaeljeger

I booted from Base OS and the same problem occurred.

Thanks Michael

 on: January 31, 2016, 12:06:50 am 
Started by michaeljeger - Last post by acg
I don't know for sure, but you will probably need to boot into a base OS version first...

 on: January 30, 2016, 11:04:38 pm 
Started by michaeljeger - Last post by michaeljeger
So here is the deal.
Did an firmware upgrade to my X99M Asrocks MB.
After that, i cannot boot anymore into the Ramdrive.
All other boot options work, except for the RAM option.

I attached a screen shot of the error.

Not really sure what is going on here.

Regards, Michael

Pages: 1 2 3 4 5 6 7 [8] 9 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.275 seconds with 15 queries.