Does MemTest perform quickly with limited RAM but struggles on higher memory?

F5F Stay Refreshed Hardware Desktop Does MemTest perform quickly with limited RAM but struggles on higher memory?

Does MemTest perform quickly with limited RAM but struggles on higher memory?

Does MemTest perform quickly with limited RAM but struggles on higher memory?

L

Lapeluche
Member

211

11-18-2025, 02:37 AM

#1

So you're running memtest to check your RAM, but you're encountering a BSOD with the message "IRQL_ Not_ Less_ or_ Equal" while downloading Wi-Fi drivers. Some people claim this is due to faulty RAM. You mentioned that one stick finished in about 15 minutes and another took 30 minutes. Is this typical? Should you return the stick or try a different slot? It triggered the BSOD specifically when downloading only Wi-Fi drivers.

L

Lapeluche

11-18-2025, 02:37 AM #1

So you're running memtest to check your RAM, but you're encountering a BSOD with the message "IRQL_ Not_ Less_ or_ Equal" while downloading Wi-Fi drivers. Some people claim this is due to faulty RAM. You mentioned that one stick finished in about 15 minutes and another took 30 minutes. Is this typical? Should you return the stick or try a different slot? It triggered the BSOD specifically when downloading only Wi-Fi drivers.

W

Waffley_1254
Member

227

11-19-2025, 09:27 AM

#2

Here are the details of your build:

- CPU: [Insert CPU info]
- CPU cooler: [Insert cooler info]
- Motherboard: [Insert motherboard model]
- RAM: [Insert RAM details]
- SSD/HDD: [Insert storage info]
- GPU: [Insert GPU info]
- PSU: [Insert power supply info]
- Chassis: [Insert chassis name]
- OS: [Insert operating system]
- Monitor: [Insert monitor details]
- PSU age: [Include age and make/model]
- BIOS version: [Current BIOS version]
- Motherboard PCB labeling: [Yes/No]
- RAM slot A2 and B2: [Yes/No]
- RAM speed variation: [Describe if faster in one slot]
- Driver download issue: [Explain problem with Wi-Fi drivers]
- Driver download source: [Specify where to download from]

W

Waffley_1254

11-19-2025, 09:27 AM #2

Here are the details of your build:

- CPU: [Insert CPU info]
- CPU cooler: [Insert cooler info]
- Motherboard: [Insert motherboard model]
- RAM: [Insert RAM details]
- SSD/HDD: [Insert storage info]
- GPU: [Insert GPU info]
- PSU: [Insert power supply info]
- Chassis: [Insert chassis name]
- OS: [Insert operating system]
- Monitor: [Insert monitor details]
- PSU age: [Include age and make/model]
- BIOS version: [Current BIOS version]
- Motherboard PCB labeling: [Yes/No]
- RAM slot A2 and B2: [Yes/No]
- RAM speed variation: [Describe if faster in one slot]
- Driver download issue: [Explain problem with Wi-Fi drivers]
- Driver download source: [Specify where to download from]

F

finnster20
Member

161

11-26-2025, 10:17 PM

#3

So I'm running a CPU7800x3d, GPU7800xt, and using an expert 16x2 DDR5 RAM at 6000MHz with a 30-30 clock speed. My motherboard is from Mobo Gigabyte Elite Rev 1.2. I have a 2TB SSD and a 1TB Samsung SSD. The operating system is Windows 11. My power supply is an Lian Li Edge model at 850W. I installed it last year. I'm connecting to slot 2 and 4. I get the Wi-Fi drivers from the official support site and also use Gigabyte Control Center.

F

finnster20

11-26-2025, 10:17 PM #3

So I'm running a CPU7800x3d, GPU7800xt, and using an expert 16x2 DDR5 RAM at 6000MHz with a 30-30 clock speed. My motherboard is from Mobo Gigabyte Elite Rev 1.2. I have a 2TB SSD and a 1TB Samsung SSD. The operating system is Windows 11. My power supply is an Lian Li Edge model at 850W. I installed it last year. I'm connecting to slot 2 and 4. I get the Wi-Fi drivers from the official support site and also use Gigabyte Control Center.

F

FikarXD
Member

193

11-27-2025, 12:14 AM

#4

And the pace was quick during the first test, yet it dropped significantly afterward. The BSOD left me uncertain whether it was a motherboard issue, so I reached out to Gigabyte support for clarification.

F

FikarXD

11-27-2025, 12:14 AM #4

And the pace was quick during the first test, yet it dropped significantly afterward. The BSOD left me uncertain whether it was a motherboard issue, so I reached out to Gigabyte support for clarification.