Bsod playing various games

eddybaby1234 · 17 Oct 2011

I have recently beenn having problems with this error it happens everytime i try to play recent games can any one help

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 03D63344
BCP2: 00000002
BCP3: 00000001
BCP4: 82ACFEF2
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\101711-25218-01.dmp
C:\Users\ed\AppData\Local\Temp\WER-57328-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

yowanvista · 17 Oct 2011

Update the Nvidia driver
Drivers - Download NVIDIA Drivers

Stop any overclocking if any
Update your Realtek NIC driver
Realtek

Code:

Rt86win7.sys        0x92b52000    0x92b77000    0x00025000    0x49a65b16    26/02/2009 13:04:22

Information

If your still get BSODs run Driver Verifier and upload any dumps which are then created
Driver Verifier - Enable and Disable

Note: Your computer may not be functional in Normal Mode if faulting drivers are detected during this phase, you may need to use Safemode with Networking.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 03d63344, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82acfef2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba0848
Unable to read MiSystemVaType memory at 82b7fe40
 03d63344 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+69
82acfef2 f00fba2900      lock bts dword ptr [ecx],0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  a40bfbac -- (.trap 0xffffffffa40bfbac)
ErrCode = 00000002
eax=2000caf9 ebx=0000000e ecx=03d63344 edx=00000001 esi=03d6333c edi=852bf754
eip=82acfef2 esp=a40bfc20 ebp=a40bfc34 iopl=0         nv up ei pl nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010203
nt!MiReplenishPageSlist+0x69:
82acfef2 f00fba2900      lock bts dword ptr [ecx],0   ds:0023:03d63344=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82acfef2 to 82a785db

STACK_TEXT:  
a40bfbac 82acfef2 badb0d00 00000001 a40bfc10 nt!KiTrap0E+0x2cf
a40bfc34 82ac9b24 82ba1140 00000001 00000002 nt!MiReplenishPageSlist+0x69
a40bfca0 82ac73d7 00000001 00000002 03691000 nt!MiRemoveAnyPage+0x514
a40bfd1c 82a783e8 00000001 03691000 00000001 nt!MmAccessFault+0x2100
a40bfd1c 6ef5824c 00000001 03691000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0130d700 00000000 00000000 00000000 00000000 0x6ef5824c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+69
82acfef2 f00fba2900      lock bts dword ptr [ecx],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiReplenishPageSlist+69

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiReplenishPageSlist+69

BUCKET_ID:  0xA_nt!MiReplenishPageSlist+69

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

eddybaby1234 · 17 Oct 2011

ok it is still happening even after updating the drivers and it happened as soon as windows loaded up with the verifier active here the the dump file from that hope it helps

thanks ed

yowanvista · 18 Oct 2011

A driver used by Magi ISO caused the crash, remove this software

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
    call to IoMarkIrpPending.
Arg2: 8540712a, The address in the driver's code where the error was detected.
Arg3: 984e0f68, IRP address.
Arg4: 00000103, Status code.

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


BUGCHECK_STR:  0xc9_24c

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  24c

FAULTING_IP: 
mcdbus+712a
8540712a 8b442404        mov     eax,dword ptr [esp+4]

FOLLOWUP_IP: 
mcdbus+712a
8540712a 8b442404        mov     eax,dword ptr [esp+4]

IRP_ADDRESS:  984e0f68

DEVICE_OBJECT: 8d3f9e78

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82d83f03 to 82b2beb4

