0x7B error, same time but not all the time.

[J-Money]

I recently put in a new SSD and about half or one third of the time I get an 0x7B blue screen error only when Windows is booting right at the screen where the 4 windows fly together. Doesn't happen any other time.


I can't find anything on why it would only happen so randomly.


I reinstalled Windows three times, same thing every time.
I tried Startup repair, no go on that. I get "BadDriver" as the reason though for it not starting.
I can't see a dump file of it because it happens to early for one to generate.


I'm guessing one of two things:

1. SSD faulty
2. Motherboard isn't reliable with SSD.


Specs for it are:

SSD = Crucial RealSSD C300 64GB (newest firmware)
Motherboard = Abit IP35 Pro (running SSD in IDE mode)


Any ideas?

 

[Veliko]

Try your old hard drive and see if it still does it. Got any other RAM to swap out?

 

[Burner27]

I recently put in a new SSD and about half or one third of the time I get an 0x7B blue screen error only when Windows is booting right at the screen where the 4 windows fly together. Doesn't happen any other time.


I can't find anything on why it would only happen so randomly.


I reinstalled Windows three times, same thing every time.
I tried Startup repair, no go on that. I get "BadDriver" as the reason though for it not starting.
I can't see a dump file of it because it happens to early for one to generate.


I'm guessing one of two things:

1. SSD faulty
2. Motherboard isn't reliable with SSD.


Specs for it are:

SSD = Crucial RealSSD C300 64GB (newest firmware)
Motherboard = Abit IP35 Pro (running SSD in IDE mode)


Any ideas?

Can you run the Debugging Tools for Windows on the MiniDump file to see what the error is? Here's a link to what you'll need to install:


http://msdn.microsoft.com/en-us/windows/hardware/gg463009

Copy the minidump file to your desktop and run the debugging tool against it from there.

 

[Mark R]

Stop 7B means that Windows couldn't complete booting because it couldn't find the boot files. Debugging this error is a pain - as it occurs so early in the boot process that logs are not saved, and dump files not created.

The commonest cause of this, is to have 2 drives in the computer which have had windows installed. Because Windows randomises driver loading - this means that every few boots, windows changes the order in which it searches drives for the boot files.

So, if you upgrade to an SSD, and keep your old drive installed - one thing that can happen is that Windows will boot under BIOS control. Then, about when the windows coming together animation plays, windows switches to its owner drivers to finish loading. If you have an old installation, under some circumstances Windows can get confused and try to finish booting from the wrong drive - this causes a Stop 7B error.

To check if this is the problem - load up 'disk management' under 'computer management'. Then look to see the settings of each drive (e.g. boot, page file, active, system, etc.) . Only one drive should be labelled as 'boot'. If 2 drives are marked 'boot', then you can get this problem.

Fixing this is a pain, as Windows doesn't have a method of making a drive 'unbootable' without reformatting it. This can be done with a linux live CD/USB.

If you think this is your problem, then I'll explain how to mark the drive unbootable.

 

[J-Money]

I checked and only the SSD is showing as boot, I also tried it by itself and it still did it randomly.

My other hard drive (Seagate 750GB) does not ever have this issue so I'm suspecting some sort of intermittent malfunction in the SSD.

I'm still within the 30 days on Newegg RMA policy so I'll RMA it and get a new one, if the problem persists at least I know for sure it wasn't the hard drive.

Thanks a lot for the help.