Question Can skipped A1 & B1 RAM slots cause BSOD errors?

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Hi everyone. I have built a new PC recently, but since then I have got a lot of random BSOD errors. Most of the errors mention the VBoxNetLwf driver: The driver detected an internal driver error on \Device\VBoxNetLwf, but some of the error messages mention some BugCheck The bugcheck was: 0x0000001a
When I was building the PC the CPU fan was blocking access to the A1 RAM slot, so I installed two RAM sticks to the A2 and B2 slots. May this be the cause of the random BSOD errors?
This's the error events file, this zip archive contains two dmp files from C;\Windows\minidump and this is the System Info file

 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Update: I uninstalled the VirtualBox and the system is still crashing with the following error: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041792, 0xfffff2000003e468, 0x0000001000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
 
Last edited:
Your motherboard manual will tell you where two ram sticks should be installed.
There should be one stick per channel.
I so not know in your case if a2/b2 represents different channels.

Depending on the motherboard, the other two slots may be ok.

I suspect ram is not your issue.

Run memtest86.
It boots from a usb stick and does not use windows.
You can download the free edition here:
https://www.memtest86.com/download.htm

If you can run a full pass with NO errors, your ram should be ok.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Thank you for the reply. Here's is the manual for my motherboard. It doesn't say anything whether the RAM sticks should be installed into the A1 and B1 slots or A1 and A2, but from the motherboard layout diagram as I understand it I installed the RAM sticks in the correct set of slots. Here's the except about the RAM:


Part list:
  • CPU: AMD Ryzen 5 1600 (14nm) 3.2 GHz 6-Core Processor
  • Motherboard: ASRock B450M PRO4-f Micro ATX AM4 Motherboard
  • Memory: Corsair 8 GB (1 x 8 GB) DDR4-2133 CL15 Memory
  • Memory: Corsair 8 GB (1 x 8 GB) DDR4-2133 CL15 Memory
  • Storage: Seagate Barracuda Compute 500 GB 3.5" 7200RPM Internal Hard Drive
  • Power Supply: Thermaltake Toughpower GX1 RGB 500 W 80+ Gold Certified ATX Power Supply
  • Video Card: EVGA GeForce GT 620 1 GB
Today I scanned my HDD disk and not a single bad sector was found.
Tomorrow I will start the memory test to run while I'm at work. If it's not because of the RAM sticks, then I'm really running out of guesses. If ram is not the problem then what else can it be?
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
The only setting I'm aware of is the SVM mode that I have enabled in the BIOS. The problem is still persist even after I uninstalled Virtual Machine though. It happens very randomly someday it crashes few times in a row another day it may crash only once and sometimes it doesn't crash throughout a whole day of using my PC. I'm really confused.
 
Update: I've run the memtest86 for 9 hours and no errors were found. The system still crashes.
The answer to your original question is that ram is not the cause.

I think the answer will be found in the virtual box app or a patch.
Read this thread:
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
I read the whole discussion and the issue I'm having is really different from what the OP on the other forum has. I don't think the crashes are related to the virtual machine because I was able to run emulators and virtual machines with no issue. The system crashes very randomly even after I deleted the VirtualBox. It may crash while I'm surfing the web or when the PC is on idle. I checked the file system with /sfc scannow and it detected some corrupted files and repaired them. It's strange because I reinstalled the Windows several times because of the constant system crashes. This's almost a fresh windows installation. I installed the Windows from DVD disk. I'm planning to buy a flesh drive in few days and try to install Windows from it, maybe it help...
 
Download and install windows directly from microsoft.
Any other source may contain malware and will not be current.

If you do not have a ssd, it is time to buy one.
You will be very pleased with the new overall quickness.
A 500gb samsung 860 evo should be about $50.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Update: Yesterday I installed and used Ubuntu throughout the whole day without any issue. Today I installed Windows 10 from a flash drive with GPT partition table and the Windows crashed after few hours of using the PC. I have no idea what makes it crash
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
So I was looking for an answer on the web and found a list of supported CPUs by the motherboard. I noticed that the AMD 5 1600(YD1600BBM6IAF) is supported starting from the BIOS version P2.0.

I have installed AMD 5 1600 YD1600BBAFBOX on the system and my BIOS version is p1.60.