STACK_TEXT:  
88195abc 82d83f03 000000c9 0000024c 8540712a nt!KeBugCheckEx+0x1e
88195adc 82d862cd 8540712a 88195b14 8540712a nt!VerifierBugCheckIfAppropriate+0x30
88195af4 82d86414 0000024c 8540712a 00000103 nt!ViErrorFinishReport+0xc9
88195b64 82d84620 0000024c 984e0f68 00000103 nt!VfErrorReport6+0x51
88195b94 82d83e5f 8834e6f4 8834e690 00000000 nt!IovpCallDriver2+0x155
88195ba8 82d7e6d4 8834e6f4 00000000 927446c0 nt!VfAfterCallDriver+0x119
88195bcc 82a84545 00000000 92772600 8d3f9e78 nt!IovCallDriver+0x269
88195be0 8554e49c 6d8bb938 88195c6c 00000000 nt!IofCallDriver+0x1b
88195c24 85559ffe 00772600 88195c6c 88195c50 Wdf01000!FxIoTarget::SubmitSync+0x198
88195c48 85f5d7d6 00000020 92772600 927446c0 Wdf01000!imp_WdfRequestSend+0x178
88195c7c 85f5d381 9271bcc0 82a197a0 9271bcc0 cdrom!RequestSendMcnRequest+0x4a
88195cb0 85f5d85d 9271bcc0 6d880968 92747608 cdrom!RequestProcessSerializedIoctl+0x37c
88195cc4 8556e042 6d8b89f0 9853efe0 92747608 cdrom!IoctlWorkItemRoutine+0x4b
88195ce0 8556e0aa 927436e0 88195d00 82c614dc Wdf01000!FxWorkItem::WorkItemHandler+0xad
88195cec 82c614dc 927436e0 92747608 861814c0 Wdf01000!FxWorkItem::WorkItemThunk+0x19
88195d00 82acaa6b 9853efe0 00000000 861814c0 nt!IopProcessWorkItem+0x23
88195d50 82c55fda 00000001 a58f9227 00000000 nt!ExpWorkerThread+0x10d
88195d90 82afe1d9 82aca95e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  mcdbus+712a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mcdbus

IMAGE_NAME:  mcdbus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49a3cf05

FAILURE_BUCKET_ID:  0xc9_24c_VRF_mcdbus+712a

BUCKET_ID:  0xc9_24c_VRF_mcdbus+712a

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

eddybaby1234 · 18 Oct 2011

ok ive removed the driver mentioned but the pc was just crashing everytime i booted up so i had to do it quickly but now i cant even get windows to load before it crashes even in safe modes any ideas on what to do

thanks ed

eddybaby1234 · 18 Oct 2011

ok i have managed to boot the pc in safe mode and here is the latest dump file hope it helps.

thanks ed

yowanvista · 18 Oct 2011

This seems to be a RAM problem, if you get BSODs/crashes even in Safe Mode then its a hardware problem
Test the RAM RAM - Test with Memtest86+

If any errors are detected during this test the RAM should be replaced

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: a5f90f68, address trying to free
Arg2: a5f904bf, address where one bit is corrupted
Arg3: 008b0094, (reserved)
Arg4: 00000032, caller is freeing an address where nearby bytes within the same page have a single bit error

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


BUGCHECK_STR:  0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE:  32

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  vsserv.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82b2fbbb to 82b27eb4

STACK_TEXT:  
a0c27ab0 82b2fbbb 000000c1 a5f90f68 a5f904bf nt!KeBugCheckEx+0x1e
a0c27ad4 82b306a1 a5f90f68 a5f90000 a5f90f68 nt!MiCheckSpecialPoolSlop+0x6e
a0c27bb4 82b69b90 a5f90f68 90cec758 90cec758 nt!MmFreeSpecialPool+0x15b
a0c27c18 82d8a06e a5f90f68 00000000 a0c27c40 nt!ExFreePoolWithTag+0xd6
a0c27c28 82d7fab2 a5f90f68 02d37030 a5f90f68 nt!ViCtxFreeIsrContext+0xf
a0c27c40 82d7a1c0 82c71e5d a5f90f68 a0c27c94 nt!VfIoFreeIrp+0xd3
a0c27c50 82c71e5d a5f90f68 8d6265f3 00000001 nt!IovFreeIrpPrivate+0x47
a0c27c94 82c4fc10 00000001 a0c27ccc a0c27ce4 nt!IoRemoveIoCompletion+0xc5
a0c27d18 82a871fa 00000258 01d1ff54 01d1ff44 nt!NtRemoveIoCompletion+0x106
a0c27d18 77c970b4 00000258 01d1ff54 01d1ff44 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01d1ff2c 00000000 00000000 00000000 00000000 0x77c970b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckSpecialPoolSlop+6e
82b2fbbb cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiCheckSpecialPoolSlop+6e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02a389

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+6e

BUCKET_ID:  0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+6e

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

eddybaby1234 · 18 Oct 2011

ok so i tried doing that but the system just restarted itself and now when ever i try loading anything it just comes up with system resor or start windows normally whenever i select either of them it just restars again it seem like its getting worse.