RAM on the qvl simply means that the motherboard vendor tested that particular kit and found it to work. A kit not on the qvl doesn't mean it won't work, it just hasn't been tested.
What kit do you have again?
RAM on the qvl simply means that the motherboard vendor tested that particular kit and found it to work. A kit not on the qvl doesn't mean it won't work, it just hasn't been tested.Okay so heres a question - there are no white RGB RAM kits that are listed on the QVL to get me to 64GB, and none that have native EXPO
What are my options?
Is there a way to manually find the right timings or settings to use this RAM? is it a problem to not use the approved RAM?
I am using the most recent BIOS, and everything is now back to default except EXPO is on. So far, the computer seems to be functioning normal.. also yes i am A2/B2 for the RAM. my memory kit is F5-6000J3036G32GX2-TZ5NRWIt should be A2/B2 for the RAM.
What BIOS are you using? And is everything back to default settings or have you changed anything in BIOS?
Maybe try this instead? https://www.techpowerup.com/memtest64/-is there utility in running memtest86 overnight?
Not sure. memtest64 is just more convenient as you can run it in Windows and let it keep running I guess while you browse the internet and stuff. Could do it for a few days like that without losing access to your PC.is there any major difference between memtest86 or 86+ or memtest64?
Log Name: System
Source: Application Popup
Date: 8/28/2024 9:23:38 AM
Event ID: 26
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: A-PC
Description:
Application popup: explorer.exe - Application Error : The instruction at 0x00007FFA51623FAA referenced memory at 0x0000000000000024. The memory could not be written.
Click on OK to terminate the program
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Popup" Guid="{47bfa2b7-bd54-4fac-b70b-29021084ca8f}" />
<EventID>26</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2024-08-28T13:23:38.2156449Z" />
<EventRecordID>7354</EventRecordID>
<Correlation />
<Execution ProcessID="1176" ThreadID="21456" />
<Channel>System</Channel>
<Computer>A-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Caption">explorer.exe - Application Error</Data>
<Data Name="Message">The instruction at 0x00007FFA51623FAA referenced memory at 0x0000000000000024. The memory could not be written.
Click on OK to terminate the program</Data>
</EventData>
</Event>Found this on Reddit regarding this error, although the user got it during shutdown after playing games.Code:Log Name: System Source: Application Popup Date: 8/27/2024 12:17:22 PM Event ID: 26 Task Category: None Level: Information Keywords: User: SYSTEM Computer: A-PC Description: Application popup: explorer.exe - Application Error : The instruction at 0x00007FFB7A2A3FAA referenced memory at 0x0000000000000024. The memory could not be written. Click on OK to terminate the program Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Popup" Guid="{47bfa2b7-bd54-4fac-b70b-29021084ca8f}" /> <EventID>26</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2024-08-27T16:17:22.6989898Z" /> <EventRecordID>4431</EventRecordID> <Correlation /> <Execution ProcessID="1300" ThreadID="18956" /> <Channel>System</Channel> <Computer>A-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="Caption">explorer.exe - Application Error</Data> <Data Name="Message">The instruction at 0x00007FFB7A2A3FAA referenced memory at 0x0000000000000024. The memory could not be written. Click on OK to terminate the program</Data> </EventData> </Event>
This is the error from event viewer. happens only on log off or shutdown, intermittently.
Well - ill say this. i turned off the service and then shut down. and no error. ill keep testing, and if i notice the error again ill keep disabling it before reboot and see if that prevents the error.Found this on Reddit regarding this error, although the user got it during shutdown after playing games.
For anyone having this issues just got to disable "gaming input services" in services.msc and you still can use your controller everything works fine and no errors when restarting or shutting down
If you set it to disable it shouldn't run anymore so this should be a long term fix. Here's a link to the reddit thread:Well - ill say this. i turned off the service and then shut down. and no error. ill keep testing, and if i notice the error again ill keep disabling it before reboot and see if that prevents the error.
if that is in fact the error, is there any way to long term fix or troubleshoot this? or is it pending a microsoft update.
They should be called breakdates. I block them through DNS and only apply the ones that matter manually.updates from windows
Try a different uefi version until you find one that works reliably. When I first setup my AMD it took three different versions to find the one that worked best. Besides the reboot issue it might untangle other issues.DRAM light but if i manually power cycle that it loads.
Thanks for suggestion...uhh, how do I do that?Try a different uefi version until you find one that works reliably. When I first setup my AMD it took three different versions to find the one that worked best. Besides the reboot issue it might untangle other issues.
Just download older versions of the BIOS and "update" the BIOS through the normal process.Thanks for suggestion...uhh, how do I do that?
will have to do that when i have a touch more timeJust download older versions of the BIOS and "update" the BIOS through the normal process.
Dang, that sucks about your Lian Li controllers. Hopefully they get you squared away quickly. You might be able to connect them to a fan header in the interim if they stop working again? I don't believe there is a way to downgrade the firmware since you don't get to choose a file.will have to do that when i have a touch more time
as an aside - the new TL controller i installed is no longer recognized by l connect or windows.
a brief search on reddit though suggests its related to the newest l connect software and firmware updates that were pushed through (which i stupidly did) and now my second TL fan controller and fans are not working . i sent a message to lian li though. this seems like a wide spread issue.
DOes anyone know how to downgrade TL controller/L connect software?
interesting, i tried to downgrade to 2.0.17, and ran the L connect 3 clear software, and rebooted. this did not remove L connect 2.018 but now my fans are working again.. still in 2.0.18
Pics? Nuh uh. He's got a fancy card with an LED. I want a video!And of course we want to see pics! Share whatever you want!
Yeah, I don’t think there’s a way to downgrade the firmware but you can downgrade to 2.0.17 software which the company company is offering right now because they realize there is at least some sort of issue… I did not end up doing that since the fans now seem to be working after running the L3 clear but this might be a temporary fix. I did file a support request with the company to at least get one of my controllers replacedDang, that sucks about your Lian Li controllers. Hopefully they get you squared away quickly. You might be able to connect them to a fan header in the interim if they stop working again? I don't believe there is a way to downgrade the firmware since you don't get to choose a file.
And of course we want to see pics! Share whatever you want!
Can you think of some game benchmark that will run faster than realtime? That would be fun to see. Like something you used to run a decade ago and run it on your rig and it just goes whoosh whoosh done!are there any benchmarks that I should run?