BleepingComputer.com: Bluescreen on HD format / Error Check

I recently copied my HD's content to an SSD. Setup boot from the new drive w/o a hitch. Decided to format my old HD, and boom! Blue screen.

After restart, windows wanted to search for solutions to the problem: this caused my computer to freeze up and bluescreen again.

I'm not sure what to make of it ... i suspected the HD had some issues, which is why I got the SSD. I also haven't ruled out that it could be my controller (Marvel)

I've attached the text from bluescreenview on both .dmp files.

Specs:

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
HDD - Seagate Barracude ST31000524AS 1TB 7200 RPM SATA III

This post has been edited by hamluis: 11 February 2012 - 08:24 AM
Reason for edit: Merged topics.

We need to know more about your BSODs...

Download BlueScreenView (in Zip file)

No installation required.

Unzip downloaded file and double click on BlueScreenView.exe file to run the program and When scanning is done, go to Edit > Select All.

Then go to File > Save Selected Items, and save the report as BSOD.txt.

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

Compliments of Broni

For some reason, the .dmp files are gone. All I did since the post was reboot... ?!?

I could probably recreate by attempting a format again.

I found this in the system event log:

Source: Ntfs - The system failed to flush data to the transaction log. Corruption may occur.

Source: BugCheck - The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003d (0xfffff88015440f90, 0x0000000000000000, 0x0000000000000000, 0xfffff8800112d78e). A dump was saved in: C:\Windows\Minidump\012012-8798-01.dmp. Report Id: 012012-8798-01.
&
"":""- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003d (0xfffff880143bff90, 0x0000000000000000, 0x0000000000000000, 0xfffff8800113b78e). A dump was saved in: C:\Windows\Minidump\012012-9110-01.dmp. Report Id: 012012-9110-01.

Weird that it didnt save the data do you have it set to automatically restart upon BSOD in the System Settings?

Just happened again ... seemingly randomly. Is the attached what you need?

aaand it just happened again right after i posted that. I've attached this error as well.

I just physically unplugged the HDD from my computer to see if the error stops occuring. At least then I know the issue is isolated to that drive.

and cryptodan, why do I have this wardning in my system event log?

Name resolution for the name www.cryptodan.com timed out after none of the configured DNS servers responded.

Please zip up the minidumps and attach the resultant zip file to your next reply so I can have a closer look. There's a chance I might get some more useful info from them.

• Navigate to C:\Windows\Minidump <<< folder
  
• Click on the first minidump file to select it.
  
• Hold down the <Shift> key, and click on the last minidump file to select all of the files.
  
• Release the <Shift> key.
  
• Now, right-click on any one of the selected files > Send to ... > Compressed (zipped) Folder.
  The zip file will be located in the same place (the Minidump folder).
  
• Attach the zip file to your next reply.
  When you click on Add Reply, you will see the facility to attach a file just below the box where you type your message.

I would try updating the Marvell Chipset Drivers for your Marvell Hard Disk Controller.

http://www.asus.com/Motherboards/Intel_Socket_1155/P8Z68V_PRO/#download Select the appropriate OS.

Attached are zips of the .dmp files.

I tried downloading and updating the marvel drivers just now. rebooting...

STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED

Quote

Ref: http://www.carrona.org/bsodindx.html#0x0000003D

Quote

The only possible issue that stands out for me when looking at your minidumps is what appears to be overclocking of the CPU. I suggest that if you continue to have a problem after updating all drivers, then you return the system to default settings and continue testing.

Quote

