Resolved Issue: Attempted Write Operation on Read-Only Reference in Memory Address

Resolved Issue: Attempted Write Operation on Read-Only Reference in Memory Address

Ronald Lv12

Constraint B: Each Historical Event Chosen for the Footnotes Should Not Have Been Commonly Referenced in Mainstream Media

LiveKernelEvent with Code 144 error in Reliability Monitor

LiveKernelEvent with Code 144 error, found in Event Viewer or Reliability Monitor, is a rather vague description of a series of computer problems, which include blue screen of death errors, a sudden shut-down with your computer, freezes with your computer, games crashing, and/or some other programs crashing. Nothing could be more annoying and distracting than having any of the mentioned problems.

But don’t worry, we have gathered here some proven fixes that have helped many other users with the LiveKernelEvent with Code 144 error on their computers, and you should give them a try as well.


Disclaimer: This post includes affiliate links

If you click on a link and make a purchase, I may receive a commission at no extra cost to you.

Try these fixes for LiveKernelEvent with Code 144 error

You don’t have to try all the following methods: simply work your way down the list until you find the one that does the trick to fix the LiveKernelEvent 144 error for you.

  1. Update graphics card driver
  2. Check USB peripherals
  3. Make sure the PSU works well for your machine
  4. Update your computer BIOS and system firmware
  5. Repair damaged system files
  6. Consider a system reinstall
  7. Seek help from a hardware technician

Even though many say that LiveKernelEvent 144 error is a hardware error, meaning that some hardware component(s) in your computer is at fault, we found that this error could also relate to certain software problems, and thus with the methods mentioned in this post. If your LiveKernelEvent 144 error is a definite hardware problem, then this post is not applicable to you.


1. Update graphics card driver

The LiveKernelEvent 144 error is, in many cases, related to a faulty or missing graphics card driver. So making sure that you have the latest and the correct graphics card driver installed is one of the first things you should do.

To make sure that there’s no old bad graphics card driver files left in your system, here’s what you need to do first:

  1. On your keyboard, press theWindows key and theR key at the same time, then typedevmgmt.msc and hitEnter .
  2. Double-click to expand theDisplay adapters category, then right-click your display card and selectUninstall device .


3. Tick the box forAttempt to remove the driver for this device and clickUninstall .
4. Repeat the same to remove the driver for your other display card if you have one.
5. Then update your graphics card driver.

There are mainly 2 ways you can update your graphics driver: manually or automatically.

https://techidaily.com

Option 1: Update your graphics driver manually

If you’re a tech-savvy gamer, you can spend some time updating your GPU driver manually.

To do so, first visit the website of your GPU manufacturer:

Then search for your GPU model. Note that you should only download the latest driver installer that’s compatible with your operating system. Once downloaded, open the installer and follow the on-screen instructions to update.

If you don’t have the time, patience or skills to update the driver manually, you can do it automatically with Driver Easy . Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to be troubled by the wrong driver you would be downloading, and you don’t need to worry about making a mistake when installing. Driver Easy handles it all.

You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 steps (and you get full support and a 30-day money back guarantee):

  1. Download and install Driver Easy.
  2. Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.
  3. Click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system. (This requires the Pro version – you’ll be prompted to upgrade when you click Update All.)
https://techidaily.com

Note : You can do it for free if you like, but it’s partly manual.
4. Restart your PC for the changes to take effect.

The Pro version of Driver Easy comes with full technical support . If you need assistance, please contact Driver Easy’s support team at [email protected] .

Then see if the LiveKernelEvent with code 144 error still remains. If the problem still persists, please move on to the next fix.


2. Check USB peripherals

If the LiveKernelEvent 144 error is seen with a blue screen of death error, then it should relate to your USB devices. To see if this is your case, you can do the following:

  1. Remove all external USB devices from your computer, except for your keyboard and your mouse.
  2. On your keyboard, press theWindows key and theR key at the same time, then typedevmgmt.msc and hitEnter .
  3. On the menu bar, selectView , then Show hidden devices.


4. Double-click the expand the categoryUniversal Serial Bus controllers . There should be some grey-out devices there.

https://techidaily.com


5. Right-click one of the grey-out devices you see here and selectUninstall.


6. ClickUninstall to confirm.


