Jump to content

Recommended Posts

Posted

Hi

Hopefully someone can help me understand this error code, my xp pc randomly reboots with this error

Error code 1000008e, parameter1 c0000005, parameter2 01bf802f, parameter3 b65ddca5, parameter4 00000000.

Any help would be great


Posted

Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved

Common exception codes include:

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.

So a driver on your machine attempted to access memory that was invalid, or accessed memory that had been paged out while the driver was at DPC level or higher.

Do you have any .dmp files in your Windows directory around the time of the last crash? That's about the only way to know for sure who/what caused this.

Posted (edited)
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved

Common exception codes include:

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.

So a driver on your machine attempted to access memory that was invalid, or accessed memory that had been paged out while the driver was at DPC level or higher.

Do you have any .dmp files in your Windows directory around the time of the last crash? That's about the only way to know for sure who/what caused this.

I have 2 .dmp files in the minidump folder in the windows directory. How do i determine what is wrong from these. The issue is i can't think what device drivers i've installed recently, so i wonder would it be an application

It has just happened again only this time will not allow me to logon displaying an access violation message and then displays a critical stop. So restarted and attempted to goto safe mode with networking but failed with another critical error. So this time just tried safe mode and got in no problem. Could this be a networking issue as when downloading files from the internet they would fail and pc seems to always restart when on the internet

Edited by graemek
Posted
I have 2 .dmp files in the minidump folder in the windows directory. How do i determine what is wrong from these. The issue is i can't think what device drivers i've installed recently, so i wonder would it be an application

No, this is a kernel error. It could be an application working with a kernel-mode driver, but the app itself isn't the problem if this is the case.

It has just happened again only this time will not allow me to logon displaying an access violation message and then displays a critical stop. So restarted and attempted to goto safe mode with networking but failed with another critical error. So this time just tried safe mode and got in no problem. Could this be a networking issue as when downloading files from the internet they would fail and pc seems to always restart when on the internet

It could be - if you could post the .dmp files here, we can open them in the debugger and try to tell you what's wrong.

Posted

I have attached the dump file. I think i may have found the problem, i think one of my ram dimms is faulty. I have removed one of them and the issue seems to disappear will continue testing and post back to results

Dumps.rar

Posted
I have attached the dump file. I think i may have found the problem, i think one of my ram dimms is faulty. I have removed one of them and the issue seems to disappear will continue testing and post back to results

In looking at the dump files, I would have to agree that it looks like faulty RAM. Each time, we're accessing memory via win32k.sys to draw data on the screen or handle window functions, and the memory address referenced is partially gone, but not fully bad. Meaning we had a fault either reading in, or writing to, the page in memory, most likely.

Posted (edited)

Try running Memtest to check your RAM for errors, if the RAM is healthy there should be no errors.

Edited by DL.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...