Several types of Blue screen, and crashes
10 minutes ago, Drakeshade said:I am sorry, I have uploaded them separately.
Ok, what I am going to do here, is post some relevant info from the crash dumps, then post my thoughts at the end.
____
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 0000000000000d10, physical page number
Arg3: 0000013a30efbd50, zero
Arg4: ffffbc80fe950000, zero
PROCESS_NAME: MemCompression
______
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffee8007e9a1e0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80335112e7c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
PROCESS_NAME: svchost.exe
______
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffc000d25d10f8
Arg3: 0000000100000000
Arg4: 0000000000000000
MEMORY_CORRUPTOR: ONE_BIT
SYMBOL_NAME: ONE_BIT
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
____
No need to examine the other crash dumps, you have faulty RAM.
Run MemTest86
And find out which stick is bad.
Report back.
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 accountSign in
Already have an account? Sign in here.
Sign In Now