Burnin test V9.2(1001) Memory test fail

[Eric_Lin]

Hi

I've used Burnintest V9.2(1001)

Run three software at the same time for 12 hours,
1.intel TAT tool CPU loading to 80%
2.Play 1080p HD video in Media player
3.Burnin test default mode and add 3D Graphics

The test result will be memory failure ,Burn in tool shows the 0xc0000005 memory exception in logging.


Configuration:
OS: Win10 Pro 20H2
CPU: intel RKL I7
RAM: DDR4 3200 Hynix 4G (only fail 4G & 4G+4G if 8G or 8G+8G pass)

[David (PassMark)]

BurnInTest already does CPU test and video playback.
Adding more CPU load and more video playback tests (running at the same time) isn't likely to increase the load on the system.
i.e. if you already have 100% load on the CPU, then you can't have 200% CPU load by running even more software at the same time. No more testing gets down, everything just runs slower.

See this post for background information
https://www.passmark.com/support/bur...uty_cycles.php

We've got not idea what Intel TAT tool does internally, or how much RAM it uses.
But what is sure is that 4GB of RAM is no longer enough RAM to run Windows 10. Yes 4GB is enough to boot Windows up and load up 1 browser tab. But any serious application will fail with 4GB. This is partially because 300MB of the RAM is used by UEFI BIOS and memory mapped hardware, 1GB of that 4GB is likely used as video RAM and partially because Windows and all applications now use a lot more RAM than 10 years ago. Google Chrome with a few tabs can use 2GB by itself. So there is nearly no free RAM after booting the machine.

We would need need to see the debug logs from BurnInTest to comment on the specific RAM error you had (Turn on Log Level 2 from the BurnIntest preferences window).

[Eric_Lin]

Hi David,

Thanks for your reply, i will provide error log to you.

I've a question, how to Turn on Log Level 2 ?

Thanks!

[David (PassMark)]

You can turn on Log Level 2 from the BurnIntest preferences window (on the logging tab).

[Eric_Lin]

Update debug & Log Level 2 log Memory error log.zip

[David (PassMark)]

These log entries were near the start of the test run.


LOG NOTE: 2021-03-28 22:05:25, Memory (RAM), System Memory Total: 3822MB, Test RAM allocated 10MB, Available: 580MB, Suggested Delta: 99944448, New Test RAM: 200MB, Activity count: 4, Operations: 20
LOG NOTE: 2021-03-28 22:05:25, Memory (RAM), Mem Total Phys: 3822MB [Available Phys: 580MB], Page: 6886MB [Available Page: 749MB], Total Virt: 134217727MB [Available Virt: 134212926MB], Memory Load: 84

So right at the start we can see that
A) Only 10MB of free RAM is available for available for testing (without crippling the O/S entirely). So really the RAM test is doing nothing as there is no free RAM to test. It is pointless to run a RAM test if there is no available RAM.

B) The paging file is already 6886MB in size, but only 749MB of that paging file is available. So even at the start of testing there is so much pressure on the inadequate 3.8GB of installed RAM that it is swapping heavily to disk.


Then 12 minutes later, near the end of the test run we see this,

LOG NOTE: 2021-03-28 22:17:48, Memory (RAM), System Memory Total: 3822MB, Test RAM allocated 4MB, Available: 537MB, Suggested Delta: 0, New Test RAM: 4MB, Activity count: 1810, Operations: 18400
LOG NOTE: 2021-03-28 22:17:48, Memory (RAM), Mem Total Phys: 3822MB [Available Phys: 537MB], Page: 9213MB [Available Page: 1501MB], Total Virt: 134217727MB [Available Virt: 134212911MB], Memory Load: 85

Here the situation is even more dire. Only 4MB is being tested & the paging file has expanded in size by a 3GB. Meaning something has used even more RAM during these 12 minutes. Of course at this point there is no RAM to use, and you are really using disk space via the paging file. This might point to a buggy device driver or 3rd party application leaking RAM (or just using more and more RAM over time).

There was also this log entry below, from the Windows event log, which I think points to a hardware failure on the PCIe bus. Probably unrelated to the problem you are reporting

LOG NOTE: 2021-03-28 22:21:30, System Event, 1649 - Warning, Event ID: 0x00000011, Source: Microsoft-Windows-WHEA-Logger (Generated time: 2021-03-28 22:21:2
LOG NOTE: 2021-03-28 22:21:30, System Event, 1649 - Description: A corrected hardware error has occurred. Component: Error Source: 4 Primary Bus Device: Function: :: Secondary Bus: Device:Function: :: Primary Device Name:0x101 Secondary Device Name:0x10

And these ones from the O/S, complaining that there isn't enough RAM for several processes (unfortunately Microsoft doesn't document this warning message at all it seems).

LOG NOTE: 2021-03-28 22:08:18, Application Event, 733 - Information, Event ID: 0x000003E9, Source: Windows Error Reporting (Generated time: 2021-03-28 22:08:1
LOG NOTE: 2021-03-28 22:08:18, Application Event, 733 - Description: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: D3D12Test64.exe P2: 0.0.0.0 P3: 10.0.19042.2.0.0 P4: P5: P6: P7: P8: P9: P10: At

LOG NOTE: 2021-03-28 22:13:18, Application Event, 734 - Information, Event ID: 0x000003E9, Source: Windows Error Reporting (Generated time: 2021-03-28 22:13:1
LOG NOTE: 2021-03-28 22:13:18, Application Event, 734 - Description: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: audiodg.exe P2: 10.0.19041.804 P3: 10.0.19042.2.0.0 P4: P5: P6: P7: P8: P9: P10:

LOG NOTE: 2021-03-28 22:18:19, Application Event, 736 - Description: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: bit.exe P2: 9.2.1002.0 P3: 10.0.19042.2.0.0 P4: P5: P6: P7: P8: P9: P10: Attached

[David (PassMark)]

Update: What we are going to do is add a new warning message. Something along the lines of,
"Inadequate free RAM available to run the memory test".

Then log this when the memory test isn't able to allocate at least 100MB of RAM to test. This will make the low RAM situation more obvious to the technician running the tests. Even 100MB of 4GB is only 2% of the RAM being directly tested.

[Eric_Lin]

Thank you very much for your analysis and reply!

[ericcompal]

Hi David :
I have same issue like this case, could you take a look my log ?
Thanks

Eric

[David (PassMark)]

Yep, found the problem in your log. Is kind of obvious as it is exactly the same issue as above.

Memory
Total Physical Memory: 3800MB
Available Physical Memory: 1469MB

3.8GB of RAM is below the minimum required to run Win10 or Win11.
Especially when you only have 1.4GB Free after booting.
This is especially comical as you are running a fairly new high end CPU. But the machine would basically be unusable. I hope you aren't selling this machine to the public.

And you are using an old version of BurnInTest.

Try V10 of BurnInTest with a reasonable amount of RAM.

[ericcompal]

Thank you for help , David.