BleepingComputer.com: Bluescreen on HD format / Error Check

If I get any more bluescreens, I'll attach the file. Here's what has been going on since last post:


Did a low level format of the seagate 1TB drive. Partitioned and formatted drive in windows (no errors)
scanned seagate drive for errors, none found
scanned C drive with malewarebytes (nothing found)

No more bluescreens, but one odd thing happened...
I had left the aforementioned scans running overnight. in the morning, when I came to my computer, the explorer shell was up, but I couldn't do anything. start menu was empty, my computer blank, no programs would open from anywhere. when I tried Ctrl+alt+del and saw this message:
"Failure to display security & logon options when Ctrl+alt+del was pressed..."

after reboot, everything seems fine .... but I'm at a total loss as to why that happened. A few google searches returned no explanations.

So I haven't seen the "blank windows" issue again, but I'm having an issue with my external drive. My most recent windows backup failed (and it had not previously). I attempted to write about 6gb of files to it, and midway through, the drive dissapeared from mycomputer and the move froze. When I tried to run a check disk on the external drive, it freezes midway through.

I don't think the external drive is failing, as I've had it several years and it has had 0 issues and still works on my laptop without a hitch. My best guess is a driver conflict ... but I'm not sure how to confirm or disconfirm that theory, and not sure what else could be wrong.

All of the disk issues make me think this is either freak driver issues or a hardware issue with my board's drive controllers.

That freeze could mean that it is fixing something I would let the chkdsk go through to completion.

So I got an RMA on the seagate drive .... just suspected a lot of issues.

However, I just had the "blank windows" error again. This time, with a bluescreen. We can consider this issue closed, as I believe it was a combination of the seagate drive being bad as well as corrupted raid controller driver files.

I will open a new topic for the other issue, which I believe is unrelated to hard drive or controller issues.

So I'd seen this happen once before ... the explorer shell stayed open, but none of the icons did anything, start menu totally empty, and Ctrl+Alt+Del produces an error and fails to load. This time, the computer actually BSOD'd.

Attached is the BSOD. Specs below. Let me know if you need other information.

MOBO - Asus P8Z68-V Pro/Gen3
CPU - Intel Core i7-2600K
RAM - 32GB G.Skill Ripjaws X Series (4X 8GB)
GPU - EVGA Geforce GTX 580 (Fermi) 3GB 384-bit GDDR5
PSU - Corsair Enthusiast Series TX850 V2 850W
SSD - Crucial M4 256GB SATA III

This post has been edited by Andrew Fiedler: 26 January 2012 - 09:59 PM

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt, copy all content and paste it into your next reply.

Louis

See attachment. In the past I was told to upload the entire .dmp file in a zip ... sorry if it was not what you were looking for.

No need to apologize for providing data .

A few years ago, there were no tools which simplified trying to make heads/tails out of BSOD error messages and dump files were the only approach that one could take. Fortunately, that has changed and what was a rather convoluted process (in the eyes of many users) can now be simplified by using tools such as BlueScreenView. Troubleshooting BSODs still is not an exact science, but now it's easier to see where Windows is throwing a fit...and (sometimes) why .

I've pasted the content from your attachment below...makes it easier for everyone here to see the content, which is why we ask that such be pasted into the next post.

