BSOD on Windows 7 64bit - kernel stack inpage error

Welcome to SF!

Usual causes: Memory, Corrupt paging file, File system errors, Disk errors, Bad cables, BIOS, Missing Service Pack, Bad motherboard, Virus infection (particulary in the MBR), Improperly seated cards

BSOD Index

That's the only thing we can tell from what you gave us. Could you please upload the dmp files? https://www.sevenforums.com/crash-loc...d-problem.html

Thanks,
~JK

Try scanning with Malwarebyes, using a full scan.

Try testing your hard drive with one of these tools: HD Diagnostic

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

If you can find a BIOS update, install it.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_050410-24944-01.zip\050410-24944-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a1c000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Tue May  4 15:39:29.321 2010 (GMT-4)
System Uptime: 0 days 0:49:07.475
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 13350ccb98001ae, 0, fffff88002a55fd0}

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

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

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

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in.  Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found.  Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED)  normally indicates
the data could not be read from the disk due to a bad
block.  Upon reboot autocheck will run and attempt to map out the bad
sector.  If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked.  See the knowledge base article on SCSI termination.
Arguments:
Arg1: 0000000000000001, (page was retrieved from disk)
Arg2: 013350ccb98001ae, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: fffff88002a55fd0, address of signature on kernel stack

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


ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

BUGCHECK_STR:  0x77_1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b0d293 to fffff80002a84900

STACK_TEXT:  
fffff880`03363b58 fffff800`02b0d293 : 00000000`00000077 00000000`00000001 013350cc`b98001ae 00000000`00000000 : nt!KeBugCheckEx
fffff880`03363b60 fffff800`02a79440 : fffffa80`0482eb60 00000000`00000001 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x439b1
fffff880`03363c70 fffff800`02a793db : 00000000`00000000 00000000`00000001 fffffa80`01846890 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`03363cd0 fffff800`02a7907c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`01846800 : nt!KiInSwapKernelStacks+0x1f
fffff880`03363d00 fffff800`02d2ca26 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`03363d40 fffff800`02a62866 : fffff800`02c01e80 fffffa80`0197ab60 fffff800`02c0fc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03363d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+439b1
fffff800`02b0d293 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+439b1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cff0

FAILURE_BUCKET_ID:  X64_0x77_1_nt!_??_::FNODOBFM::_string_+439b1

BUCKET_ID:  X64_0x77_1_nt!_??_::FNODOBFM::_string_+439b1

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

If Memtest turns up errors, replace the RAM.

If the HD Diagnostic fails, replace your hard drive or cable.

If Malwarebytes finds stuff, let it clean your computer.

You must have accidentally uploaded the same zip folder twice. The one you just uploaded is the same file as you posted earlier.

Delete the file, and upload any new files that are generated.