BSOD while Playing SWTOR, watching movies, using internet

stumpedplshelp · 10 Jan 2012

Built this rig almost 2 years ago, AMD 965 BE, 4gb ocz ddr3 1600 (had 8 but 4gb were corrupt), Win 7 Home Premium x64, Asus MB

Just started getting random BSOD in the past week or so while playing SWTOR, watching vids on internet.

Thanks in advance for any input you can give!

Hipster Doofus · 10 Jan 2012

If you have the cpu overclocked back it off to default to see it the problem continues.

stumpedplshelp · 10 Jan 2012

CPU is not OCed at all, didn't wan tto take a chance with it being in a Thermaltake lanbox, and minimum room for cooling fan

stumpedplshelp · 11 Jan 2012

ANY type of help on this would be greatly appreciated!!

writhziden · 12 Jan 2012

Code:


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\stumpedplshelp\BSOD INFO\Windows_NT6_BSOD_jcgriff2\011012-18579-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`03046670
Debug session time: Tue Jan 10 12:15:47.729 2012 (UTC - 7:00)
System Uptime: 0 days 1:07:33.290
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 41768, 1, 0}

Probably caused by : afd.sys ( afd! ?? ::GFJBLGFE::`string'+1529 )

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

1: 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: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 0000000000041768, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002edd108 to fffff80002e7dc40

STACK_TEXT:  
fffff880`035894f8 fffff800`02edd108 : 00000000`0000004e 00000000`00000007 00000000`00041768 00000000`00000001 : nt!KeBugCheckEx
fffff880`03589500 fffff800`02eee856 : fffffa80`03d35250 0000001e`0159b00a 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x175b6
fffff880`03589540 fffff880`040c2109 : fffffa80`03d3008b 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x37875
fffff880`035895d0 fffff880`04074849 : fffffa80`062d6000 00000000`00000000 fffffa80`0000004c fffffa80`041b5e10 : afd! ?? ::GFJBLGFE::`string'+0x1529
fffff880`035896a0 fffff880`040b84b9 : fffffa80`062430b8 00000000`00000001 fffffa80`050bc150 00000000`00000000 : afd!AfdReceiveDatagramEventCommonHandler+0x389
fffff880`03589740 fffff880`0169bc75 : fffffa80`0000004c fffffa80`0497a380 00000000`00000000 fffffa80`06571b70 : afd!AfdTLDgramReceiveEventHandler+0xe9
fffff880`035897d0 fffff880`0169584d : fffffa80`00000028 fffffa80`06571b70 fffffa80`00000000 fffffa80`03ece2c8 : tcpip!UdpDeliverDatagrams+0x155
fffff880`03589960 fffff880`01674227 : fffffa80`0483c900 fffffa80`04fe1580 fffffa80`063c0017 00000000`00000000 : tcpip!UdpReceiveDatagrams+0x1ed
fffff880`03589a70 fffff880`01673d3a : 00000000`00000000 fffff880`0178e800 fffff880`03589c30 fffffa80`0497a380 : tcpip!IppDeliverListToProtocol+0xf7
fffff880`03589b30 fffff880`01673339 : 00000000`00000000 fffffa80`06239000 00000000`00000000 fffff880`03589c20 : tcpip!IppProcessDeliverList+0x5a
fffff880`03589bd0 fffff880`0165826f : fffffa80`06239080 fffffa80`00000001 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a
fffff880`03589cb0 fffff800`02e75757 : fffff880`0178e800 00000000`00000011 00000000`00000000 00000000`00000000 : tcpip!IppLoopbackTransmit+0x38f
fffff880`03589d60 fffff800`02e75711 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`046860b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd! ?? ::GFJBLGFE::`string'+1529
fffff880`040c2109 488bcd          mov     rcx,rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  afd! ?? ::GFJBLGFE::`string'+1529

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4db4dd96

FAILURE_BUCKET_ID:  X64_0x4E_7_afd!_??_::GFJBLGFE::_string_+1529

BUCKET_ID:  X64_0x4E_7_afd!_??_::GFJBLGFE::_string_+1529

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

This is usually caused by a driver accessing bad memory or a problem with the memory itself.

Run the following steps and post back after doing each one.

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete.
Run Driver Verifier to find any driver incompatibilities/conflicts. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.