BSOD various incidents, error 0x000000fc

[EpixBurninator]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: fc
BCP1: FFFFF900C06D8688
BCP2: D2E0000090F9A863
BCP3: FFFFF88005F12930
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022112-24024-01.dmp
C:\Users\Austin\AppData\Local\Temp\WER-51963-0.sysdata.xml


Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? xp
- an OEM or full retail version? full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? varies
- What is the age of OS installation (have you re-installed the OS?) re-installed within the past 2 months

Any help is appreciated. I use my computer for gaming and many of the times the computer has crashed were while I was playing a game.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\EpixBurninator\Windows_NT6_BSOD_jcgriff2\022112-26878-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c45670
Debug session time: Tue Feb 21 10:44:40.732 2012 (UTC - 7:00)
System Uptime: 0 days 0:39:50.730
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8947d1644, b3b7465ee6f9e59a, fffff80002eade80, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8947d1644, Reserved
Arg2: b3b7465ee6f9e59a, Reserved
Arg3: fffff80002eade80, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
	0 : A generic data region
	1 : Modification of a function or .pdata
	2 : A processor IDT
	3 : A processor GDT
	4 : Type 1 process list corruption
	5 : Type 2 process list corruption
	6 : Debug routine modification
	7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002a7cc40

STACK_TEXT:  
fffff880`02fc75d8 00000000`00000000 : 00000000`00000109 a3a039d8`947d1644 b3b7465e`e6f9e59a fffff800`02eade80 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

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

Loading Dump File [D:\Kingston\BSODDmpFiles\EpixBurninator\Windows_NT6_BSOD_jcgriff2\021912-23072-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c5b670
Debug session time: Sun Feb 19 17:31:44.623 2012 (UTC - 7:00)
System Uptime: 0 days 1:10:43.621
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 30, 0, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000030
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgnsa.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88004e296e0 -- (.trap 0xfffff88004e296e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000004c00000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b70bc5 rsp=fffff88004e29870 rbp=fffff88004e298c0
 r8=fffff80002a16000  r9=0000000000000001 r10=0000058000000000
r11=0000000fffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiResolvePageFileFault+0x1115:
fffff800`02b70bc5 8b4830          mov     ecx,dword ptr [rax+30h] ds:0003:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a25d7e to fffff80002a92c40

STACK_TEXT:  
fffff880`04e29578 fffff800`02a25d7e : 00000000`0000001a 00000000`00041287 00000000`00000030 00000000`00000000 : nt!KeBugCheckEx
fffff880`04e29580 fffff800`02a90d6e : 00000000`00000000 00000000`00000030 fffffa80`02491800 00000000`04c00000 : nt! ?? ::FNODOBFM::`string'+0x46485
fffff880`04e296e0 fffff800`02b70bc5 : 00000000`000960a2 00000000`00000000 00000000`00000000 fffff880`0116ba48 : nt!KiPageFault+0x16e
fffff880`04e29870 fffff800`02b056b0 : 00000000`7795e6d0 fffff680`003bcaf0 fffffa80`04e12ec8 00000000`00000011 : nt!MiResolvePageFileFault+0x1115
fffff880`04e299b0 fffff800`02a9ff19 : 00000000`00000000 ffffffff`ffffffff fffffa80`0519ce40 fffffa80`0518dda0 : nt! ?? ::FNODOBFM::`string'+0x399d4
fffff880`04e29ac0 fffff800`02a90d6e : 00000000`00000008 00000000`7795e6d0 00000000`00000001 00000000`0235f9e0 : nt!MmAccessFault+0x359
fffff880`04e29c20 00000000`7795e6d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`013dfa18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7795e6d0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46485
fffff800`02a25d7e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46485

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485

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

Directly or indirectly caused by AVG; typically due to a network adapter/a network adapter driver/antivirus software. I do note you using a USB wireless device. USB wireless is unstable due to the USB device not providing the proper power to the adapter to maintain it. We recommend replacing USB wireless adapters with a PCI adapter in the system.

Uninstall AVG with the AVG Remover and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.


Start with the above and see if stability improves. If not, we will do further analysis and provide more steps.