Jump to content

did you try to reseat your RAM? 

did you try to turn it off and on again?

                   -`                    y0ur5h4d0w@Darkness
                  .o+`                   ------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: Darkness
               `+oooooo:                 Kernel: Latest  
               -+oooooo+:                Packages: Only what i need to keep it simple
             `/:-:++oooo+:               Shell: ZSH
            `/++++/+++++++:              Main Monitor: LG Ultragear LG 27GS85Q 
           `/++++++++++++++:             Secondary Monitor: Asus MG28UQ
          `/+++ooooooooooooo/`           DE: Plasma Always Bleeding Edge  
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
       -osssssso.      :ssssssso.        Icons: Breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: Kitty 
     /ossssssss/        +ssssooo/-       Terminal Font: Noto Color Emoji 17 FreeMono 13 
   `/ossssso+/:-        -:/+osssso+-     CPU: AMD Ryzen 7 9800X3D (16) @ 5.307GHz 
  `+sso+:-`                 `.-/+oso:    GPU: AMD ATI Radeon RX 7800 XT 
 `++:.                           `-/+/   GPU: AMD ATI Radeon Graphics 
 .`                                 `/   Memory: 61830MiB 

 

Link to post
Share on other sites

5 minutes ago, drorsabi1 said:

No

 

Then the signs point to faulty RAM, first try each stick in each slot and see if the BSOD stops, you may just have 1 faulty stick

 

Also, what are your specs?

Console.WriteLine("Hello World!");

Link to post
Share on other sites

there's probably 4 cases which can affect your PC:

1. missing BIOS updates
2. faulty RAM

3. windows files corruption

4. crappy windows update that broke stuff

 

 

in order to troubleshoot you should start from the easy step:

 

as very first try i would check with sfc /scannow and DISM if there's issues with your windows install if this fails,

 

then i would suggest to detach all the disks in your PC, attach a brand new disk and do a clean install of windows and use it for a bit, this would exclude the windows issues, if the system still breaks there's another problem

 

then you should consider check if there's a BIOS update, there's probably something wrong that is fixed

if still the issue persists even after the bios update then you should run a RAM test which can take loooooong time but will address the hardware issue

 

 

 

                   -`                    y0ur5h4d0w@Darkness
                  .o+`                   ------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: Darkness
               `+oooooo:                 Kernel: Latest  
               -+oooooo+:                Packages: Only what i need to keep it simple
             `/:-:++oooo+:               Shell: ZSH
            `/++++/+++++++:              Main Monitor: LG Ultragear LG 27GS85Q 
           `/++++++++++++++:             Secondary Monitor: Asus MG28UQ
          `/+++ooooooooooooo/`           DE: Plasma Always Bleeding Edge  
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
       -osssssso.      :ssssssso.        Icons: Breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: Kitty 
     /ossssssss/        +ssssooo/-       Terminal Font: Noto Color Emoji 17 FreeMono 13 
   `/ossssso+/:-        -:/+osssso+-     CPU: AMD Ryzen 7 9800X3D (16) @ 5.307GHz 
  `+sso+:-`                 `.-/+oso:    GPU: AMD ATI Radeon RX 7800 XT 
 `++:.                           `-/+/   GPU: AMD ATI Radeon Graphics 
 .`                                 `/   Memory: 61830MiB 

 

Link to post
Share on other sites

5 minutes ago, drorsabi1 said:

How do I check RAM if it is taking between 5 minutes to 30 minutes to get bsod 

 

memtest86 and memtest64 are the tools to use OR as @Blasty Blosty said, you can boot the system with just one single ram stick at the time and check if it works fine untill the system crash with a specific ram stick inserted

 

however, i would go for memtest86 since memtest64 is used inside windows and if the system crash you won't be able to fully test the ram

 

 

in order to correctly manage the test on memtest86 i would suggest you to detach every single ram stick and plug them one by one and do the single ram stick test in order to make is somewhat quicker, remember to put the single ram stick in the correct slot for single ram stick position, check your manual for better informations

                   -`                    y0ur5h4d0w@Darkness
                  .o+`                   ------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: Darkness
               `+oooooo:                 Kernel: Latest  
               -+oooooo+:                Packages: Only what i need to keep it simple
             `/:-:++oooo+:               Shell: ZSH
            `/++++/+++++++:              Main Monitor: LG Ultragear LG 27GS85Q 
           `/++++++++++++++:             Secondary Monitor: Asus MG28UQ
          `/+++ooooooooooooo/`           DE: Plasma Always Bleeding Edge  
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
       -osssssso.      :ssssssso.        Icons: Breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: Kitty 
     /ossssssss/        +ssssooo/-       Terminal Font: Noto Color Emoji 17 FreeMono 13 
   `/ossssso+/:-        -:/+osssso+-     CPU: AMD Ryzen 7 9800X3D (16) @ 5.307GHz 
  `+sso+:-`                 `.-/+oso:    GPU: AMD ATI Radeon RX 7800 XT 
 `++:.                           `-/+/   GPU: AMD ATI Radeon Graphics 
 .`                                 `/   Memory: 61830MiB 

 

