Solved BSOD first thing then OK on 2nd boot up

[pooksahib]

Hello. Once again, I find myself seeking the assistance of the good folks here.

Kind of an odd one, I think - the first bootup of the day goes as normal and I start surfing/working with no problem. Then, after about 5 mins, the buffering symbol appears, keyboard/mouse of no use to me and open windows/desktop icons start to disappear before the BSOD kicks in. It can't be because of something I've done as it's happened when I've been away from my desk.

I then 'start Windows normally' and, as is the case right now, carry on computing with no issues.

The log is attached and I thank most sincerely anyone prepared to have a look.

 

[Layback Bear]

Could you also add to your system specs the power supply and what security programs you use? Some times this information is helpful.

 

[pooksahib]

Have done. Thanks.

This is my 3rd time at the PC today and my 3rd BSOD. Same story, going fine for about 5 mins then things start disappearing from the screen prior to the BSOD. I've attached the logs of the 2nd and 3rd crashes.

Kind regards.

 

[pooksahib]

I've just had 3 'no problem' days which was great. The latest development, however, is that I'm getting BSOD IMMEDIATELY on powerup (not even the welcome screen). But it's not the full BSOD - the text only fills half the screen. Like before, though, all is well after the reboot. Latest log attached, my thanks to anyone prepared to have a look.

 

[essenbe]

Hello, pooksahib. I will try to assist you with this. I have briefly looked at your dump files. The last dump file you have was on 3/09. Could you check and make sure your system is configured for small memory dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

What I am getting from your dump file is very consistent. They are all error codes F4 which, in my experience is a storage error.

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007932b30, Terminating object
Arg3: fffffa8007932e10, Process image file name
Arg4: fffff80003193130, Explanatory message (ascii)

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory [COLOR=red]because of an I/O error status[/COLOR] of 0x%x

If you would please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

I would also like you to run both the short and long test on all of your Mechanical hard drives. Especially the 1 TB Samsung drive. I would not run the test on your SSD. Please run Seatools for DOS
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

Please let me know the results of those tests.

 

[pooksahib]

Hello essenbe. I think you've nailed it although it wasn't the Samsung that needed the attention. Scannow insisted everything was OK but Seatools failed one of the HDDs. Fortunately, it was the Seagate so I ran 'Fix All Now' and, three hours later, it 'passed'. The log said nothing more than that so I presume it repaired a few bad sectors during those three hours.


I've since booted up a few times with no problems whatsoever which means you have my sincere thanks. All the best to you.

 

[essenbe]

You're very welcome. But, I would suggest you keep a close eye on that drive.