Several small problems combine to make a bigger one
1-Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller
DuplexSecure - Downloads
when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.
2- Old drivers needing updating
Code:
MarvinBus.sys 9/23/2005 5:17:57 PM 0x90157000 0x90185000 0x0002e000 0x43347105
000.fcl 9/26/2008 9:11:12 AM 0x9ad68000 0x9ad94000 0x0002c000 0x48dcdf70
Rt86win7.sys 2/26/2009 5:04:22 AM 0x8f353000 0x8f378000 0x00025000 0x49a65b16
3-Since they both reflect memory_corruption I would run memtest.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
I suspect the stpd.sys and driver updates will help. Let us know if they dont.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\060411-18283-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c49000 PsLoadedModuleList = 0x82d89230
Debug session time: Sat Jun 4 09:54:02.358 2011 (GMT-4)
System Uptime: 0 days 0:01:36.106
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0001f374, page frame number
Arg3: 00000002, current page state
Arg4: 00023c23, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: VSSVC.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 82d2ca4d to 82d1b428
STACK_TEXT:
883b3758 82d2ca4d 0000004e 00000099 0001f374 nt!KeBugCheckEx+0x1e
883b3770 82ccaefa c0402000 883b3808 9324b3d8 nt!MiBadShareCount+0x24
883b37b4 82ccb193 9324b1e8 9b4729a0 9324b1e8 nt!MiDeletePfnList+0x2c4
883b3c14 82cbf878 9324b1e8 9324b1e8 00000000 nt!MiDeleteAddressesInWorkingSet+0x28f
883b3c40 82e5a9bb af669056 9b4729a0 000000ff nt!MmCleanProcessAddressSpace+0x87
883b3cb4 82ebe0ef 00000000 8c6eff40 00000001 nt!PspExitThread+0x685
883b3ccc 82cb7699 8c6eff40 883b3cf8 883b3d04 nt!PsExitSpecialApc+0x22
883b3d1c 82c7e974 00000001 00000000 883b3d34 nt!KiDeliverApc+0x28b
883b3d1c 774a70b4 00000001 00000000 883b3d34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
00f3f7a4 00000000 00000000 00000000 00000000 0x774a70b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+24
82d2ca4d cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+24
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fd76c
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_99_VRF_nt!MiBadShareCount+24
BUCKET_ID: 0x4E_99_VRF_nt!MiBadShareCount+24
Followup: MachineOwner
---------
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 Reference
- - Driver manufacturer links are on this page:
Drivers and Downloads