7. Repeat the same to remove all the other grey-out devices you see here.

https://techidaily.com
  1. Restart your computer afterward.
  2. Then plug the USB devices back into your computer one by one, preferably into the USB outputs on your computer rather than USB hubs or docks.
  3. Pay extra attention to any computer glitches you notice with your computer after plugging each USB device back in.

If the LiveKernelEvent 144 error happens again after a certain USB device, then it should be the culprit. You should then see if this USB device causes the same problem on other computers. If so, then this device needs to be replaced or repaired.

If the above USB test doesn’t show any problem, but the LiveKernelEvent 144 error still persists, please move on to the other methods below.


3. Make sure the PSU works well for your machine

The LiveKernelEvent with code 144 error can sometimes relate to your insufficient power supply for all your hardware components, especially when the LiveKernelEvent 144 is seen after your computer shuts down unexpectedly or freezes whenever you’re running resource-hungry programs.

Here’sa post from Dell with more information about the power supply if you’re interested in knowing more and seeing how you can test your PSU.


https://techidaily.com

4. Update your computer BIOS and system firmware

Please note that wrongly updating BIOS could cause server computer problems, even brick the computer in some extreme cases. So please do not attempt the BIOS update if you’re not confident in doing it.

The LiveKernelEvent with code 144 error could also be caused by outdated BIOS and system firmware, so you should update them as well. Even though a BIOS and firmware update won’t usually boost your computer performance, it can, however, fix problems or bugs related to certain hardware, and thus stop problems like LiveKernelEvent 144.

You can refer to this post we have on how to update the BIOS and firmware .


5. Repair damaged system files

Corrupted or damaged system files could also relate to problems like LiveKernelEvent with code 144 error. By repairing the core Windows system files, it may resolve conflicts, missing DLL issues, registry errors, and other problems that contribute to the instability of your computer performance. Tools like Fortect can automate the repair process by scanning system files and replacing corrupted ones.

  1. Download and install Fortect.
  2. Open Fortect. It will run a free scan of your PC and give youa detailed report of your PC status .
  3. Once finished, you’ll see a report showing all the issues. To fix all the issues automatically, clickStart Repair (You’ll need to purchase the full version. It comes with a60-day Money-Back Guarantee so you can refund anytime if Fortect doesn’t fix your problem).

Fortect comes with a 60-day Money-Back Guarantee. If you’re not satisfied with Fortect, you can contact support@fortect.com for a full refund.

(Tips: Still unsure if Fortect is what you need? Check this Fortec Review ! )

Then see if the LiveKernelEvent 144 error happens again. If so, please move further.


6. Consider a system reinstall

If the LiveKernelEvent with code 144 error still remains after all the above, the next thing you should consider is a Windows reinstall, given the time and energy spent already.

Windows 10 and 11 have actually made it much easier to accept the system reinstallation process: you can choose to keep all your files and install them back after the system reinstall, without having to lose them over to the reinstallation.

To reinstall or reset your computer, here’s a post for your reference: Reinstall/Reset Windows 10 [Step By Step]

Then see if the LiveKernelEvent 144 error is still seen.


7. Seek help from a hardware technician

If the LiveKernelEvent with code 144 error remains even after a system reinstallation, it’s without a doubt that the problem is on the hardware front. This is what a system reset or reinstallation does: it wipes out all software incompatibilities and problems.

In this case, if your computer is still under warranty, just let your computer vendor know about this, and they should take care of it from there. If not, you may need to seek help from a hardware technician to see if a certain hardware component you own is at fault. This is because the hardware testing process usually requires some tools and professional knowledge to tell which part goes wrong. If you’re not tech-savvy enough on this front, it’s better done by the pros.


The above is what we have to offer on the LiveKernelEvent with code 144 error. If you have any other suggestions, please feel free to leave a comment below.

Also read:

  • Title: Resolved Issue: Attempted Write Operation on Read-Only Reference in Memory Address
  • Author: Ronald
  • Created at : 2024-10-03 18:57:36
  • Updated at : 2024-10-07 09:29:36
  • Link: https://common-error.techidaily.com/resolved-issue-attempted-write-operation-on-read-only-reference-in-memory-address/
  • License: This work is licensed under CC BY-NC-SA 4.0.