BSOD, need help to analyse dmp file

Please follow the https://www.sevenforums.com/crashes-d...tructions.html so we can get all of the crash files and analyze it better.

-Justin

Please fill out your system specs. Click the link in my signature to do it.

Code:

*******************************************************************************
*                                                                             *
*                        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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa80058d67c8, 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:
------------------


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff8000308737c to fffff80003092640

STACK_TEXT:  
fffff880`03308818 fffff800`0308737c : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`058d67c8 : nt!KeBugCheckEx
fffff880`03308820 fffff800`0307c297 : fffffa80`058d6760 00000000`c000009d 00000000`00000000 fffffa80`058d67f8 : nt! ?? ::FNODOBFM::`string'+0x51140
fffff880`033088e0 fffff800`03085cf7 : fffffa80`039f2040 fffffa80`039f2090 00000000`10000004 fffff880`01614fe7 : nt!IopCompletePageWrite+0x57
fffff880`03308910 fffff800`03097b9d : fffffa80`039f2040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1c7
fffff880`03308990 fffff800`03096eaa : fffff880`03308b00 00000000`00000000 fffffa80`00000000 fffffa80`07064470 : nt!KiCommitThreadWait+0x3dd
fffff880`03308a20 fffff800`030222ff : fffffa80`00000002 fffff880`03308d20 fffffa80`00000001 00000000`00000013 : nt!KeWaitForMultipleObjects+0x272
fffff880`03308ce0 fffff800`0332fcce : fffffa80`039f2040 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03308d40 fffff800`03083fe6 : fffff880`02f63180 fffffa80`039f2040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+51140
fffff800`0308737c cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

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

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

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

It appears you may have a hard drive issue. Have you checked your disk for errors? If not, open up a command prompt (hit the Win key and type cmd) and type the following:

chkdsk /r

That will scan your drive for errors and attempt to fix them.

Ok, hit the Win key and type cmd, then in the list that appears above it, right click on the command prompt app and select run as administrator. Then do the chkdsk command.

greenlocal,

Let's look at the results. Here is directions for you:

# **********************INSTRUCTIONS**************************
# STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR ******************
# ************************************************************
#
# WIN key | type POWERSHELL | do NOT hit ENTER |
# in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
# choose "Run as administrator" |
# Click on the YES button (if such appears)
#
# WIN key = key with Microsoft log on top
#
# for the guru:
# WIN | type POWERSHELL | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo
# ************************************************************
# STEP 2 ** COPY AND PASTE ***********************************
# ************************************************************
#
# COPY the script using CTRL+C,
# COPY every line of script down thru both EXIT statements
#
# PASTE into Powershell
#----Right-Click at the PowerShell Prompt
#----(Ctrl+V does not work)
#
# Start copying with first script line without a # at start of the line
# Note: Actually, you can paste the entire file if you rather
#-------Lines starting with a # are ignored by PowerShell
# ************************************************************
# STEP 3 ** SCRIPT OUTPUT & SCRIPT PURPOSE *******************
# ************************************************************
# --The script output and purpose is given at the very front of the script
#
# --The script output and purpose is given at the very front of the script
#
# ************************************************************
# ***************** NOTE - POWERSHELL VERSION*****************
# if you receive this error msg:
#--The system can not find the path specified
# you may need to update your PowerShell
# you must be using Powershell 2.0 or later.
#
# To determine your Powershell version:
#---Run PowerShell
#---enter $host.version
#---you should see at least:
# Major Minor Build Revision
# ----- ----- ----- --------
# 2......0......-1.....-1
#
# If you do not see the above, update your Vista/Win 7.
# ************************************************************
# *************** NOTE - EXECUTION POLICY*********************
# If you haven't set the execution policy, you may need to:
#---Run PowerShell
#---enter SET-EXECUTIONPOLICY -EXECUTIONPOLICY REMOTESIGNED
# ************************************************************

Script:

# ************************************************************
# Places CHKDSKLOGS.txt on your DESKTOP
# Results of running chkdsk (check disk) are in ChkDskLogs.txt
# ************************************************************

$obj = new-object -typename psobject
$events = get-winevent -filterhashtable @{logname='application';id=1001,26212,26214} -verbose:$false -ea:silentlycontinue |
where {($_.providername -ne 'Microsoft-Windows-LoadPerf') -and ($_.providername -ne 'Windows Error Reporting')} |
sort-object -property timecreated -desc 
If ($events -eq $Null) {$events = "No check disk logs exist." } ELSE {
$obj = $events | SELECT timecreated, id, message }

$obj | ft -auto -wrap > $env:userprofile\desktop\CHKDSKLOGS.TXT

EXIT
EXIT

# ************************************************************ 


Attach the chkdsklogs.txt file that appears on your desktop to your next post.