Windows 7 Bluescreen's - Please help!

This dump shows a stop error code of FC which is a hardware error. The Dump, unfortunately, does not point to a particular driver

STOP 0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

Usual causes: Device driver

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\060510-23852-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82807000 PsLoadedModuleList = 0x8294f810
Debug session time: Sat Jun  5 05:34:35.203 2010 (GMT-4)
System Uptime: 0 days 0:07:04.904
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
1: kd> !analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {af2ceb14, 7fa31963, af2ce778, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

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

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: af2ceb14, Virtual address for the attempted execute.
Arg2: 7fa31963, PTE contents.
Arg3: af2ce778, (reserved)
Arg4: 00000000, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFC

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

TRAP_FRAME:  af2ce778 -- (.trap 0xffffffffaf2ce778)
ErrCode = 00000011
eax=00000000 ebx=807c2000 ecx=00000000 edx=8001003b esi=853368a8 edi=807c7800
eip=af2ceb14 esp=af2ce7ec ebp=88a3e368 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
af2ceb14 d8eb            fsubr   st,st(3)
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8284d638 to 8288c903

STACK_TEXT:  
af2ce760 8284d638 00000008 af2ceb14 00000000 nt!MmAccessFault+0x106
af2ce760 af2ceb14 00000008 af2ceb14 00000000 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
af2ce7ec 8286e966 807c2120 807c3a3c 82875b25 0xaf2ceb14
af2ce7f8 82875b25 807c3a3c 00000000 853368a8 nt!KiSwapContext+0x26
af2ce830 82874423 af2ce858 853368a8 88ad5640 nt!KiSwapThread+0x266
af2ce858 8286e2cf 853368a8 85336968 00000000 nt!KiCommitThreadWait+0x1df
af2ce8d4 828bb392 88ad5640 00000009 00000000 nt!KeWaitForSingleObject+0x393
af2ce948 82836950 852c4bcc 00000000 00000000 nt!MiWaitForInPageComplete+0x75
af2ce96c 82a19e62 00000000 00000000 00000000 nt!MiPfCompletePrefetchIos+0x6c
af2ce9a0 82a0b7e3 00000001 af2ce9f0 00000000 nt!MmPrefetchPages+0x19b
af2cea2c 82a0d0f2 002cea58 af2cebb4 00000001 nt!PfpPrefetchFilesTrickle+0x1b0
af2cead0 82a0cdaf b2e9c000 8b5abc78 af2cebc8 nt!PfpPrefetchRequestPerform+0x2a6
af2ceb24 82a269c7 af2cebb4 04704001 8b5abcb4 nt!PfpPrefetchRequest+0x16e
af2cebe8 82a92936 012bf7fc 00000014 04704001 nt!PfSetSuperfetchInformation+0x182
af2ced20 8284a44a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0xb00
af2ced20 777f64f4 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
012bf814 00000000 00000000 00000000 00000000 0x777f64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+dc
8284d638 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiTrap0E+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf

FAILURE_BUCKET_ID:  0xFC_nt!KiTrap0E+dc

BUCKET_ID:  0xFC_nt!KiTrap0E+dc

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

I find the following outdated drivers on your system. Windows 7 does not pay well with older drivers.

Apfiltr.sys Fri Mar 14 08:23:10 2008 (47DA6E2E)
b57nd60x.sys Sun Apr 26 07:15:34 2009 (49F44256)
bcmwl6.sys Thu Mar 26 20:58:48 2009 (49CC24C8)
BisonC07.sys Fri Jun 19 07:41:20 2009 (4A3B7960)
GEARAspiWDM.sys Mon May 18 08:16:53 2009 (4A1151B5)
iaStor.sys Thu Jun 04 21:42:33 2009 (4A287809)
igdkmd32.sys Fri Jul 03 12:33:51 2009 (4A4E32EF)

I recommend that you update these obsolete drivers, especially Apfiltr.sys - which is an Alps Pointing-device Driver or Alps Touch Pad Driver belongs to the software Alps Pointing-device Driver for Windows 2000/XP or Alps Touch Pad Filter Driver for Windows 2000/XP or Alps Touch Pad Driver for Windows 2000/XP or Alps Pointing-device Filter Driver by Alps Electric Co., Ltd (www.alps.com).

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 - 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: Drivers and Downloads

I also recommend that you enable Driver Verifier.

Using Driver Verifier to identify issues with Drivers

Please follow these instructions in order to run it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

Please post back with any questions.

Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

Povall54 said:

Thanks for the extremely quick response, i've also had a MEMORY_MANAGEMENT BSOD. I've scanned with memtest and found no issues.

I noticed in that log there was reference to a vista driver? Could it be i've installed a out of date driver?

I edited my original post, You may need to refresh the page.

To answer your question, a memory management BSOD can be triggered by several things such driver conflicts, defective RAM, program incompatibility, etc. This particular dump pointed to driver problems and that is why I started with those.

Jonathan is right on target; run Driver Verifier.

When you ran memtest, how many passes did you run? I recommend at least seven passes using memtest 86+.

Leave Verifier running for as long as 36 hours, and use your computer normally while you do.

If it doesn't BSOD in 36 hours, turn it off.

Jonathan beat me to it.