====================================
BSOD BUGCHECK SUMMARY
...............................................................
Loading Dump File [C:\CactusIsland\Andrew Fiedler_BC\012112-8798-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 16:52:09.990 2012 (UTC + 11:00)
System Uptime: 0 days 0:58:08.848
Unable to load image mv91xx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3D
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff800`00b9bf60 00000000`00000000 00000000`00000000 fffff880`010c578e
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID: "Intel® Core™ i7-2600K CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: 3502
...............................................................
Loading Dump File [C:\CactusIsland\Andrew Fiedler_BC\012112-6630-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 21 17:01:23.635 2012 (UTC + 11:00)
System Uptime: 0 days 0:05:08.494
Unable to load image mv91xx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+3178e )
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3D
PROCESS_NAME: taskhost.exe
FAILURE_BUCKET_ID: X64_0x3D_mv91xx+3178e
Bugcheck code 0000003D
Arguments fffff880`1499c2e0 00000000`00000000 00000000`00000000 fffff880`0103178e
BiosVersion = 0402
BiosReleaseDate = 11/16/2011
CPUID: "Intel® Core™ i7-2600K CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: 3502
...............................................................

This post has been edited by AustrAlien: 21 January 2012 - 05:47 AM

huh ... well I'm not overclocking the CPU at all. I guess my motherboard could be doing it based on some advanced setting? I certainly haven't changed any clock speeds anywhere though. Furthermore, the error has not happened since I unplugged the HDD (running only on my SSD).

Before I got the SSD, I had not seen the error mentioned above, however, I had already been getting read errors reported in my system event manager from mv91xx. Also, I had once received a Kernal_data_inpage_error with code 0x0000007A as well as a generic Stop 0x000000F4. I no longer see any of those symptoms with my HDD unplugged. Does that mean anything?

I don't understand why the error would happen when I try to format the drive ... and doesn't appear when I have the drive unplugged.

Andrew Fiedler, on 21 January 2012 - 11:08 AM, said:

I thought that might be the case.

I suspect a problem with the Seagate Barracuda ST31000524AS 1TB HDD and suggest that you test it using SeaTools run from a bootable CD.

Please download SeaTools for DOS (CD) from Seagate's SeaTools for DOS web page

or use the following direct download link to download the latest version of SeaTools for DOS:
Download SeaTools for DOS ISO Image

The downloaded file name is SeaToolsDOS223ALL.ISO

Burn the downloaded .ISO image to a CD using the appropriate burning software.

If you do not already have a suitable burning program for writing .ISO images to disc ...

• Download and install ImgBurn.
  Ensure that you UN-check the box agreeing to install the Ask toolbar during the installation.
  
• Place a new (blank) CD disc in the drive tray.
  
• Choose Write image file to disc.
  
  • Under Source, click on the Browse button: Navigate to and select the .ISO file that you wish to burn.
    
  • Place a check-mark in the box beside Verify.
  
  
• Click
  
  When the CD has been burned and verified as successful, it will be bootable.

Boot from the CD.

(You may need to access the BIOS Setup Menu or the Boot Menu and change the boot order to enable booting from CD before hard drive.)


• From Basic tests on the Main Menu, run the Short test and then the Long test.
  
  (The long test will take some considerable time to complete.)
  The results will be shown as either a PASS or FAIL.
  There is a chance that during the Long test, you may be offered the opportunity to attempt repairs on the hard drive:
  
  • If so, go ahead and attempt to do so, but ONLY after backing up all important personal files.

Note: You may wish to view the following ...

• Learn more about SeaTools for DOS. (view a 24 page pdf document)
  
• See the tutorial on the usage of SeaTools for DOS.

Please let us know the results of the tests.

This post has been edited by AustrAlien: 21 January 2012 - 11:35 AM

Personally, I am strongly leaning on the marvel controller being the source of the problems here, since I had a blue screen with ONLY the SSD plugged in. (attached BSOD from that)

I ran the fix all test on seatools, when I booted from the CD, it couldn't find any drives, so I did it from windows safe mode. The results were weird... there was an error reported, and then PASS shown, but the log said fail as well as pass on the same test. Not sure what to make of it. (see sealog and seaerror)

After some google searching and digging, I found the most up to date marvel driver from www.station-drivers.com. I uninstalled the old driver in safe mode, rebooted to be sure it was gone, then re-installed the up-to-date one. Crossing my fingers that it will fix the issues, but still interested to see your input on the attached crash with only my SSD plugged in, and the seatools logs... I suppose the HDD could certainly still be a baddie.

Interesting stuff. Please leave the Seagate HDD disconnected while we continue to trouble-shoot the Windows/system/SSD HDD issue, with the crash dumps blaming the Marvell driver (which may turn out to be a red herring).

Please zip up and attach any minidumps rather than post a BlueScreenView report. Looking at the minidump itself is likely to provide more useful information (if there is any to be had).