Random BLK SOD-sometimes 5/night

Turn off automatic restart on BSOD by typing "advanced system settings" in Start Menu, then go to Startup & Recovery settings and turn off the option there, then restart the PC. If you still get an instant reboot, then you most definitely have hardware failure, which will mean sending that sucker in for an RMA. If you have the option, it doesn't hurt to backup the whole disk image using something like Clonezilla so everything's completely restored on the new hardware.

koolkat77:
Ran boot-up /scannow 3 times consecutively. Each time I was told that "some corrupt files were found, but could not fix all of them." Looked at the CBS.log file and found three identical error lines (identical except for the timestamps):.

• 2012-09-23 19:44:12, Error CBS Failed to shred identity: Microsoft-Windows-InternetExplorer-LanguagePack [HRESULT = 0x80070057 - E_INVALIDARG]

Many other lines mention Failure to open items, for example: "Info ... Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]." So I expect this /scannow was not valid. The earlier one I ran, at least pointed to corrupt files--my guess is that the message "some corrupt files were found, but could not fix all of them." is just boilerplate issued whenever an error of any kind is returned. The command line I used was

• sfc /scannow /offbootdir=c: /offwindir=c:\windows

I mention this because the directions said that the drive letter was unlikely to be c:, but it was for my run. After reboot I performed another /scannow from cmd shell and found a line that seems to say that the stored system file was also corrupt:

• 2012-09-24 06:28:18, Info CSI 000000e6 [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\IME\IMESC5\DICTS"\[l:22{11}]"PINTLGB.IMD"; source file in store is also corrupted

I am attaching the CBS.log file, for whatever it might be worth. Would it be possible to get the correct files from my ASUS install-partition?
>> Hmm! I could download the DigitalRiver iso -- I have seen a tutorial on how to repair using the full windows disk. I do have the serial-number -- it was hidden under my laptop with the label "Serial Number" (Thanks, gregrocker)

Vir Gnarus: I see your post. Thanks, I will try it.

Vir Gnarus: Yes, I do have [x](Write an Event to the System Log) checked and [](Automatically Restart) unchecked. This (I believe) would give me a BLU-SOD, but I do not get that (just an instant Black screen and a reboot), and it appears nothing is written to the Event Log until -after- reboot, it is a message that my system was not shut down cleanly, followed by a message that the preceding reboot was "unexpected."
.
But I don't get an instant reboot. It takes a day, an hour, or sometimes only a few minutes--and can't be pinned down to a particular application--I might be in Word, reading a pdf file, or browsing with Firefox, Chrome or IE. Or, yes, writing a post here.

That's the thing. You are not getting BSODs, you are getting instant restarts triggered by your hardware. If you were getting BSODs, your system would freeze and the appropriate blue screen would appear, regardless if it managed to create a crashdump/eventlog entry or not. This is not involved with any software or Windows, this is a hardware malfunction.

There's really no point trying to ascertain what hardware it is when you have the system under warranty with an OEM vendor. Your best bet is to call them up and force them (yet do so respectfully) to do a replacement of the whole system, telling them that your warranty is about to expire (is it?) and if they keep dodging the issue by trying to replace parts you may over extend this beyond the warranty's expiration date and you'll just be left with a bad system. You will need to be very aggressive with them as they will try to evade replacing the whole system. Again, make sure to backup with Clonezilla so you keep everything exactly as is so you can return it to its original state once you get the new replacement.

I see you ran memtest86 for 16 passes, but have you swapped around RAM sticks checking the slots for debris, tried different configurations?

Have you run HD Diagnostic extended CD scan followed by Disk Check from the installer/Repair CD Command Line? If necessary run Check File System from Partition Wizard.

Have you tried System Restore from installer System Recovery Options or System Repair Disk ?

The problems with running Disk Check and System Restore from Windows point to a major Win7 problem to be resolved to know if it's causing your crashes.

Sometimes stray boot sector code can also cause anomalous behavior which would still fall into the software realm. It's enough of a possibility I'd want a baseline perfect install on wiped HD to know for sure.

Did I mention that I am using an external USB mouse? I sure thought I did--but that may have been another forum because I see that I did not. So sorry, koolkat77, gregrocker and Vir Gnarus.

If I take away the USB mouse or click [x] disable touchpad when an external mouse is plugged in, the restarts stop. (Well I got one but that was early on, several days ago, and with the mouse, not with the touchpad-only--and none since). This doesn't prove it has been fixed, but I unchecked that box and got another reset within 1 1/2 hours.

I have other problems with the system, but I may live with them and not ship it to ASUS (Hooray). Thanks to the diagnostics you guys put me through I have more confidence in the unit. You three have been very generous with your time and expertise. This is a great forum. I learned a lot that will help with future problems.

With crossed fingers, I mark it solved.

-Cab-

Looks like I jumped the gun--hoping it was solved--that seems to have been wishful thinking. Not having both the mouse and the touchpad working made a lot of difference, but even now I get the BLK-SOD about once every day or two, instead of 5 times a day. I've tried touchpad alone and mouse with touchpad disabled, still get some BLK-SOD's. So it may be driver-related. I've checked all the drivers, touchpad and USB, they seem to be the "latest."

Shipping it to ASUS? I already have the RMA, but I really can't afford to be without it for a month. But unless someone has some suggestions to try,
I'll have to do that. gregrocker if memtest86 passes as-is, is there a need to move the memory around?

I will say and say again, black screen crashes and instant restarts without blue screens are caused by hardware, not software. Drivers cannot be involved here, especially since we've already done a number on replacing them. If they were involved, they would cause lockups and blue screens, but not instant restarts. Driver changes can sometimes alleviate symptoms a bit by causing alterations to hardware activity, but it does not resolve the underlying issue.

It looks like your only option will be the RMA at this point in time, or to somehow get a tech to come over (though I believe that's a business-only option). Your other option is to start buying separate replacement parts for your system and installing the replacements yourself, starting with the motherboard. This, however, is not a preferred venture, but it is an option.

Thanks, Vin Gnarus. I am going to do an original restore today just to exhaust all possible remedies.