BSOD 7A and other crashes.

sharf224 · 06 Apr 2014

Hi all,

I've been having this issue for a while and thought I had fixed it, but apparently not.

To start out, I've attached the logs generated by DM log collector, though any dump files will be old and obsolete. My computer has been freezing more often than blue screening, and when it does blue screen, it's a 7A, and it never actually writes the dump file (I have set it to do it), for some reason this crash prevents it from writing to the drive.

Following this blue screen, my bios does not detect my OS drive (SSD) and I have to reboot several times to get it to detect it. I have tried switching the sata port/cable and we'll see if that fixes it.

Previously, I had a card read go bad and that was causing the blue screens. I removed it and everything was fine for a few weeks and now it's back. I have run chkdsk without any errors.

I do not have any info of the latest blue screen, as it usually sits for a while and then reboots itself without writing anything. If I catch it again, I'll take a picture of it.

If anyone can find any obvious problems in these logs to set me in the right direction I'd appreciate it.

koolkat77 · 06 Apr 2014

Is the firmware for your SSD up to date?

sharf224 · 07 Apr 2014

It is out of date, but that's a risky upgrade I'd like to avoid if it's not a likely cause.

Arc · 07 Apr 2014

sharf224 said:

It is out of date, but that's a risky upgrade I'd like to avoid if it's not a likely cause.

Not getting any stop 0x7A crash dump in your zip. There are stop 0x3B etc. But, here is a standard stop ox7A output .....

Code:

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 8dd047f8, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000056, error status (normally i/o status code)
Arg3: 2d113864, current process (virtual address for lock type 3, or PTE)
Arg4: 902f90ba, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Had I been in your place, I would not have expressed any doubt to any suggestion given by koolkat77, because we are sharing the board over a long time.

Until you update the SSD firmware, stop 0x7A troubleshooting cannot be started.

sharf224 · 07 Apr 2014

As I said in my initial post, there are no new stop codes because everytime there is a stop code it never "performs memory dump" etc. It just blue screens, locks at that for a few minutes, then reboots without creating a dump file. Yes I have also checked all the settings, it is supposed to be writing a dump file.

If something happened during the firmware update and the drive was corrupt and I had to re-install the OS I would have major problems, I have too many deadlines coming up for which I need my computer. Perhaps this weekend I can try it.

I also never expressed doubt in his suggestion. The firmware is out of date and people have had issues with corsair's SSDs before. My doubt is in the fact that if I get a power blink or something during the firmware update I am in big trouble.

Arc · 07 Apr 2014

We cannot do anything more until and unless the SSD firmware is up-to-date.

sharf224 · 23 Apr 2014

Alright, I've updated the firmware, it still blue screened.

It still had the same problem, it would blue screen, but would not write the dump file. So I took some pictures of it with my phone.

Also, one of the last times it crashed, a running program I had open just closed, and all of my shortcuts stopped working, my start menu showed no installed programs and nothing worked for a few seconds until it blue screened. So this leads me to believe it is a failing drive/cable/mother board.

Arc · 23 Apr 2014

Reseat the sata and power.

Also change the SATA cables. Apply them on the other unused SATA ports on the motherboard.

If it still BSODs, you need to change the SSD.

Edit: Post a screenshot of the SSD using http://crystalmark.info/software/Cry...o/index-e.html

sharf224 · 23 Apr 2014

I already did that pre-firmware update but I'll try it again.

Arc · 23 Apr 2014

sharf224 said:

I already did that pre-firmware update but I'll try it again.

If you have already done it, one more try may not provide anything better.

Try to get a replacement from the vendor, if you can.