BSOD with all parameters

johnyb98 · 13 Jan 2016

Good evening.

I have a Windows 7 system, that cannot reach desktop.
After the Windows 7 flag is created from the four colors coming from depth, then a blank black screen as it is normal, and then, as I wait for the desktop, here comes the hot restart. And this cycle restart again, and again, and again, etc. etc.

System has two identical WD SATA 500GB each, in a RAID 1 row (mirroring).

Have tried from F8 make the repair:no result
Have tried chkdsk /r:no result

Error on BSOD is:
UNMOUNTABLE_BOOT_VOLUME
0x000000ED (0xFFFFFA8004 98DCD0, 0xFFFFFFFFC00000C0, 0x0000000000000000, 0x0000000000000000)

Could you please help me?

Thank you!

BorisTheAnimal · 13 Jan 2016

Hi there johny.

I would recommend that you run memtest86+:
RAM - Test with Memtest86+

It seems that it might help you resolve the issue!

*Update

Found this:

AMI BIOS:
1 beep - System boot successfull
*1beep - Refresh failure - (NO VIDEO) memory refresh failure (bad memory)
2 beeps - Parity error - bad memory

So you will definitely have to check the ram.

Cheerio /Boris :)

johnyb98 · 14 Jan 2016

You are totally right, Boris. In this desktop, the last six months, many times NO VIDEO in screen at start up. So, tried with turn on and off screen, to have image. I thought of all possibilities:
screen itself
screen cable
VGA to DVI adapter
VGA card

But never thought of RAM. If I have understood well enough, maybe a failure RAM is the NO VIDEO result. Right?

So, now I have started checking RAM. And I will upload results when finish.
Something strange, now. Something that I have never seen in other Memtest86+ checking I have made before is as follows:when Memtest86+ starts, I hear two short beeps:beep-beep. But, no errors in error column. Maybe because it has two modules A-DATA and two Transcened. Each one of 1024MB. So, 4GB of total RAM.
What about all that?

Thanks!

**Pauly** · 14 Jan 2016

An 0xED BSOD as you mention is an unmountable boot volume which can be very problematic to diagnose as you cannot access windows to retrieve dump/diagnostic files, one of our top BSOD guys has done a thread for just this type of scenario have a read through it will give you some ideas of things you can do/things to try but as you are running a raid setup that will complicate things

Troubleshooting stop 0x7B and stop 0xED.

BorisTheAnimal · 14 Jan 2016

Well johny just like Pauly said because of that you cannot get into Windows will make solving this problem more tedious than normally.

Would you be able to get some information on your hardware? Like if we can get the motherboard model we can check the QVL if any of your sticks are actually supported, if either of them aren't well then.

johnyb98 · 14 Jan 2016

Well, motherboard is a GIGABYTE GA-890XA-UD3.

BorisTheAnimal · 14 Jan 2016

johnyb98 said:

Well, motherboard is a GIGABYTE GA-890XA-UD3.

Have you tried taking out both Transcend sticks and vice versa and try booting?

johnyb98 · 14 Jan 2016

No. I haven't. Do you suggest so? Do you believe this could solve 0xED problem?

I believe that, even if Transcened or A-DATA RAM is defective, even by letting on motherboard only healthy modules, is too late. Because now, some or many necessary Windows boot files are destroyed. Something that will not be fixed with just healthy modules on motherboard.

What do you think about that?

BorisTheAnimal · 14 Jan 2016

Well I would then suggest that you do option number 6 in the thread that Pauly mentioned.

My thinking of the memory was just a thought.

Like I said without anything to go on this problem could be caused by really whatever.

**Pauly** · 15 Jan 2016

I would start with a HDD diagnostic check using Seagate seatools software or similar, you can make a bootable flash drive to run it off so windows will not come into it.
If drive checks out ok then you can start looking at boot files etc