Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD first thing then OK on 2nd boot up

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.

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.

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.

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. Dump Files - Configure Windows to Create on BSOD

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.

Code:

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)

Code:

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status 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 SeaTools for DOS and Windows - How to Use

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.

BSOD first thing then OK on 2nd boot up

BSOD 3B constantly when doing simple thing.Hello. I get BSOD'd everyday, but it happens most of the time when I watch a Youtube video or downloading a game from Steam, or just downloading in general I suppose. The stop code 3B pops up maybe 20 times a day, sometimes I can go a day without getting a crash. Also, I do receive other BSOD stop...

BSOD Help and Support

Some thing weid when boot up ..Hello .
All of the certain when i start the windows , it goes to the boot page and ask if i want to start windows 7 ...? as if i have dual boot , which i don't.
How do i set it boot up directly without asking ...?
Thanks in advance .

General Discussion

BSOD please help. about to crush this thingstarted getting memory access violations in starcraft 2. re installed the OS from a clean version of win 7 ultimate 64 upgrade. format disk, clean install. started the computer and blue screen. finaly loaded and ran for awhile and BSOD. tested ram and it tested with 2 errors. replaced ram. still...

BSOD Help and Support

BSOD doing any thing..Im getting BSOD all the time iv reinstalled windows 7 cleared all my hdd changed Ram nothing works..
So here i am looking for skilled help :)
Is Windows 7 . . .
- x64
- the original installed OS on the system? no
- an OEM or full retail version? Retail
- What is the age of system...

BSOD Help and Support

weird thing with my graphics on boot upi have a weird thing happening. if my crt monitor is turned off when i boot my pc, when i turn it on i hear windows do its little "da ding" and the picture i have is at 800x600. when i right click the desktop as soon as i click the nvidia control panel it "da dings" again and goes to the display it...

Graphic Cards

OMG! Microsoft created a secret Boot-Camp-Like thing!From TechRepublic post " Five Super-Secret features in Windows 7 "
"...Apple opened the door to more users - especially IT pros - in recent years by building Boot Camp into its Macintosh computers to allow them to run Windows along side Mac OS X in a dual-boot configuration. Not to be...