As I understood, based on this source, the only difference between the YD1600BBM6IAF and YD1600BBAFBOX part numbers is that the YD1600BBAFBOX is a boxed microprocessor with fan and heatsink, but it basically identical to the YD1600BBM6IAF .
So, my question is: maybe the crashes my system experiences from the first day I built it are because of the outdated BIOS version?I have never updated BIOS before and don't know if I should try to do it. I'm afraid I can damage the motherboard. I would like to hear some advice from experienced people, can the BIOS version be related to the crashes? Is it worth to try to update the BIOS? How risky is this?
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
I have run the memtest86 for 9 hours and it didn't found any errors, but the Windows still crashes with MEMORY_MANAGEMENT (1a) error
Code:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: ffffcf01034263a8
Arg3: 8700001224eeb867
Arg4: ffffe00c1fa47c30

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3608

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-3MF977B

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 20178

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 74

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41201

BUGCHECK_P2: ffffcf01034263a8

BUGCHECK_P3: 8700001224eeb867

BUGCHECK_P4: ffffe00c1fa47c30

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Microsoft.Visual

STACK_TEXT:  
ffffa309`0f717548 fffff806`20a2ae68     : 00000000`0000001a 00000000`00041201 ffffcf01`034263a8 87000012`24eeb867 : nt!KeBugCheckEx
ffffa309`0f717550 fffff806`208c6991     : ffffcf01`034263b0 87000012`24eeb867 00000000`00000002 ffffcf67`8081a130 : nt!MiGetPageProtection+0x164f18
ffffa309`0f7175c0 fffff806`208b7e34     : ffffe00c`1c2619c0 00000206`84c00000 00000206`98000000 00000000`001fffff : nt!MiQueryAddressState+0x5c1
ffffa309`0f7177e0 fffff806`20e04eb7     : ffffa309`00000000 00000206`00000004 ffffa309`00000004 00000050`00000001 : nt!MiQueryAddressSpan+0x1d4
ffffa309`0f7178a0 fffff806`20e04955     : ffffc9eb`2c7e1225 00000000`00000000 00000000`10000000 00000050`9936f1f0 : nt!MmQueryVirtualMemory+0x557
ffffa309`0f717a40 fffff806`209d5358     : ffffe00c`14abdd20 00000000`00000000 00000000`77566d4d ffffa309`0f717a00 : nt!NtQueryVirtualMemory+0x25
ffffa309`0f717a90 00007ffb`c61dcb54     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000050`9936efb8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`c61dcb54


SYMBOL_NAME:  nt!MiGetPageProtection+164f18

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.1198

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  164f18

FAILURE_BUCKET_ID:  0x1a_41201_nt!MiGetPageProtection

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c1fe3b27-3ba8-d99e-656f-85f3d58dc669}

Followup:     MachineOwner
 
the only difference between the YD1600BBM6IAF and YD1600BBAFBOX part numbers is that the YD1600BBAFBOX is a boxed microprocessor with fan and heatsink, but it basically identical to the YD1600BBM6IAF
No, that's not the difference.
The model number differs by a letter and there's a fundamental difference between the 2 chips.

The model ending in AE (which is the one you have) is the the first gen Ryzen 5 1600 based on the 14nm Zen architecture. The one ending in AF is the Ryzen 5 1600AF which is based on the 12nm Zen+ architecture... basically the 1600AF is a slightly downclocked Ryzen 5 2600.

That is also the reason why the 1600AF needs a BIOS update to work with the board... if you had an earlier version of the BIOS (like the P1.60 you mentioned) with it you wouldn't even be able to POST, let alone getting into Windows with the AF.

Just wanted to clear that up for you. As far as the minidumps go, maybe some guys with more experience on these might chime in.

EDIT: Have you tried the memory modules individually (each one of them separately) ?
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Thanks for clarification the @ChumP .
The model ending in AE (which is the one you have) is the the first gen Ryzen 5 1600 based on the 14nm Zen architecture
The CPU-Z says that my CPU uses 12nm Technology.
Doesn't it mean that the CPU is based on the Zen+ microarchitecture? Even the core's name (Pinnacle Ridge) is the same as in the list.
Have you tried the memory modules individually (each one of them separately)
Not yet, but I'm planning to do so. I have some suspicions that the GPU is also be might related somehow to these crashes.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
I disabled the Secure Boot and NX Bit options in the BIOS settings and since then my PC hasn't crashed for two days. I think I solved the issue.
 

ASK THE COMMUNITY

TRENDING THREADS