Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD

11 Feb 2010   #1


Attachment 53439

Because Ken said to do it

My System SpecsSystem Spec
11 Feb 2010   #2

Win 8 Release candidate 8400

Quote   Quote: Originally Posted by TGSoldier View Post
Attachment 53439

Because Ken said to do it

Her crashes are being caused by her Panda antivirus, and memory corruption. she also has a ton of drivers that a re out of date listed below.

here is what I would do
1-remove the panda AV
2-run a system file check (type cmd in search>right click and run as admin>sfc /scannow
3-download memtestx86 and run for 5 passes

If she is overclocking STOP


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

Loading Dump File [C:\Users\K\Desktop\Dumps\020910-63781-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a40000 PsLoadedModuleList = 0x82b88810
Debug session time: Tue Feb  9 18:40:41.670 2010 (GMT-5)
System Uptime: 1 days 1:31:08.219
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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
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.
Arg1: c0463df8, lock type that was held (value 1,2,3, or PTE address)
Arg2: c00000c0, error status (normally i/o status code)
Arg3: 711efbe0, current process (virtual address for lock type 3, or PTE)
Arg4: 8c7bf000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:

ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

BUGCHECK_STR:  0x7a_c00000c0





LAST_CONTROL_TRANSFER:  from 82af460a to 82b1cd10

8bd4faf4 82af460a 0000007a c0463df8 c00000c0 nt!KeBugCheckEx+0x1e
8bd4fb68 82aec0d5 8838eb2c 8bd4fbc0 82b74540 nt!MiWaitForInPageComplete+0x2fd
8bd4fbfc 82ac7e3f 82b74540 8c7bf000 8838ea98 nt!MiIssueHardFault+0x3b2
8bd4fc80 82a74259 00000001 8c7bf000 00000000 nt!MmAccessFault+0x2656
8bd4fd10 82a73f7a 877cd030 8bd4fd30 00000000 nt!MiInPageSingleKernelStack+0x1cf
8bd4fd44 82acc003 877cd0a4 8bd4fd90 82c4e66d nt!KiInSwapKernelStacks+0x41
8bd4fd50 82c4e66d 00000000 abfc3599 00000000 nt!KeSwapProcessOrStack+0x78
8bd4fd90 82b000d9 82acbf8b 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


82af460a cc              int     3


SYMBOL_NAME:  nt!MiWaitForInPageComplete+2fd

FOLLOWUP_NAME:  MachineOwner



IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x7a_c00000c0_nt!MiWaitForInPageComplete+2fd

BUCKET_ID:  0x7a_c00000c0_nt!MiWaitForInPageComplete+2fd

Followup: MachineOwner

mdmxsdk.sys        0x95398000    0x9539b100    0x00003100    0x4344688d    10/5/2005 6:58:05 PM                        
HSX_CNXT.sys        0x95100000    0x951b6000    0x000b6000    0x438fa5f5    12/1/2005 8:40:05 PM                        
HSXHWAZL.sys        0x8fcd0000    0x8fd0a000    0x0003a000    0x438fa5fa    12/1/2005 8:40:10 PM                        
HSX_DPV.sys        0x95009000    0x95100000    0x000f7000    0x438fa624    12/1/2005 8:40:52 PM                        
secdrv.SYS        0x98ed5000    0x98edf000    0x0000a000    0x45080528    9/13/2006 8:18:32 AM                        
rixdptsk.sys        0x912ed000    0x9133e000    0x00051000    0x455a6ed7    11/14/2006 8:35:19 PM                        
bcm4sbxp.sys        0x91297000    0x912a8000    0x00011000    0x4562f047    11/21/2006 7:25:43 AM                        
ShlDrv51.sys        0x90000000    0x90008680    0x00008680    0x47cd54d5    3/4/2008 8:55:33 AM                        
fnetmon.SYS        0x953cd000    0x953d0c00    0x00003c00    0x47ebe153    3/27/2008 1:02:59 PM                        
av5flt.sys    av5flt.sys+9340    0x98fb7000    0x98fcf080    0x00018080    0x48e5ff79    10/3/2008 6:18:17 AM
My System SpecsSystem Spec
11 Feb 2010   #3


Thanks Ken.
My System SpecsSystem Spec

11 Feb 2010   #4

Win 8 Release candidate 8400

My System SpecsSystem Spec
11 Feb 2010   #5


Panda was uninstalled..

Could you check this one for me? Just to see if it points to anything other than the heat/mem probs/old drivers.Attachment 53608
My System SpecsSystem Spec
12 Feb 2010   #6
Microsoft MVP


Your build changed from: 7600.16385.x86fre.win7_rtm.090713-1255
to: 7600.16481.x86fre.win7_gdr.091207-1941

This reflects some sort of Windows Update - maybe an optional update for a specific problem (GDR = General Distribution Release)?

Most significant (IMO) is this:
DISK_HARDWARE_ERROR: There was error with disk hardware
Start with these diagnostics to rule out the hard drive (the STOP 0x8E above can also relate to the hard drive controller):
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
And this:
HD Diagnostic (read the details at the link)
Also, please remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page:

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
bcm4sbxp.sys Tue Nov 21 07:25:43 2006 - Broadcom 440x 10/100 Integrated Controller -
HSX_CNXT.sys Thu Dec 01 20:40:05 2005 - SoftK56 Modem Driver by Conexant   Systems -
HSX_DPV.sys  Thu Dec 01 20:40:52 2005 - SoftK56 Modem Driver by Conexant   Systems -
HSXHWAZL.sys Thu Dec 01 20:40:10 2005 - SoftK56 Modem Driver by Conexant   Systems -
mdmxsdk.sys  Wed Oct 05 19:58:05 2005 - SoftK56 Modem Driver by Conexant   Systems -
rixdptsk.sys Tue Nov 14 20:35:19 2006 - Ricoh Memory Card Reader driver -
Summary of the BSOD:
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Thu Feb 11 19:50:44.941 2010 (GMT-5)
System Uptime: 0 days 9:09:36.269
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
My System SpecsSystem Spec


Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:18.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App