Jump to content

So a few days ago my computer blue screened completely randomly. it said there was some type of memory error. after that every time I would start it up it would never successfully startup without giving a bluescreen error related to memory. Now my computer won't start up at all. it turns on but the screen never turns on and then it shuts itself back off then goes into an infinite loop of this. I cant even get into the bios. Some of the error codes I got are:

 

Machine_check_exception

Irql_not_less_or_equal

Attempted_write_to_readonly_memory

 

I've removed my graphics card, unplugged all unnecessary peripherals, reset my motherboard bios by pulling out the coincell battery, reduced the memory to one stick and i even re-seated my processor and nothing is working.

 

 

Link to comment
https://linustechtips.com/topic/702593-computer-not-starting-up-please-help/
Share on other sites

Link to post
Share on other sites

3 minutes ago, 5Beans6 said:

So a few days ago my computer blue screened completely randomly. it said there was some type of memory error. after that every time I would start it up it would never successfully startup without giving a bluescreen error related to memory. Now my computer won't start up at all. it turns on but the screen never turns on and then it shuts itself back off then goes into an infinite loop of this. I cant even get into the bios. Some of the error codes I got are:

 

Machine_check_exception

Irql_not_less_or_equal

Attempted_write_to_readonly_memory

 

I've removed my graphics card, unplugged all unnecessary peripherals, reset my motherboard bios by pulling out the coincell battery, reduced the memory to one stick and i even re-seated my processor and nothing is working.

 

 

have you tried booting on a fresh drive ?

Link to post
Share on other sites

Error Message:

IRQL_NOT_LESS_OR_EQUAL

Explanation:

This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

I didn't know what to put here...

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

×