Constant crashing with Blue screen

[Micheal]

I'm still trying to find out what programs or processes I require to shut down to stop the ASIO warning each time I start the computer. There are three warnings, with three icons.
1. The letters FMC stacked in a triangel.
2. An open yellow box with the letter G
3. A green icon with what appears to be two leaves, and a yellow and blue security shield.

Any thoughts,

thanks,

Micheál

 

[TorrentG]

Use Autoruns to delete any references to AsIO.sys.

 

[Micheal]

BSOD Again

Hey Torrent G. I've done everything you suggested, and the computer just shut down. Can you detect anything with this minidump.

View attachment 091110-21450-01.zip


Thanks,

Micheál

 

[TorrentG]

You either have faulty system or video card ram. System ram is very likely.

Test with Memtest86+ overnight and see if any errors show.

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

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff880041a9c40, 800000012797b121, fffff88003fff6f0, b}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+17 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly 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: fffff880041a9c40, Virtual address for the attempted write.
Arg2: 800000012797b121, PTE contents.
Arg3: fffff88003fff6f0, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003fff6f0 -- (.trap 0xfffff88003fff6f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880041a9c40 rbx=0000000000000000 rcx=fffffa80053d7a60
rdx=fffff8a0113f8010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041ca80f rsp=fffff88003fff880 rbp=000000000007ab07
 r8=fffffa8005a0f6e0  r9=fffff88003fff900 r10=0000000000000000
r11=fffffa8003a02410 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0x17:
fffff880`041ca80f 7418            je      dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0x31 (fffff880`041ca829) [br=0]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f47ae2 to fffff80002ec7740

STACK_TEXT:  
fffff880`03fff588 fffff800`02f47ae2 : 00000000`000000be fffff880`041a9c40 80000001`2797b121 fffff880`03fff6f0 : nt!KeBugCheckEx
fffff880`03fff590 fffff800`02ec582e : 00000000`00000001 fffff8a0`113f8010 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4237e
fffff880`03fff6f0 fffff880`041ca80f : 00000000`00000001 fffff880`041b90e5 fffff8a0`113f8010 fffff880`041b8d4b : nt!KiPageFault+0x16e
fffff880`03fff880 fffffa80`0651f008 : 00000000`00000006 fffffa80`040e7020 00000000`0007ab07 00000000`00000000 : dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0x17
fffff880`03fff8e0 00000000`00000006 : fffffa80`040e7020 00000000`0007ab07 00000000`00000000 00000000`00000000 : 0xfffffa80`0651f008
fffff880`03fff8e8 fffffa80`040e7020 : 00000000`0007ab07 00000000`00000000 00000000`00000000 fffff8a0`112e6570 : 0x6
fffff880`03fff8f0 00000000`0007ab07 : 00000000`00000000 00000000`00000000 fffff8a0`112e6570 00000012`00000001 : 0xfffffa80`040e7020
fffff880`03fff8f8 00000000`00000000 : 00000000`00000000 fffff8a0`112e6570 00000012`00000001 00000000`00000000 : 0x7ab07


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+17
fffff880`041ca80f 7418            je      dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+0x31 (fffff880`041ca829)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+17

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+17

BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+17

Followup: MachineOwner

 

[Micheal]

Hey. I did not run memtest86+. I have 4Gb of Ram in two physical components. I took one out, the computer shut down. I took the second one out, the computer shut down. I bought a new surge protector just in case, but the computer shut down.

Can we conclude that the issue is with the sound card?

Thanks,

Micheál