BSOD sudden crashes

[fchiang]

Hi

My computer crashes every now and then. It will restart and everything seems alright until it crashes again.

I attach the dump file. Grateful for your help.

 

[koolkat77]

Follow these-

Get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the rb:
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:
http://www.sevenforums.com/tutorials/433-disk-check.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc4005ffa8, ffffffffc000000e, 40f9bbe0, fffff8800bff5000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+37bba )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. 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: fffff6fc4005ffa8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000040f9bbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800bff5000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b0d9d2 to fffff80002a9e640

STACK_TEXT:  
fffff880`0331d848 fffff800`02b0d9d2 : 00000000`0000007a fffff6fc`4005ffa8 ffffffff`c000000e 00000000`40f9bbe0 : nt!KeBugCheckEx
fffff880`0331d850 fffff800`02ac613f : fffffa80`055733a0 fffff880`0331d9c0 fffff800`02c22ec0 fffffa80`055733a0 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`0331d930 fffff800`02aac9b9 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`02abdf43 : nt!MiIssueHardFault+0x28b
fffff880`0331da00 fffff800`02ad2ee0 : 00000000`00000001 fffff880`0bff5000 fffffa80`04a6c300 fffff6fc`4005ff80 : nt!MmAccessFault+0x1399
fffff880`0331db60 fffff800`02ad30d0 : fffffa80`03c62b60 00000000`00000001 fffffa80`00000000 fffff800`02acff03 : nt!MiInPageSingleKernelStack+0x134
fffff880`0331dc70 fffff800`02ad305f : 00000000`00000000 00000000`00000001 fffffa80`039c8040 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`0331dcd0 fffff800`02ad2da4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`039c8000 : nt!KiInSwapKernelStacks+0x1f
fffff880`0331dd00 fffff800`02d3bcce : ffbfdfff`ffffffdf 5fbdf5fa`eceffdf2 fafffbb7`fffff7da beffffff`fffffbff : nt!KeSwapProcessOrStack+0x84
fffff880`0331dd40 fffff800`02a8ffe6 : fffff880`02f63180 fffffa80`039ee040 fffff880`02f6dfc0 ffff7ffe`effdffff : nt!PspSystemThreadStartup+0x5a
fffff880`0331dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+37bba
fffff800`02b0d9d2 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+37bba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+37bba

BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+37bba

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