@Georgene_Nunn Yep, no gold should be showing on the connection end of the SSD as it should be under the shroud. There’s a very good possibility that’s causing your issue. Also, if you are only using one RAM module, it needs to be in Slot 0.
3 Likes
Could it be a bluetooth issue? I’ve been having no trouble with my 12th gen DIY i5 (running Linux instead of Windows though), but when I tried using some bluetooth headphones for a few hours, at some point the machine locked up and needed a long press of the power button. Since then I’ve been avoiding bluetooth. Maybe try that for a few days if possible,
1 Like
Yesterday no further crashes after the swap and reseat. This morning it behaved very erratically when I turned my monitor on after boot up. Had to hard shut down due to unresponsiveness. So I took the opportunity to swap the ram back to slot 0.
I think reseating the drive is likely to be the solution to the core problem, but I will likely have to back up, wipe, and reinstall, since I don’t especially trust windows to fully recover from the instability caused by the crash-happy period. That said, if I go 2 days without another BSOD I’d say that got it solved. If not I may move on to live linux and/or no bluetooth.
I doubt it’s possible to adjust future board models to be more strict about how the support screw lines up so the drive has to be fully inserted to be secured, but it may be worth making a note in documentation that none of the gold should be showing (unless it’s already there and I overconfidently missed it). It’s not necessarily self-evident - with RAM, for example, there actually is a tiny bit of the contact area exposed and that’s… normal? Or at least no matter how snugly I try to insert it, it remains visible. I seem to recall that being fairly standard for RAM and (incorrectly) assumed it was fine for the stick style of SSD as well!
Just BSOD’d. Memory Management. Was afk for maybe… a half hour? and the moment I sat down it dropped into BSOD. This time with a little bar across the top, glitchy colors, and it wouldn’t restart after hitting 100%, it sat there with the fan running.
SFC didn’t find anything. I’m all ears for other things I should check.
Honestly I think I’ll have to up my timeline for backing up, wiping, and starting over.
In my experience (I’m strictly a Dell repair tech, so YMMV):
I have repaired desktop machines that were randomly displaying BSODs with different errors - including several of those mentioned in the OP - by replacing the processor.
This was after replacing the system board and sometimes the RAM (at the very least a RAM dance was performed, exonerating it).*
I also repaired laptops behaving like that the same way. More and more that means replacing the system board (which sorta partially exonerates the processor, making the whole issue messier…).
It sounds to me like you’ve done everything you could possibly do, and more than Dell would need in order to have me replace the CPU.
So if I had to guess… you may be heading for a motherboard replacement.
* For a while it happened so often I created my own little conspiracy theory:
As a hardware resolution to the Spectre and Meltdown bugs, the CPU manufacturer sent out BIOS updates that purposely faulted the CPU, requiring it to be replaced with one that doesn’t have them.
I concocted this little fantasy because, in my initial training the processor was emphasized as absolutely the last component to be replaced, because it was the hardiest thing in the computer. Then a couple years after those bugs appeared it seemed like I was suddenly replacing desktop CPUs left and right.
(Disclaimer: This is entirely for my own amusement. Nobody should take it seriously - I certainly don’t.)
ATTEMPTED_WRITE_TO_READONLY_MEMORY - this error occurs if a driver attempts to write to a portion of memory that has been designated as read only.
If you haven’t yet, make sure you’re on the latest BIOS and that you’ve got the latest drivers directly from Intel’s website.
If you have other USB based devices usually plugged in remove them one at a time and see if it resolves.
Just to not leave this hanging with no updates, had a migraine weekend so didn’t get a chance to start fresh like I hoped.
BIOS is 3.10 as noted in OP. USB items plugged in are: monitor via hdmi expansion card, power via USB-c expansion card, fan via USB-A expansion card, and one unused USB-C expansion card. Crashes have occurred in nearly every configuration.
(I have not tried unplugging absolutely everything and running the system long term aiming for a crash, largely because this is also my work computer and it’d make life pretty challenging. I’d also hope for another way to test if basic components were the source of the conflict!)
Here’s a list of the latest crashes.
11-8 memory management "A corrupted PTE has been detected. This is possibly a software problem. This is a typical case of memory corruption. "
11-7 memory management
11-5 system service exception - win32kbase.sys (win32kbase+0x7148F)
Are you able to install nirsoft bluescreen viewer and post the information that results on your next BSOD?
Certainly! I usually use WhoCrashed but this might get more info?
3 recent crash dumps saved from BSV
==================================================
Dump File : 111722-8000-01.dmp
Crash Time : 11/17/2022 4:49:22 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0000000000041792 Parameter 2 : ffffd33fff0363c0
Parameter 3 : 0000100000000000 Parameter 4 : 0000000000000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f92d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f92d0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111722-8000-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 2,380,004
Dump File Time : 11/17/2022 4:49:55 PM
==================================================
Dump File : 111722-18859-01.dmp
Crash Time : 11/17/2022 12:18:26 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffff828a64b163c8 Parameter 2 : 0000000000000000
Parameter 3 : fffff8064fa0ef66 Parameter 4 : 0000000000000002
Caused By Driver : FLTMGR.SYS
Caused By Address : FLTMGR.SYS+28060
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f92d0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111722-18859-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 2,427,532
Dump File Time : 11/17/2022 12:19:13 PM
==================================================
Dump File : 111622-19515-01.dmp
Crash Time : 11/16/2022 1:04:56 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffffc0000005 Parameter 2 : fffff8006610c910
Parameter 3 : fffff18719a6e998 Parameter 4 : fffff18719a6e1d0
Caused By Driver : FLTMGR.SYS
Caused By Address : FLTMGR.SYS+8b10
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : fileinfo.sys+c910
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111622-19515-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 19041
Dump File Size : 2,581,420
Dump File Time : 11/16/2022 1:06:02 PM
A note - after I got the system thread exception, I ran chkdsk, sfc, and dism. All found and fixed errors. Didn’t even get a whole 24 hours before it started bugging out again!
I’ve had a mix of work deadlines and seasonal migraines so actually doing a system wipe hasn’t been an option. 
Tho I am open to suggestions on the best method for wiping and starting over once I can carve out the day to make sure I’m super backed up and have time to get all my software set back up! I haven’t had to do a full system wipe in a bit and last time I was able to use 2 drives in the same system to shuffle things around.
Hi @Georgene_Nunn,
We’d definitely recommend a wipe and a fresh install of the OS and the Framework Driver Bundle only as it seems either something is corrupted in storage or something is wrong with the SSD itself. With a fresh OS install, you’ll eliminate most other potential sources of the BSODs. If you continue to have issues with the bare minimum installed, all signs point to a SSD failure. If under warranty, it will be replaced.
Understood. SSD is a Sabrent drive purchased thru newegg. Doubt I have any coverage. Man, what a rough go.
Earlier I turned on my attached monitor and the whole system went unresponsive. Two core windows processes, the desktop window manager and windows explorer, were each using a big chunk of cpu and reported high power use. Whole system’s just sort of wigged out. Tho I’ve had display specific issues almost the entire run of the laptop so far.
Fully wiped the drive. reloaded windows. Used the framework driver set dated 2021-12-16 that i had on a backup drive. bios still listed as 3.10.
Slowly adding back what I need. Browsers, ms office.
Got my first page fault in a non-paged area error while typing this!
I actually regret wiping the whole machine because I didn’t break down and buy a replacement drive first so now I have to live with it being unstable AND all my settings blown out. boo
Sorry for the late reply. The other option is the use drivers directly from Intel’s website as opposed to the ones provided by Framework. They may solve the fault issue. The page_fault_in_nonpaged_area is usually driver related. There have been issues with SSDs and the Intel Management Engine before that were solved with a driver update from Intel in the past.
1 Like
Ah sorry, forgot to mention that I had gotten the Intel drivers when I had these issues.
Not super fun update. I just finished installing a WD Black SN850X, one of the ones from the approved list, I believe. Totally fresh windows install. Used the December 16 2021 driver bundle to get it online.
Was just in the process of getting things set up and had my first page fault in a non-paged area. Still need to update windows to 22h2 and all other requisite patches and updates, and I’m grabbing the Intel support assistant to push updates once that’s done.
This bsod so early out of the gate has me spooked though. Maybe I should reinstall the bios for good measure. Or rollback the bios to 3.07 (down from 10) if it will let me?
If this round of updates and patches doesn’t do the trick then. I’m running out of things that I can personally attempt to fix. It’s possible that this is still somehow something I did or didn’t do but I’m running out of ways that could be true. At least on my older crashy Toshiba I knew it was because of deprecated hardware.
It’s impacting my work for sure but at the moment I’m just worried that I won’t be able to run the big update to dwarf fortress when that releases in a few days.
EDIT: memory management error as I was installing updates.
Worth checking all items again to make sure they’re seated properly hardware wise, including the wireless card. May also be worthwhile to attempt a static discharge of the laptop. Is there a different driver that can be installed for your monitor?
Got an updated copy of memtest86 on a thumb drive. Errors on test 7 and 13 on round 1. Put my old ram (which was the hardware piece I’d tried replacing first!) back in and I’m testing that. Halfway through pass 2 with no problems.
Went thru the bios and turned Intel Turbo Boost Max Technology 3.0 back on, I can’t remember what conflict management attempt prompted me to try turning it off, but it definitely didn’t add stability.
If this set of tests passes the next step is to make sure every driver is current.
Is it just normal now for systems to be wildly unstable without driver massage? I had really good luck with previous computers being pretty solid until hardware EOL. This process has exceptionally touchy. Appreciate people hanging in there with me. Feels like it’s been uphill for months now.
Yes you need the drivers for a stable experience, always been that way, and older the windows install iso i.e. the more updates there are for it, more hellish and slow the experience will be. Still not clear what Windows version you are attempting to install, and also what processor. I am assuming 11th gen since you mention a 3.10 BIOS. By the way there is a new BIOS available for 11th gen…get it. Rolling back to an older BIOS is almost never recommended, and running an older BIOS is just asking to have issues that may have been resolved in a later version.
As to the why you have had so many issues… 1) looks like you had a dying SSD, 2) most SSD’s these days have some form of error connection built in, 3) this error correction may have been hiding other issues, 4) you clearly switched to RAM that has an issue.
Recommend getting to a good default state. 1) Latest BIOS, 2) Memtested good RAM, 3) New nvme drive, preferably a known good reliable brand. 4) Download the latest Windows 11 install media (Windows 10 is not supported so if you are trying to install it you will have nothing but problems). 5) Install the OS you chose using recent install media, and in the case of WIndows 11 install all the latest drivers Framework has provided. 6) Reboot. 7) Lastly install all remaining WIndows 11 updates. 8) See if you have any problems. At this point if you do, contact support and get a new motherboard.
Your entire thread just sounds like you had a bad component, replaced a good component with a bad component, replaced the original bad component with a new component, and just finally replaced the bad replacement componennt with the original good component which should not have been replaced. Hopefully it all works now.
1 Like
That’s not quite what I meant about drivers but I’m not going to belabor the issue, I phrased myself badly. Moving on.
Framework Laptop BIOS and Driver Releases (11th Gen Intel® Core™) 3.10 is the latest provided in the KB for 11th gen, last updated August 1 2022. The only other version I see is a beta for 3.17 here 11th Gen Intel Core BIOS 3.17 Beta - given everything, I will wait until 3.17 is official.
Knowing that SSDs can be opaque when it comes to issues is helpful.
The type of BSOD errors I’ve gotten during the process are typically blamed on either bad drivers or bad ram. After exhausting driver fixes I moved to replace the ram which obviously backfired. Also I can safely say that memtest64 was a waste of time. I wanted to use a tool that would allow me to drop the test and resume work immediately if I had to, clearly not worth the compromise in quality of testing.
I think the order you mentioned here is exactly it. At least a little frustrating given that Crucial has historically been reliable ram, ime. Entirely possible I’m responsible for the original drive being hosed, since it wasn’t seated right originally. That style of drive is entirely new to me, and since it’s not uncommon for there to be visible connector with ram modules, I didn’t think anything of there being visible connector on the drive, especially since the screw went into place without issue.
So barring any future crashes, it seems like this was just difficult to diagnose hardware failures. Sheesh. Thanks again for being an extra set of eyes, people. Considering this closed.
3 Likes
I know I have never had a bad stick of Crucial RAM, and I have bought a lot of it. Sometimes you just get a perfect storm.
1 Like
This time with a little bar across the top, glitchy colors, and it wouldn’t restart after hitting 100%, it sat there with the fan running.
This looks like a faulty RAM to me. I had the same experience with my linux install. If it doesn’t want to start again, pay attention to the led signals on the side of the laptop, there is a guide 11 gen 12th gen that tells you what they mean. You can determine who is at fault like that.