C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #1 Hello. What a cool site and a great service by knowledgeable folks! I've been building for years and I've never had trouble like this... built a new AM5 computer for my son using a Gigabyte motherboard, Corsair Vengeance Ram and a Ryzen 5 7600X proc and a WD Blue SA510 SSD. After installing a fresh copy of Windows 10 on it it began this death spiral of BSODs. Mostly IRQ_LESS_THAN_EQUAL. I ended up trying 2 more types of ram from 16-32GB... then I swapped the Gigabyte motherboard for a ASRock B650M RS Pro Wifi... reinstalled Windows, still receive bluescreens. We then swapped the memory yet again (making sure the memory and CPU were on the compatibility list of the motherboard. At this point the hardware is as follows: Ryzen 5 7600X AsRock B650 Pro RS Wifi (AM5 mboard) Corsair Vengence CMK32GX5M2B5600C40 2x16 Samsung EVO 1TB SSD 700Watt ThermalTake PSU XFX Radeon RX6600 GPU - All software drivers are current. - SSD Firmware is current - Bios firmware is next to newest release - I've run the system with GPU and on integrated... BSODs happen on both - I've ran the system on a single stick of Ram in slot B2... it still BSODs - I've disabled XMP in the BIOs... running the ram on the default speeds - reseated ram numerous times and reseat and re-applied thermal grease to the CPU at least twice - ran chkdsk and sfc and a memtest... no issues ; ) I've done a lot more than that that I can't think of just yet. The only thing I haven't replaced since the start of this process is the Proc and I'm close to pulling the trigger on a Ryzen 7 Proc. Hoping I don't have to go that route but I just don't trust this build after all this. Attachments SysnativeFileCollectionApp.zip 1.8 MB · Views: 1 Last edited: Mar 11, 2024
Hello. What a cool site and a great service by knowledgeable folks! I've been building for years and I've never had trouble like this... built a new AM5 computer for my son using a Gigabyte motherboard, Corsair Vengeance Ram and a Ryzen 5 7600X proc and a WD Blue SA510 SSD. After installing a fresh copy of Windows 10 on it it began this death spiral of BSODs. Mostly IRQ_LESS_THAN_EQUAL. I ended up trying 2 more types of ram from 16-32GB... then I swapped the Gigabyte motherboard for a ASRock B650M RS Pro Wifi... reinstalled Windows, still receive bluescreens. We then swapped the memory yet again (making sure the memory and CPU were on the compatibility list of the motherboard. At this point the hardware is as follows: Ryzen 5 7600X AsRock B650 Pro RS Wifi (AM5 mboard) Corsair Vengence CMK32GX5M2B5600C40 2x16 Samsung EVO 1TB SSD 700Watt ThermalTake PSU XFX Radeon RX6600 GPU - All software drivers are current. - SSD Firmware is current - Bios firmware is next to newest release - I've run the system with GPU and on integrated... BSODs happen on both - I've ran the system on a single stick of Ram in slot B2... it still BSODs - I've disabled XMP in the BIOs... running the ram on the default speeds - reseated ram numerous times and reseat and re-applied thermal grease to the CPU at least twice - ran chkdsk and sfc and a memtest... no issues ; ) I've done a lot more than that that I can't think of just yet. The only thing I haven't replaced since the start of this process is the Proc and I'm close to pulling the trigger on a Ryzen 7 Proc. Hoping I don't have to go that route but I just don't trust this build after all this.
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #2 Here is my WhoCrashed Log System Information (local) Computer name: DESKTOP-PLD3ALTWindows version: Windows 10, 10.0, version 2009, build: 19045 (x64)Windows dir: C:\WindowsHardware: B650M Pro RS, ASRockCPU: AuthenticAMD AMD Ryzen 5 7600X 6-Core Processor 8664, level: 25Processor count:12 logical processors, active mask: 4095RAM: 31864.9MB Crash Dump Analysis Crash dumps are enabled on your computer. Crash dump directories: C:\Windows C:\Windows\Minidump On Sun 3/10/2024 9:52:00 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump)Bugcheck code: 0xBE(0xFFFFF804C62C0DFF, 0x9000001A4791121, 0xFFFFDB810675FE90, 0xB)Bugcheck name:ATTEMPTED_WRITE_TO_READONLY_MEMORYDriver or module in which error occurred: Program.sys (BEDaisy+0x70DFF)File path:C:\ProgramBug check description:This is issued if a driver attempts to write to a read-only memory segment.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. Google query:bedaisy ATTEMPTED_WRITE_TO_READONLY_MEMORY On Sun 3/10/2024 5:52:17 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4390-01.dmp (Minidump)Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF803672FB320, 0x0)Bugcheck name:DPC_WATCHDOG_VIOLATIONDriver or module in which error occurred: amdppm.sys (amdppm+0x2fa7)File path:C:\Windows\System32\drivers\amdppm.sysDescription: Processor Device DriverProduct: Microsoft® Windows® Operating SystemCompany: Microsoft CorporationBug check description:The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis:This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Sun 3/10/2024 9:52:00 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-5656-01.dmp (Minidump)Bugcheck code: 0xBE(0xFFFFF804C62C0DFF, 0x9000001A4791121, 0xFFFFDB810675FE90, 0xB)Bugcheck name:ATTEMPTED_WRITE_TO_READONLY_MEMORYDriver or module in which error occurred: Program.sys (BEDaisy+0x70DFF)File path:C:\ProgramBug check description:This is issued if a driver attempts to write to a read-only memory segment.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. Google query:bedaisy ATTEMPTED_WRITE_TO_READONLY_MEMORY On Sun 3/10/2024 9:30:12 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4984-01.dmp (Minidump)Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF807450FB320, 0x0)Bugcheck name:DPC_WATCHDOG_VIOLATIONDriver or module in which error occurred: amdppm.sys (amdppm+0x2fa7)File path:C:\Windows\System32\drivers\amdppm.sysDescription: Processor Device DriverProduct: Microsoft® Windows® Operating SystemCompany: Microsoft CorporationBug check description:The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis:This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Sun 3/10/2024 8:40:03 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4796-01.dmp (Minidump)Bugcheck code: 0xA(0x10, 0x2, 0x0, 0xFFFFF8026839CAD3)Bugcheck name:IRQL_NOT_LESS_OR_EQUALBug check description:This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. On Sun 3/10/2024 8:32:17 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4562-01.dmp (Minidump)Bugcheck code: 0x3B(0xC0000005, 0xFFFFF8033FC06241, 0xFFFFA6017B7E1920, 0x0)Bugcheck name:SYSTEM_SERVICE_EXCEPTIONBug check description:This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. The following dump file was found but appeared to be corrupt: C:\Windows\LiveKernelReports\PdcLockWatchdog-20240310-2130.dmp
Here is my WhoCrashed Log System Information (local) Computer name: DESKTOP-PLD3ALTWindows version: Windows 10, 10.0, version 2009, build: 19045 (x64)Windows dir: C:\WindowsHardware: B650M Pro RS, ASRockCPU: AuthenticAMD AMD Ryzen 5 7600X 6-Core Processor 8664, level: 25Processor count:12 logical processors, active mask: 4095RAM: 31864.9MB Crash Dump Analysis Crash dumps are enabled on your computer. Crash dump directories: C:\Windows C:\Windows\Minidump On Sun 3/10/2024 9:52:00 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump)Bugcheck code: 0xBE(0xFFFFF804C62C0DFF, 0x9000001A4791121, 0xFFFFDB810675FE90, 0xB)Bugcheck name:ATTEMPTED_WRITE_TO_READONLY_MEMORYDriver or module in which error occurred: Program.sys (BEDaisy+0x70DFF)File path:C:\ProgramBug check description:This is issued if a driver attempts to write to a read-only memory segment.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. Google query:bedaisy ATTEMPTED_WRITE_TO_READONLY_MEMORY On Sun 3/10/2024 5:52:17 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4390-01.dmp (Minidump)Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF803672FB320, 0x0)Bugcheck name:DPC_WATCHDOG_VIOLATIONDriver or module in which error occurred: amdppm.sys (amdppm+0x2fa7)File path:C:\Windows\System32\drivers\amdppm.sysDescription: Processor Device DriverProduct: Microsoft® Windows® Operating SystemCompany: Microsoft CorporationBug check description:The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis:This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Sun 3/10/2024 9:52:00 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-5656-01.dmp (Minidump)Bugcheck code: 0xBE(0xFFFFF804C62C0DFF, 0x9000001A4791121, 0xFFFFDB810675FE90, 0xB)Bugcheck name:ATTEMPTED_WRITE_TO_READONLY_MEMORYDriver or module in which error occurred: Program.sys (BEDaisy+0x70DFF)File path:C:\ProgramBug check description:This is issued if a driver attempts to write to a read-only memory segment.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. Google query:bedaisy ATTEMPTED_WRITE_TO_READONLY_MEMORY On Sun 3/10/2024 9:30:12 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4984-01.dmp (Minidump)Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF807450FB320, 0x0)Bugcheck name:DPC_WATCHDOG_VIOLATIONDriver or module in which error occurred: amdppm.sys (amdppm+0x2fa7)File path:C:\Windows\System32\drivers\amdppm.sysDescription: Processor Device DriverProduct: Microsoft® Windows® Operating SystemCompany: Microsoft CorporationBug check description:The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis:This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Sun 3/10/2024 8:40:03 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4796-01.dmp (Minidump)Bugcheck code: 0xA(0x10, 0x2, 0x0, 0xFFFFF8026839CAD3)Bugcheck name:IRQL_NOT_LESS_OR_EQUALBug check description:This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. On Sun 3/10/2024 8:32:17 PM your computer crashed or a problem was reported Crash dump file: C:\Windows\Minidump\031024-4562-01.dmp (Minidump)Bugcheck code: 0x3B(0xC0000005, 0xFFFFF8033FC06241, 0xFFFFA6017B7E1920, 0x0)Bugcheck name:SYSTEM_SERVICE_EXCEPTIONBug check description:This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver. The following dump file was found but appeared to be corrupt: C:\Windows\LiveKernelReports\PdcLockWatchdog-20240310-2130.dmp
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #3 Here's my BlueScreenView log Dump FileCrash TimeBug Check StringBug Check CodeParameter 1Parameter 2Parameter 3Parameter 4Caused By DriverCaused By AddressFile DescriptionProduct NameCompanyFile VersionProcessorCrash AddressStack Address 1Stack Address 2Stack Address 3Computer NameFull PathProcessors CountMajor VersionMinor VersionDump File SizeDump File Time031024-5656-01.dmp3/10/2024 9:52:00 PMATTEMPTED_WRITE_TO_READONLY_MEMORY0x000000befffff804`c62c0dff09000001`a4791121ffffdb81`0675fe9000000000`0000000bBEDaisy.sysBEDaisy.sys+70dff x64ntoskrnl.exe+3fd5b0 C:\Windows\Minidump\031024-5656-01.dmp1215190411,281,1803/10/2024 9:52:30 PM031024-4984-01.dmp3/10/2024 9:30:12 PM 0x0000013300000000`0000000100000000`00001e00fffff807`450fb32000000000`00000000ntoskrnl.exentoskrnl.exe+3fd5b0 x64ntoskrnl.exe+3fd5b0 C:\Windows\Minidump\031024-4984-01.dmp1215190414,941,1083/10/2024 9:30:43 PM031024-4796-01.dmp3/10/2024 8:40:03 PMIRQL_NOT_LESS_OR_EQUAL0x0000000a00000000`0000001000000000`0000000200000000`00000000fffff802`6839cad3ntoskrnl.exentoskrnl.exe+3fd5b0 x64ntoskrnl.exe+3fd5b0 C:\Windows\Minidump\031024-4796-01.dmp1215190411,368,9883/10/2024 8:40:33 PM031024-4562-01.dmp3/10/2024 8:32:17 PMSYSTEM_SERVICE_EXCEPTION0x0000003b00000000`c0000005fffff803`3fc06241ffffa601`7b7e192000000000`00000000ntoskrnl.exentoskrnl.exe+3fd6f0 x64ntoskrnl.exe+3fd6f0 C:\Windows\Minidump\031024-4562-01.dmp1215190411,680,5483/10/2024 8:32:45 PM031024-4390-01.dmp3/10/2024 5:52:17 PM 0x0000013300000000`0000000100000000`00001e00fffff803`672fb32000000000`00000000ntoskrnl.exentoskrnl.exe+3fd6f0 x64ntoskrnl.exe+3fd6f0 C:\Windows\Minidump\031024-4390-01.dmp1215190414,538,8283/10/2024 5:52:44 PM
Here's my BlueScreenView log Dump FileCrash TimeBug Check StringBug Check CodeParameter 1Parameter 2Parameter 3Parameter 4Caused By DriverCaused By AddressFile DescriptionProduct NameCompanyFile VersionProcessorCrash AddressStack Address 1Stack Address 2Stack Address 3Computer NameFull PathProcessors CountMajor VersionMinor VersionDump File SizeDump File Time031024-5656-01.dmp3/10/2024 9:52:00 PMATTEMPTED_WRITE_TO_READONLY_MEMORY0x000000befffff804`c62c0dff09000001`a4791121ffffdb81`0675fe9000000000`0000000bBEDaisy.sysBEDaisy.sys+70dff x64ntoskrnl.exe+3fd5b0 C:\Windows\Minidump\031024-5656-01.dmp1215190411,281,1803/10/2024 9:52:30 PM031024-4984-01.dmp3/10/2024 9:30:12 PM 0x0000013300000000`0000000100000000`00001e00fffff807`450fb32000000000`00000000ntoskrnl.exentoskrnl.exe+3fd5b0 x64ntoskrnl.exe+3fd5b0 C:\Windows\Minidump\031024-4984-01.dmp1215190414,941,1083/10/2024 9:30:43 PM031024-4796-01.dmp3/10/2024 8:40:03 PMIRQL_NOT_LESS_OR_EQUAL0x0000000a00000000`0000001000000000`0000000200000000`00000000fffff802`6839cad3ntoskrnl.exentoskrnl.exe+3fd5b0 x64ntoskrnl.exe+3fd5b0 C:\Windows\Minidump\031024-4796-01.dmp1215190411,368,9883/10/2024 8:40:33 PM031024-4562-01.dmp3/10/2024 8:32:17 PMSYSTEM_SERVICE_EXCEPTION0x0000003b00000000`c0000005fffff803`3fc06241ffffa601`7b7e192000000000`00000000ntoskrnl.exentoskrnl.exe+3fd6f0 x64ntoskrnl.exe+3fd6f0 C:\Windows\Minidump\031024-4562-01.dmp1215190411,680,5483/10/2024 8:32:45 PM031024-4390-01.dmp3/10/2024 5:52:17 PM 0x0000013300000000`0000000100000000`00001e00fffff803`672fb32000000000`00000000ntoskrnl.exentoskrnl.exe+3fd6f0 x64ntoskrnl.exe+3fd6f0 C:\Windows\Minidump\031024-4390-01.dmp1215190414,538,8283/10/2024 5:52:44 PM
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Mar 11, 2024 #4 Hi! Try to uninstall the software (Battle Eye?) that installs bedaisy.sys in your drivers list. And check if this driver disappears.
Hi! Try to uninstall the software (Battle Eye?) that installs bedaisy.sys in your drivers list. And check if this driver disappears.
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #5 xilolee said: Hi! Try to uninstall the software (Battle Eye?) that installs bedaisy.sys in your drivers list. And check if this driver disappears. Click to expand... So I ran the uninstaller in the Destiny2 folder (the game that required Battle Eye). I've had constant BSODs since. I got on Battle Eye's site and read their FAQ and it looks like their software causes a lot of issues. Their site said that Driver Verifier needed to be disabled on some systems so I double-checked and it is disabled on mine. At this point I can't even get the system to boot... just got a DPC_WATCHDOG_VIOLATION (Which seems to be related to CPU thermal issues), I also tried to run the SysNativeDataCollection App and it BSOD'd in the middle of that. This has to be the worst build I've ever seen. I'm not sure where to go here. The only hardware that hasn't been replaced has been the CPU. I have noticed that when I do try to run most anything on the system if it doesn't BSOD it'll black screen crash. I installed a Bench marking program on it and it was running well... had about 17 passes and the GPU was screaming at 112 FPS and then at about pass 14 the benchmark software crashed out (with no bluescreen). Destiny 2 will start up and run for a bit and then randomly crash out. I understand that the mixture of hardware causes a potent cocktail of software and drivers to be installed on this system but this is about as barebones Windows 10 as it gets. I've reinstalled and wiped the SSD numerous times. I've also ran msconfig, checked to not show Microsoft services and disabled about everything that is starting up. Any ideas? Is there a way to definitively test a CPU to determine if it has issues?
xilolee said: Hi! Try to uninstall the software (Battle Eye?) that installs bedaisy.sys in your drivers list. And check if this driver disappears. Click to expand... So I ran the uninstaller in the Destiny2 folder (the game that required Battle Eye). I've had constant BSODs since. I got on Battle Eye's site and read their FAQ and it looks like their software causes a lot of issues. Their site said that Driver Verifier needed to be disabled on some systems so I double-checked and it is disabled on mine. At this point I can't even get the system to boot... just got a DPC_WATCHDOG_VIOLATION (Which seems to be related to CPU thermal issues), I also tried to run the SysNativeDataCollection App and it BSOD'd in the middle of that. This has to be the worst build I've ever seen. I'm not sure where to go here. The only hardware that hasn't been replaced has been the CPU. I have noticed that when I do try to run most anything on the system if it doesn't BSOD it'll black screen crash. I installed a Bench marking program on it and it was running well... had about 17 passes and the GPU was screaming at 112 FPS and then at about pass 14 the benchmark software crashed out (with no bluescreen). Destiny 2 will start up and run for a bit and then randomly crash out. I understand that the mixture of hardware causes a potent cocktail of software and drivers to be installed on this system but this is about as barebones Windows 10 as it gets. I've reinstalled and wiped the SSD numerous times. I've also ran msconfig, checked to not show Microsoft services and disabled about everything that is starting up. Any ideas? Is there a way to definitively test a CPU to determine if it has issues?
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #6 Even the web browser crashes on this system. I run Brave browser on it and you'll be on a page and the entire screen will disappear and be replaced with "STATUS_ACCESS_VIOLATION", when Brave is in this state Edge will work fine. I think I'll remove Brave and just use Edge... but I've never seen a browser behave this way.
Even the web browser crashes on this system. I run Brave browser on it and you'll be on a page and the entire screen will disappear and be replaced with "STATUS_ACCESS_VIOLATION", when Brave is in this state Edge will work fine. I think I'll remove Brave and just use Edge... but I've never seen a browser behave this way.
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #7 I ran the system on the one ram stick that I hadn't run it solely on yet in slot B2. Everything seemed pretty stable and I was able to run the the benchmark software successfully. I then decided to reinstall Battle Eye and it BSOD'd during installation and I'm in a continuous loop of them just trying to get Windows to start up now.
I ran the system on the one ram stick that I hadn't run it solely on yet in slot B2. Everything seemed pretty stable and I was able to run the the benchmark software successfully. I then decided to reinstall Battle Eye and it BSOD'd during installation and I'm in a continuous loop of them just trying to get Windows to start up now.
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Mar 11, 2024 #8 Try to run the RAM and the CPU at stock settings, i.e. remove any overclocking.
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #9 xilolee said: Try to run the RAM and the CPU at stock settings, i.e. remove any overclocking. Click to expand... As far as I know I have. Everything in bios is set to auto but I did go into the Asrock DRAM settings and there was an option to specify 4800 instead of 5400 (slower), I chose that. I haven't touched any CPU settings.
xilolee said: Try to run the RAM and the CPU at stock settings, i.e. remove any overclocking. Click to expand... As far as I know I have. Everything in bios is set to auto but I did go into the Asrock DRAM settings and there was an option to specify 4800 instead of 5400 (slower), I chose that. I haven't touched any CPU settings.
C cliftyman Member Joined Mar 10, 2024 Posts 9 Mar 11, 2024 #10 I may have been a bit premature but I purchased a Ryzen 5 7600 (65W) Proc. Should be here tomorrow. I've went through 3 different memory configs and two different motherboards with this build. The only thing I haven't replaced through all of it is the processor. I bought the R57600X because of the price and I didn't really read up on it's specs very well. I think the 7600 is more of a cool running, middle-of-the-road CPU...
I may have been a bit premature but I purchased a Ryzen 5 7600 (65W) Proc. Should be here tomorrow. I've went through 3 different memory configs and two different motherboards with this build. The only thing I haven't replaced through all of it is the processor. I bought the R57600X because of the price and I didn't really read up on it's specs very well. I think the 7600 is more of a cool running, middle-of-the-road CPU...
