BSOD on desktop

[nick91900]

del

 

[Arc]

Hello nick91900.

The zip you uploaded does not contain any crash dump. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Follow it manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump.

Post it on the next system crash. Aslo upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

A stop 0xF4 is a storage related bugcheck.

1. Update your SSD's Firmware (skip it, if it is not a SSD)
2. Re-seat the sata and power.
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results.

 

[nick91900]

Just got another blue screen. Different stop this time.

Made sure I got the right dump now.


EDIT
I pulled the HD out and took a look at the bottom. The silver piece in the center looks damaged. I was scratched looking...like it was spinning and something brushed against it. I have a laptop and it should be pretty protected. The only way I can see that happening is if the area to the right of the track pad was pressed in really hard. I'll include a pic

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  [COLOR=Red]Typically caused by
a bad block in the paging file or [B]disk controller error[/B]. [/COLOR]Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa80072d17c8, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff800036c60cc to fffff800036d1fc0

STACK_TEXT:  
fffff880`03508818 fffff800`036c60cc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`072d17c8 : nt!KeBugCheckEx
fffff880`03508820 fffff800`036bafc7 : fffffa80`072d1760 00000000`c000009d 00000000`00000000 fffffa80`072d17f8 : nt! ?? ::FNODOBFM::`string'+0x50040
fffff880`035088e0 fffff800`036c4a37 : fffffa80`0670b510 fffffa80`0670b560 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03508910 fffff800`036c7c3d : fffffa80`0670b510 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`03508990 fffff800`036d44da : 00000000`00000000 00000000`00000000 00000103`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x3dd
fffff880`03508a20 fffff800`0365fa5f : fffffa80`00000002 fffff880`03508d20 fffffa80`00000001 00000000`00000013 : nt!KeWaitForMultipleObjects+0x272
fffff880`03508ce0 fffff800`03968e5a : fffffa80`0670b510 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03508d40 fffff800`036c2d26 : fffff880`03164180 fffffa80`0670b510 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03508d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+50040
fffff800`036c60cc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+50040

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50040

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50040

Followup: MachineOwner
---------

First let me know .... is the HDD properly connected? And, is it physically damaged for sure?

 

[Petey7]

I suggest using Seatools as Arc recommended. If you do not have a blank cd (which a lot of people don't buy any more) then you can use the Seatools for Windows. You can also use the free trial of HD Tune. I find the HD Tune does better in terms of telling you exactly what the problem is. It sounds to me, based on what you said about your music suddenly stop playing, that you might have a number of bad sectors, resulting in files becoming corrupted. It might be time to replace the hard drive.

 

[richnrockville]

FWIW: Steve Gibson's program spinwrite has saved many a hard disk and the critical data on it.
Not cheap but well worth it if your data is critical.   Home of Gibson Research Corporation   is their url.


Rich

 

[nick91900]

del

 

[Britton30]

I haven't used it for some time but Sea Tools used to offer to "fix" a bad drive after the long scan foe Seagate drives.

 

[nick91900]

del

 

[Britton30]

You'll first have to get w7 on the new drive. While you still can download the network drivers and save to a USB stick, get one or five if you don't have any, they are very handy.