Randomly...but mostly while gaming i have been getting BSODs, P.F.N.P.A. and pointing to something called amdlog.sys. I have been to the 10th page of google trying to finger this out but no luck. According to what im reading, the culprit is AMDLOG.sys. Another issue thats going on is the screen will go black and the mouse and keyboard will just shut off. The pc will remain on (lit up) but requires a reset. Can anyone shed any light on this? Thanks in advance!
cpu= ryzen 5 2600,
gpu = rx 590,
16gb mushkin ram (2933) currently @2800
1tb mushkin ssd,
1tb hdd,
mb = msi b450 gaming plus on win10 machine.
water cooled
I ran the minidump through windbg and this is what it says.
PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffff9f0c53312064, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff80070fc8271, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec Value: 2
Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-AL6752P
Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject
Key : Analysis.Elapsed.Sec Value: 2
Key : Analysis.Memory.CommitPeak.Mb Value: 69
Key : Analysis.System Value: CreateObject
ADDITIONAL_XML: 1
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 50
BUGCHECK_P1: ffff9f0c53312064
BUGCHECK_P2: 0
BUGCHECK_P3: fffff80070fc8271
BUGCHECK_P4: 2
READ_ADDRESS: fffff8006c3733b8:
Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8006c22a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006c22a3d8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff9f0c53312064
MM_INTERNAL_CODE: 2
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffeb08ea71d3c0 -- (.trap 0xffffeb08ea71d3c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000004ab02054 rbx=0000000000000000 rcx=ffff9f0c095af200 rdx=ffff9f0c08810010 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80070fc8271 rsp=ffffeb08ea71d550 rbp=ffffeb08ea71d5f8 r8=ffffeb08ea71d5f8 r9=0000000000989680 r10=00000000002000a0 r11=fffff780000003b0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe nc
amdlog+0x8271:
fffff800`70fc8271 393c10 cmp dword ptr [rax+rdx],edi ds:ffff9f0c`53312064=????????
Resetting default scope
STACK_TEXT:
ffffeb08`ea71d118 fffff800`6c02dd34 : 00000000`00000050 ffff9f0c`53312064 00000000`00000000
ffffeb08`ea71d3c0 : nt!KeBugCheckEx ffffeb08`ea71d120 fffff800`6bec91af : 00000000`00501802 00000000`00000000 00000000`00000000 ffff9f0c`53312064 : nt!MiSystemFault+0x195c94 ffffeb08`ea71d220 fffff800`6bfd041e : 00000000`00120112 fffff800`70fc9884 00000000`0000022e ffff9f0c`0958c800 : nt!MmAccessFault+0x34f ffffeb08`ea71d3c0 fffff800`70fc8271 : 00000000`0000009a ffff9f0c`095af040 00000000`00000000 ffff9f0c`095af618 : nt!KiPageFault+0x35e ffffeb08`ea71d550 00000000`0000009a : ffff9f0c`095af040 00000000`00000000 ffff9f0c`095af618 ffff9f0c`02478180 : amdlog+0x8271 ffffeb08`ea71d558 ffff9f0c`095af040 : 00000000`00000000 ffff9f0c`095af618 ffff9f0c`02478180 fffff800`70fc5bc4 : 0x9a ffffeb08`ea71d560 00000000`00000000 : ffff9f0c`095af618 ffff9f0c`02478180 fffff800`70fc5bc4 ffff9f0c`095af618 : 0xffff9f0c`095af040
SYMBOL_NAME: amdlog+8271
MODULE_NAME: amdlog
IMAGE_NAME: amdlog.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 8271
FAILURE_BUCKET_ID: AV_R_INVALID_amdlog!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6ec2f481-7981-8474-65eb-29e2712ed790}
Followup: MachineOwner
guess no one will touch this with a 50 foot pole
I have not seen many AMD users with Muskin, Corsair and G.Skill memory seem to be the best choice. I use the G.Skill Flare X which is targeted for Ryzen
Go to your BIOS and reset the RAM settings. The problem will be solved. If you are going to do RAM OC, try increasing CL values with BIOS RAM timing settings.
I did just that last night as well as reseat the ram. So far it has not happened again even after a 6 hour marathon of cities skylines on max settings. This issue is very random, so i wont know if it fixed it for a while. Ill post if the issue continues or goes away. Also, i have already replaced the PS with a 700 watt unit, this did not help.
Are the RAMs connected to the correct DIMMs? Has the system been tried with single module RAM? What is the CPU max. temperature? Is the AMD driver with errors removed and tried a different version? Is the motherboard BIOS up to date?
Yes running dual chan, tried removing/swapping sticks
Cpu is running stock at this time. When i set it up to run my ram @ 2933, system unstable (mb supports 2933). Its not at stock speeds but had to run the ram at 2800 which was stable. Cpu temps are 28c to 64c max. max 64c running furmark cpu burner.
i am unaware of an amd driver with errors. which driver are we talking about?
MB bios is indeed up to date.
Reduce the RAMs speed. Some RAMs lose their high OC capacity when running dual mode. The reason for the system error is the RAMs with high probability. Also the error message you got is a sign of a hardware problem not a driver problem.
I took the time to look over the specs before I moved into the X570 and made sure the RAM was perfect for my R5 3600
G.Skill Flare X is aimed at Ryzen users and it works fine on my X570-A PRO at the DDR4-3200 speed my CPU supports
Seems hardly worth the hassle to fiddle with memory timing when getting the right product eliminates problems
if yall are sure that grabbing the gskill ram will fix this... im good to try it. something of interest though... while this pc is having issues, its sister pc (exact same specs and hardware) has no issues at all. i would be swapping parts in tween em but the issue im having is random and can go a month before it starts acting up. ill try the gskill and see what happens.
I tested my G.Skill Flare X RAM on my MSI X470 Gaming Plus and it works fine on that board.
The speed is obviously dependant on the CPU installed.
i have it set to factory defaults in bios now. ram is running at something like 2400 or something like that.
what speed ram should i choose? 2933, 3000, 3200....3400?? cpu r5-2600 . as it stands if i try to use my mushkin 2933 @ 2933, the system is unstable.
damname wrote:
what speed ram should i choose? 2933, 3000, 3200....3400?? cpu r5-2600 . as it stands if i try to use my mushkin 2933 @ 2933, the system is unstable.
According to the AMD CPU manual the R5 2600 is designed for DDR4-2933. If the RAM cannot do that speed it may not have XMP or complete JEDEC speeds.
ordered... waiting
used the ram config @gskill to make sure it all lined up.
The maximum RAM speeds specified by the processor and by the motherboard may be different. Your motherboard has 3200 support.
damname wrote:
G.SKILL Flare X Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) AMD X370 / B350 Memory (Desktop Memory) Model F4-3200C14D-16GFX
ordered... waiting
used the ram config @gskill to make sure it all lined up.
I use that for my X570 and R5 3600 CPU, very stable on default settings
ram just came and i slapped it in and set the xmp profile to 3200. it detected the correct timings and all that. booted the pc and opened msi command center which is reporting the dram freq @ 2400. opened task manager and it is also reporting the freq at 2400. restarted the pc and checked the settings in bios....all is well. restarted again and booted into win10 and its still reporting the ram at 2400 with incorrect timings. not sure what im doing wrong here. been checking google and no joy on this. anyone?
i have the latest bios version btw.
damname wrote:
ram just came and i slapped it in and set the xmp profile to 3200. it detected the correct timings and all that. booted the pc and opened msi command center which is reporting the dram freq @ 2400. opened task manager and it is also reporting the freq at 2400. restarted the pc and checked the settings in bios....all is well. restarted again and booted into win10 and its still reporting the ram at 2400 with incorrect timings. not sure what im doing wrong here. been checking google and no joy on this. anyone?
i have the latest bios version btw.
CPU and motherboard, also PSU is helpful
its listed in the original post up top.
cpu= ryzen 5 2600,
gpu = rx 590,
1tb crucial ssd, (crucial oops!)
1tb hdd,
mb = msi b450 gaming plus on win10 machine.
water cooled
psu is apevia 700 watt (just replaced a gold cert 600w psu trying to figure this out)
damname wrote:
its listed in the original post up top.
cpu= ryzen 5 2600,
gpu = rx 590,
1tb crucial ssd, (crucial oops!)
1tb hdd,
mb = msi b450 gaming plus on win10 machine.
water cooled
psu is apevia 700 watt (just replaced a gold cert 600w psu trying to figure this out)
Your CPU can support up to DDR4-2933, so my DDR4-3200 would run at DDR4-2933 with your processor.
Try manually setting DDR4-2933 with XMP enabled
i did try xmp 2933. it still reports in windows, cpuz, msi control center and CMD as 2400 with incorrect timings as well. i also tried manually setting it to 3200 and 2933. i save changes and reboot, it reboots....and then reboots again and finally into windows with incorrect settings. i have been trying the stuff i see doing google searches like removing the psu cable and battery and a whole battery of other things.
heres the kicker..... I WAS able to get xmp 2900 with the mushkin redline ram but this flare x..... wondering if i just wasted my money.
try a clean install of windows
tried that already.
FIXED!!! msi customer support is the shiznot! they knew right what to do to fix this. they released a beta version of the bios 4 days ago (6/12/20)... so i dinna have the latest version as i thought. i flashed bios about 3 weeks ago so i thought i had the latest version.
anyway...i flashed to the beta version uploaded on the 12th and XMP works and running stable @3200
.1D0 bios on MY msi b450 gaming plus screwed up ram slot 4 and caused it to bsod even at 2800mhz custom clock with mushkin redline ram rated for 2933. when i installed flare x, the system would default the ram to 2400 no matter what i did. NO XMP profiles or custom clocks would work at all. I flashed to .1E2 and XMP works again and was able to clock at 3200 stable.
thanks for all the help
damname wrote:
FIXED!!! msi customer support is the shiznot! they knew right what to do to fix this. they released a beta version of the bios 4 days ago (6/12/20)... so i dinna have the latest version as i thought. i flashed bios about 3 weeks ago so i thought i had the latest version.
anyway...i flashed to the beta version uploaded on the 12th and XMP works and running stable @3200
.1D0 bios on MY msi b450 gaming plus screwed up ram slot 4 and caused it to bsod even at 2800mhz custom clock with mushkin redline ram rated for 2933. when i installed flare x, the system would default the ram to 2400 no matter what i did. NO XMP profiles or custom clocks would work at all. I flashed to .1E2 and XMP works again and was able to clock at 3200 stable.
thanks for all the help
Sorry I only have sets of G.Skill memory so I know how they work on AMD systems. Far from rich enough to have every make and model.
Still crashing................
AMDLOG.sys is still the issue. heres what who crashed says about it.
crash dump file: C:\WINDOWS\Minidump\081520-7859-01.dmp
This was probably caused by the following module: amdlog.sys (0xFFFFF803223D8271)
Bugcheck code: 0x50 (0xFFFF9601C3CA7263, 0x0, 0xFFFFF803223D8271, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdlog.sys .
Google query: amdlog.sys PAGE_FAULT_IN_NONPAGED_AREA
it always comes back around to this driver or whatever. who do i update amdlog.sys as who crashes recommends?