So, i've had this error for months where my PC crashed when playing games. It has only recently started giving minidumps. Now that i have one, can you guys help me fix this?
Here's the analysis from windbg
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff73500a, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: b86714e9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ff73500a
FAULTING_IP:
RDUMMY+4e9
b86714e9 c6410a01 mov byte ptr [ecx+0Ah],1
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: AvastSvc.exe
LAST_CONTROL_TRANSFER: from 804ef19f to b86714e9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b1ef4a24 804ef19f 83dc8ea0 82f707b0 82f70914 RDUMMY+0x4e9
b1ef4a58 8054bd24 82f707b0 83dc1530 83dc15e8 nt!IopfCallDriver+0x31
b1ef4ab8 b80d9400 83dc1530 82f707b0 82f707b0 nt!ExAllocatePoolWithTag+0x3bc
b1ef4b4c b80e93ed 83dc1530 82f707b0 82f7091c disk+0x1400
b1ef4b68 804ef19f 83dc1530 82f707b0 82f707b0 CLASSPNP+0x13ed
b1ef4ba4 804ef19f 83db1020 82f707b0 82f70940 nt!IopfCallDriver+0x31
b1ef4bb4 805d8110 82e0c828 82ec08b0 b1ef4c04 nt!IopfCallDriver+0x31
b1ef4bc4 805d7e02 82ec08b0 82f707b0 82f7091c nt!RawReadWriteDeviceControl+0x60
b1ef4c04 804ef19f 82ec07f8 82f707b0 82f707b0 nt!RawDispatch+0x114
b1ef4c14 b7ec609e 82f707b0 8aabf2e0 868d6338 nt!IopfCallDriver+0x31
b1ef4c40 804ef19f 82e0c828 82f707b0 806e7410 fltMgr!FltGetIrpName+0x12e0
b1ef4c50 8057f98e 82f7091c 868d6338 82f707b0 nt!IopfCallDriver+0x31
b1ef4c64 8058081d 82e0c828 82f707b0 868d6338 nt!IopSynchronousServiceTail+0x70
b1ef4d00 80579298 000013a8 00000000 00000000 nt!IopXxxControlFile+0x5c5
b1ef4d34 8054167c 000013a8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b1ef4d34 7c90e514 000013a8 00000000 00000000 nt!KiFastCallEntry+0xfc
09b3a340 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
RDUMMY+4e9
b86714e9 c6410a01 mov byte ptr [ecx+0Ah],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RDUMMY+4e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDUMMY
IMAGE_NAME: RDUMMY.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47242fec
FAILURE_BUCKET_ID: 0x50_RDUMMY+4e9
BUCKET_ID: 0x50_RDUMMY+4e9
Followup: MachineOwner
---------
So i'm assuming it's a driver problem with rdummy.sys caused by my antivirus (avast). Is there any way to fix this? Thanks .
Here's the analysis from windbg
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff73500a, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: b86714e9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: ff73500a
FAULTING_IP:
RDUMMY+4e9
b86714e9 c6410a01 mov byte ptr [ecx+0Ah],1
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: AvastSvc.exe
LAST_CONTROL_TRANSFER: from 804ef19f to b86714e9
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b1ef4a24 804ef19f 83dc8ea0 82f707b0 82f70914 RDUMMY+0x4e9
b1ef4a58 8054bd24 82f707b0 83dc1530 83dc15e8 nt!IopfCallDriver+0x31
b1ef4ab8 b80d9400 83dc1530 82f707b0 82f707b0 nt!ExAllocatePoolWithTag+0x3bc
b1ef4b4c b80e93ed 83dc1530 82f707b0 82f7091c disk+0x1400
b1ef4b68 804ef19f 83dc1530 82f707b0 82f707b0 CLASSPNP+0x13ed
b1ef4ba4 804ef19f 83db1020 82f707b0 82f70940 nt!IopfCallDriver+0x31
b1ef4bb4 805d8110 82e0c828 82ec08b0 b1ef4c04 nt!IopfCallDriver+0x31
b1ef4bc4 805d7e02 82ec08b0 82f707b0 82f7091c nt!RawReadWriteDeviceControl+0x60
b1ef4c04 804ef19f 82ec07f8 82f707b0 82f707b0 nt!RawDispatch+0x114
b1ef4c14 b7ec609e 82f707b0 8aabf2e0 868d6338 nt!IopfCallDriver+0x31
b1ef4c40 804ef19f 82e0c828 82f707b0 806e7410 fltMgr!FltGetIrpName+0x12e0
b1ef4c50 8057f98e 82f7091c 868d6338 82f707b0 nt!IopfCallDriver+0x31
b1ef4c64 8058081d 82e0c828 82f707b0 868d6338 nt!IopSynchronousServiceTail+0x70
b1ef4d00 80579298 000013a8 00000000 00000000 nt!IopXxxControlFile+0x5c5
b1ef4d34 8054167c 000013a8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b1ef4d34 7c90e514 000013a8 00000000 00000000 nt!KiFastCallEntry+0xfc
09b3a340 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
RDUMMY+4e9
b86714e9 c6410a01 mov byte ptr [ecx+0Ah],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: RDUMMY+4e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDUMMY
IMAGE_NAME: RDUMMY.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47242fec
FAILURE_BUCKET_ID: 0x50_RDUMMY+4e9
BUCKET_ID: 0x50_RDUMMY+4e9
Followup: MachineOwner
---------
So i'm assuming it's a driver problem with rdummy.sys caused by my antivirus (avast). Is there any way to fix this? Thanks .