Repetitive BSODs on startup but then none after 2 restarts

J

jasonnn1

Member
Joined
May 20, 2022
Posts
8
Hi, I was linked to this thread to get some personalised help regarding my issues with my computer.
  • A brief description of your problem (but you can also include the steps you tried)
    • I've had occasional BSODs before but as of the last month or so, my PC keeps having BSOD on startup. Either Memory management BSOD, kernel error BSOD or page input error. It gets really annoying.
    • Steps I've tried:
      • reseat my memory sticks, I'm using TT tough ram 8gb x4; nothing changed.
      • doing a memtest on said memory sticks; no issues detected when i did it.
      • updating my graphics card drivers, motherboard bios upgraded; nothing happened. I think BSOD epidemic started after I did this. Not so sure.
      • tried windows updating, but recently it keeps failing; saying that I don't have connection to download it despite having internet? Another person on the forum also mentioned that updating the system while still having BSODs may be counterproductive, so here I am asking for help.
    • Occasional BSODs when playing games or using PC prior to that BSOD epidemic.
  • System Manufacturer?
    • Microsoft
  • Laptop or Desktop?
    • Desktop
  • Exact model number (if laptop, check label on bottom)
    • not sure desktops have this
  • OS ? (Windows 10, 8.1, 8, 7, Vista)
    • Windows 11. Windows 10 prior had the same issues. Thought that upgrading to 11 would solve some issues. It didn't.
  • x86 (32bit) or x64 (64bit)?
    • x64 bit
  • (Only for Vista, Windows 7) Service pack?
    • N/A
  • What was original installed OS on system?
    • Originally windows.
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
    • full retail (key from an online site, verified and installed by microsoft)
  • Age of system? (hardware)
    • 1.5 years since desktop was put together
  • Age of OS installation?
    • 1.5 years
  • Have you re-installed the OS?
    • no, I haven't because I didn't want to lose some system files. Tried to fix it before it came to that.
  • CPU
    • AMD Ryzen 5600x
  • RAM (brand, EXACT model, what slots are you using?)
    • ToughRam Thermaltake 8gb x4 (or two pairs) Z-ONE RGB C18 3600MHz
    • All slots are used
  • Video Card
    • AMD Nitro+ Sapphire 6800xt
  • MotherBoard - (if NOT a laptop)
    • ASUS TUF Gaming x570 +Wifi AM4 ATX Desktop
  • Power Supply - brand & wattage (if laptop, skip this one)
    • Thermaltake Toughpower Grand RGB 850w 80+ Gold
  • Is driver verifierenabled or disabled?
    • not installed at all
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
    • no third party antivirus software installed
  • Are you using proxy, vpn, ipfilters or similar software?
    • Exitlag VPN for specific online games only
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
    • no
  • Are you currently under/overclocking? Are there overclocking software installed on your system?
    • Not that I am aware of. Don't tend to overclock my system to preserve its lifespan. If anything, I have undervolted CPU before.
Speccy Results:
http://speccy.piriform.com/results/DhfODwaANRGp7HxxI0ub0Yo


Hope you guys can help me!

Thank you so much for your time and effort!
 

Attachments

For some reason I am unable to open the zip file you uploaded. Please can you create a new one and try it again. Thanks!
 
Are you able to open the zip file? I am still unable to do so. Did you create a new zip file?
 
I managed to open it with 7zip. The windows built-in zip extract still would not work.

The crashes indicate memory corruption most likely due to faulty RAM modules:

