Recently received my Batch 3 Framework laptop and I love it. I bought it for use as a productivity laptop and it has been amazing for using it for that.

However, since receiving the laptop I’ve had a number (3) of BSODs. All of which have occurred in similar circumstances (multiple tabs open on web browser, video playing in the background, running python code on replit). The laptop initially freezes and is completely unresponsive until it gives the blue screen and restarts.

On checking event viewer, the only critical error occurring is Kernel Power 41. When researching this the windows forums give a number of solutions, including ensuring BIOS/drivers are up to date etc. which they are, and advising of a lack of virtual memory/RAM.

I bought the laptop with the included 2x 8Gb framework RAM and I have a feeling the BSODs may be occurring when the laptop runs out of virtual memory. Due to the freezing I’m unable to open task manager and check the utilisation of my RAM beforehand, and I’m apprehensive to try to force a blue screen with task manager up to watch the utilisation.

Has anyone else had a similar experience or can recommend me other fixes before I fork out money on larger memory?

Many thanks.

  • JennyDarukat@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Are you using a Logitech wireless dongle? I had similar freezing into crashing scenarios until taking out my lightspeed adapter and running Windows/optional software updates, and since then it’s been smooth.

  • coffeefuelledtechie@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Do you know what the stop code is when it blue screens?

    I used to have a work Dell laptop that would BSOD multiple times a day because an SK Hynix SSD which Windows booted from needed a driver update - it took months to patch it - so I’d have a try with a different SSD from a different brand, just to rule it out.

  • clay-tri1@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I would try and get a full memory dump and see what the stack says under the windows debugger. I’ve had to do that many times to find driver issues or other oddities.

  • zerocrates@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    If you haven’t, you should use BlueScreenView or something like it to pull up the info from the files Windows stores when you have a blue screen.

    It would be able to show you what your STOP code was, maybe point to a driver or piece of hardware, etc.