==================================================
Dump File : 012612-5725-01.dmp
Crash Time : 1/26/2012 8:52:25 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`1c56e700
Parameter 3 : fffffa80`1c56e9e0
Parameter 4 : fffff800`033828b0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012612-5725-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 303,743
==================================================

Generally...a single BSOD error message may not reveal anything. No pattern can be discerned from a single message and all BSOD errors are somewhat general in terms of identifying possible causes of the problem.

From http://www.aumha.org/a/stop.htm :

"0x000000F4: CRITICAL_OBJECT_TERMINATION
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message."

You say that you had a BSOD before...but there is no evidence of it in your submission. Do you have any idea why that may be? Are you running software which removes these files?

Are you overclockiing the system?

What suggestions/explanations were proposed by whomever advised you regarding your prior BSOD?

We don't have a lot to go on here, IMO.

Louis

I have not had any more marvel driver errors .... I RMA'd the seagate drive and scanned it with several different drive scanning tools and it appears to be clean.

I am now having a different bluescreen ... makes me think this could be related to my motherboard.

I created a new thread for the new bluescreen, if it should be contained within this thread, let me know and I can close that one and attach the information here.

Mod Edit: Merged topics ~ Hamluis.

This post has been edited by hamluis: 11 February 2012 - 08:28 AM

For reference, I had a previous thread on these forums, but the error message seemed like a separate occurrence so I started a new thread.
Mod Edit: Merged topics ~ Hamluis.

In any case, I've been seeing these same "blank windows" crashes periodically. Here are the 3 latest ones, starting with the oldest. They seem completely random... one when I was browsing the web, one playing a game, and one I just left my computer for a period of time with nothing but background programs running.

==================================================
Dump File : 020412-5959-01.dmp
Crash Time : 2/4/2012 10:19:00 AM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`1c775850
Parameter 3 : fffffa80`1c775b30
Parameter 4 : fffff800`033db8b0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020412-5959-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 304,231
==================================================


==================================================
Dump File : 020712-6723-01.dmp
Crash Time : 2/7/2012 9:53:47 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`1c508b30
Parameter 3 : fffffa80`1c508e10
Parameter 4 : fffff800`033e18b0
Caused By Driver : netbios.sys
Caused By Address : netbios.sys+8d0f550
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020712-6723-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 303,783
==================================================

==================================================
Dump File : 021012-6723-01.dmp
Crash Time : 2/10/2012 9:51:45 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`1c68cb30
Parameter 3 : fffffa80`1c68ce10
Parameter 4 : fffff800`033928b0
Caused By Driver : Null.SYS
Caused By Address : Null.SYS+9512550
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021012-6723-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 303,783
==================================================

This post has been edited by hamluis: 11 February 2012 - 08:29 AM

Just had another bluescreen. I am wondering if this has something to do with how my system is configured to work with my SSD? I had a list of things to do to "prep" my system for the drive, and am curious if any of it could be having an impact. Here's the list:

• Upgrade Firmware
  
• checked trim settings w/ fsutil
  
• update chipset drivers
  
• disable defrag
  
• pagefile tweaks (i've tried with it off, small, or system managed still have the crashes)
  
• disable superfetch
  
• turn off prefetch/bootfetch
  
• disable most logging in windows performance manager (except Application, Security, System, Security Essentials)

Anyway, pasted the bluescreenview text below. Also attached the .dmp file if that helps at all.

The sooner I can get to the root of this the better, as I want to replace any faulty components while they are under warranty.


==================================================
Dump File : 021412-7129-01.dmp
Crash Time : 2/14/2012 8:39:18 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`1ca8e720
Parameter 3 : fffffa80`1ca8ea00
Parameter 4 : fffff800`0339a8b0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\021412-7129-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 287,600
==================================================

Just wanted to come back and thank everyone for their input. Also, it turns out the motherboard I have has 2 6GB sata ports that are on an Intel controller. Switching my drives over to those off the Marvell controller solved all of the drive errors I had been getting.

After a call to ASUS, I found out that ALL their board have buggy Marvell controllers. Apparently, driver updates cannot solve it: the Marvell controllers are just buggy. I put in for an RMA, but highly doubt I'll get a board with a bug free Marvell controller. I dug up plenty of other people complaining of issues with the controller as well on other sites.

Replacing the board might be more trouble than its worth, if I may just get another buggy one... but its worth a try. At any rate, the Intel controller seems to work just fine.

I believe that all the issues I was having were related to problems with the on-board Marvell controller, so case closed here (haven't had even 1 BSOD since switching to the Intel ports.)

thanks for posting back the issue.

Thanks for reporting your findings. Using a Marvel controller with an SSD is a no-no: There are many reports of this issue, as you say.

Good luck.