Link to post
Share on other sites

1 hour ago, drorsabi1 said:

All the 4 ram sticks lead to bsod

that's kinda weird, the hardware issue regarding ram is really not so common, you should get a new SSD and install windows in there and check if it goes for a BSOD in the clean install.

 

if there's no BSOD in the clean windows then you have issues in the old install, there's tools like sfc and dism that could help to fix some issues, otherwise you can refresh the windows install with keeping your data, but you'll lose your software

                   -`                    y0ur5h4d0w@Darkness
                  .o+`                   ------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: Darkness
               `+oooooo:                 Kernel: Latest  
               -+oooooo+:                Packages: Only what i need to keep it simple
             `/:-:++oooo+:               Shell: ZSH
            `/++++/+++++++:              Main Monitor: LG Ultragear LG 27GS85Q 
           `/++++++++++++++:             Secondary Monitor: Asus MG28UQ
          `/+++ooooooooooooo/`           DE: Plasma Always Bleeding Edge  
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
       -osssssso.      :ssssssso.        Icons: Breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: Kitty 
     /ossssssss/        +ssssooo/-       Terminal Font: Noto Color Emoji 17 FreeMono 13 
   `/ossssso+/:-        -:/+osssso+-     CPU: AMD Ryzen 7 9800X3D (16) @ 5.307GHz 
  `+sso+:-`                 `.-/+oso:    GPU: AMD ATI Radeon RX 7800 XT 
 `++:.                           `-/+/   GPU: AMD ATI Radeon Graphics 
 .`                                 `/   Memory: 61830MiB 

 

Link to post
Share on other sites

6 hours ago, drorsabi1 said:

I try to fix blue screen mamory Management error I trying to fix it but it keep happening 

could use a lot more information.

hardware specs, what version of Windows, etc.

3 hours ago, Blasty Blosty said:

Then the signs point to faulty RAM, first try each stick in each slot and see if the BSOD stops, you may just have 1 faulty stick

 

Also, what are your specs?

What signs pointing where????

O.P. literally gave almost zero information to form any opinion or conclusion whatsoever.

 

Maybe it's an Intel 13th or 14th gen CPU that has degraded. Those often manifest as memory errors.

Link to post
Share on other sites

9 minutes ago, jmwhite33 said:

Maybe it's an Intel 13th or 14th gen CPU that has degraded. Those often manifest as memory errors.

i would still point the finger towards windows but yeah, mobo and CPU are more likely to fail way before RAM i think.

 

at least, in my experience bad RAM is a realy remote kind of hardware issue, the mobo will fail faster then the CPU probably

                   -`                    y0ur5h4d0w@Darkness
                  .o+`                   ------------------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: Darkness
               `+oooooo:                 Kernel: Latest  
               -+oooooo+:                Packages: Only what i need to keep it simple
             `/:-:++oooo+:               Shell: ZSH
            `/++++/+++++++:              Main Monitor: LG Ultragear LG 27GS85Q 
           `/++++++++++++++:             Secondary Monitor: Asus MG28UQ
          `/+++ooooooooooooo/`           DE: Plasma Always Bleeding Edge  
         ./ooosssso++osssssso+`          WM: kwin 
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
       -osssssso.      :ssssssso.        Icons: Breeze-dark [GTK2/3] 
      :osssssss/        osssso+++.       Terminal: Kitty 
     /ossssssss/        +ssssooo/-       Terminal Font: Noto Color Emoji 17 FreeMono 13 
   `/ossssso+/:-        -:/+osssso+-     CPU: AMD Ryzen 7 9800X3D (16) @ 5.307GHz 
  `+sso+:-`                 `.-/+oso:    GPU: AMD ATI Radeon RX 7800 XT 
 `++:.                           `-/+/   GPU: AMD ATI Radeon Graphics 
 .`                                 `/   Memory: 61830MiB 

 

Link to post
Share on other sites

1 minute ago, y0ur5h4d0w said:

i would still point the finger towards windows but yeah, mobo and CPU are more likely to fail way before RAM i think

I have no idea where to point because O.P. simply hasn't provided enough info to choose a direction.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×