Code: 
BugCheck 139, {1d, ffffa684ffee5c90, ffffa684ffee5be8, 0}
Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+b2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffcd08034a8000, 0, fffff80465c6e720, 0}
Probably caused by: memory_corruption ( nt!MiCompressRelocations+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffffe680dee62fa8, 2, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck BE, {ffffe7739ffdd238, 1a0000043dee4025, ffffaa05d8d85940, a}
Probably caused by: memory_corruption ( nt!MiRaisedIrqlFault+363 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffff863ffff322a8, 2, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

The challenge will be to find which module(s) is/are faulty. If you can operate with 8G of RAM you could try each module in turn or operate in pairs until you narrow down to which combination or individual module is causing you the BSODs. This can take time if the BSODs do not happen frequently.

Alternatively you can test with memtest86: MemTest86 - Download now!

Testing each module in turn to find out which are faulty. Note: memtest may not always find every fault but it is pretty good. We recommend testing for a minimum of 8 passes which requires you to test twice in succession. Obviously if a fault is detected at any time you can abort the test and mark that module as faulty.

I note what you say about this happening on first bootup. Use this to your advantage to test when the PC is cold. I wonder if you have a fault which is related to a bad solder joint which on warming up works fine but on a cold start is problematic. The fault could also be in the motherboard so this may not be easy to track down.
 
Last edited:
philc43 said:
I managed to open it with 7zip. The windows built-in zip extract still would not work.

The crashes indicate memory corruption most likely due to faulty RAM modules:

Code: 
BugCheck 139, {1d, ffffa684ffee5c90, ffffa684ffee5be8, 0}
Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+b2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffcd08034a8000, 0, fffff80465c6e720, 0}
Probably caused by: memory_corruption ( nt!MiCompressRelocations+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffffe680dee62fa8, 2, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck BE, {ffffe7739ffdd238, 1a0000043dee4025, ffffaa05d8d85940, a}
Probably caused by: memory_corruption ( nt!MiRaisedIrqlFault+363 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffff863ffff322a8, 2, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

The challenge will be to find which module(s) is/are faulty. If you can operate with 8G of RAM you could try each module in turn or operate in pairs until you narrow down to which combination or individual module is causing you the BSODs. This can take time if the BSODs do not happen frequently.

Alternatively you can test with memtest86: MemTest86 - Download now!

Testing each module in turn to find out which are faulty. Note: memtest may not always find every fault but it is pretty good. We recommend testing for a minimum of 8 passes which requires you to test twice in succession. Obviously if a fault is detected at any time you can abort the test and mark that module as faulty.

I note what you say about this happening on first bootup. Use this to your advantage to test when the PC is cold. I wonder if you have a fault which is related to a bad solder joint which on warming up works fine but on a cold start is problematic. The fault could also be in the motherboard so this may not be easy to track down.
Click to expand...
Thanks, I'll try that and go through the sticks one by one on memtest as well and let you know how it goes once I'm finished or so.
 
philc43 said:
I managed to open it with 7zip. The windows built-in zip extract still would not work.

The crashes indicate memory corruption most likely due to faulty RAM modules:

Code: 
BugCheck 139, {1d, ffffa684ffee5c90, ffffa684ffee5be8, 0}
Probably caused by: ntkrnlmp.exe ( nt!KiFastFailDispatch+b2 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffcd08034a8000, 0, fffff80465c6e720, 0}
Probably caused by: memory_corruption ( nt!MiCompressRelocations+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffffe680dee62fa8, 2, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck BE, {ffffe7739ffdd238, 1a0000043dee4025, ffffaa05d8d85940, a}
Probably caused by: memory_corruption ( nt!MiRaisedIrqlFault+363 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffff863ffff322a8, 2, 0}
Probably caused by: memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

The challenge will be to find which module(s) is/are faulty. If you can operate with 8G of RAM you could try each module in turn or operate in pairs until you narrow down to which combination or individual module is causing you the BSODs. This can take time if the BSODs do not happen frequently.

Alternatively you can test with memtest86: MemTest86 - Download now!

Testing each module in turn to find out which are faulty. Note: memtest may not always find every fault but it is pretty good. We recommend testing for a minimum of 8 passes which requires you to test twice in succession. Obviously if a fault is detected at any time you can abort the test and mark that module as faulty.

I note what you say about this happening on first bootup. Use this to your advantage to test when the PC is cold. I wonder if you have a fault which is related to a bad solder joint which on warming up works fine but on a cold start is problematic. The fault could also be in the motherboard so this may not be easy to track down.
Click to expand...
So I've gone and did the Memtest on every stick and got pass for all 4.
I tried the other approach of using them one by one. Here is what I noticed. When I have 2 slots used (slots 1, 3 from the left or closest to CPU), i dont get any mem issues (so far). Once I have a stick on slot 2 and 4 (any of the ones that passed the memtest, I get the mem_management BSOD Either on startup or while using the PC. I haven't experienced it with sticks on slots 1 and 3 just yet. I'm not sure if that is a thing or not. Will use memory sticks on slots 1 and 3 more often for now to see if the BSOD happens again
 
Excellent progress! It does look as if there might be a problem with either slot 2 or 4 but only time will tell. Does your motherboard have any warranty?
 
philc43 said:
Excellent progress! It does look as if there might be a problem with either slot 2 or 4 but only time will tell. Does your motherboard have any warranty?
Click to expand...
It does I believe; Still within the warranty. Aaaaand, with only slots 1 and 3, i did get the memory management BSOD this morning when i booted it.
 
Please provide a new upload of the logs so we can analyse the latest set of crash dumps.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top