Insane amount of BSODs

[LordMustang]

Hello guys,

I've had an MSI laptop for a while. It came with windows 8.1 installed. A while ago I updated it to windows 10, and right now I have an insane amount of bluescreens. About once to twice every day. Is there any way I can find out the cause of these BSODs? Most common errors are MEMORY_MANAGEMENT and FAULTY_HARDWARE_CORRUPTED_PAGE.

If I need to attach anything, please tell me what and how, I'll be glad to do so.

Thanks in advance!

 

[Colif]

run this on ram: http://www.memtest86.com/

can you download and run who crashed: http://www.resplendence.com/whocrashed
it will give a summary of your errors

Copy/paste results here

That last error is most likely a driver. IN Asus laptops this was caused by the touchpad software so though I know you don't have an asus, it could be a related issue none the less. http://answers.microsoft.com/en-us/windows/forum/windows_10-power/faulty-hardware-corrupted-page-error-blue-screen/c314a80f-150b-4fe8-8bb2-6801b07f0ac9?auth=1

 

[LordMustang]

This came out of WhoCrashed. I will do the Memtest later.

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 27-9-2016 16:57:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092716-31296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xFB5, 0x2ECF2C80, 0xFFFFA801AD784000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 27-9-2016 16:57:32 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xFB5, 0x2ECF2C80, 0xFFFFA801AD784000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 26-9-2016 18:10:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092616-24437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x5ED, 0x14A405F0, 0xFFFFAA81B48AA000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 26-9-2016 14:43:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092616-44640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x1A (0x41793, 0xFFFFAF8000165BA0, 0x175, 0x174)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 18-9-2016 13:08:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091816-33234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x109 (0xA3A013E1530097FD, 0x0, 0x2A1ED5063E59E544, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 18-9-2016 12:16:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091816-27671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xFC2, 0x1EA8E910, 0xFFFFC1817D0E2000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).

Those problem problems are the worst kind (sorry, i had to laugh at typo)

they all data errors, 2 point at drivers that are hiding behind the kernel and blaming it for killing itself, which is unlikely.
NTSOKRNL = critical part of windows 10, deals with driver requests. ntkrnlmp.exe is also part of same process as NTOSKRNL, I just can't remember what last two initials strand for.

 

[LordMustang]

Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).

Those problem problems are the worst kind (sorry, i had to laugh at typo)

they all data errors, 2 point at drivers that are hiding behind the kernel and blaming it for killing itself, which is unlikely.
NTSOKRNL = critical part of windows 10, deals with driver requests. ntkrnlmp.exe is also part of same process as NTOSKRNL, I just can't remember what last two initials strand for.

So what does that mean? It's quite strange that after installing windows 10, RAM breaks. So could it be fixed by doing a clean reinstall of windows and all drivers?

 

[Colif]

win 10 seems more senastive to ram problems than win 7 was. Run memtest, if you get absolutely 0 errors then we look at other things.

For instance, do this:
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

I don't know when a person will read it, if no one answers in a few days I send you elsewhere.

 

[LordMustang]

win 10 seems more senastive to ram problems than win 7 was. Run memtest, if you get absolutely 0 errors then we look at other things.

For instance, do this:
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

I don't know when a person will read it, if no one answers in a few days I send you elsewhere.

Well I never used windows 7 on this laptop, only 8.1. Tomorrow I will run memtest.

 

[Colif]

I was guessing, I had a 50% chance.

 

[LordMustang]

So far on pass 2 of memtest, already at 370 errors. Seems quite steep for a laptop that's barely 2 years old.

 

[Colif]

You need new ram, when you run memtest you don't want to find any errors. 1 is too many, 370 is off the charts

 

[LordMustang]

I don't even have the slightest idea on how to replace laptop ram, let alone finding these sticks. Warranty has expired already I think.

 

[Colif]

what model laptop is it and I go see what I can find. The little I know I think its normally easy to do as thats one of the obvious updates for a laptop, but I won't guess until I see the name of it.

 

[LordMustang]

It's an MSI ge70 2pc-272nl

 

[Colif]

MSI says not to do this at home...

[video="https://www.youtube.com/watch?v=i4xbILQgU8Q"][/video]

So might be an idea to get someone to replace ram for you. I don't know how much ram you have but max it can accept is 16gb. It looks pretty easy to do, hardest part getting back off and figuring out what ram to replace it with. Best leave that to a store I think.

 

[LordMustang]

Yeah. I'll send it to MSI and they will fix it for me, then charge $300 for 2 RAM sticks that in reality cost only $100. Besides, I'll also lose my only PC for like 2-3 weeks or so. I can't void warranty anymore, as it's already expired. The big problem is finding the right RAM.

 

[Colif]

I guess it depends how long it takes and their hourly rates. It might actually be that much all up. The ram isn't as cheap as I thought it was

Crucial shows ram for your laptop at $77 for 16gb: link and thats the cheaper one, the faster variety costs $85

A local store could charge you about same.

 

[LordMustang]

I guess it depends how long it takes and their hourly rates. It might actually be that much all up. The ram isn't as cheap as I thought it was

Crucial shows ram for your laptop at $77 for 16gb: link and thats the cheaper one, the faster variety costs $85

A local store could charge you about same.

Do you think it's possible to do by myself? I've build a few desktops in the past. Will this be much different or more difficult? And what did you search for to find the right RAM?

 

[Colif]

I don't know where you are but in Australia, for instance, their repair places charge $140 as a base cost and then cost of parts. I didn't see if they have hourly rate, judging from video its not a hard job, 20 minutes at most. Shame no repair centres near you, could have it done in a day at most if you took in in early and they weren't busy

 

[LordMustang]

Well I'm not really eager to pay $140 for something I might be able to do by myself. The hardest part is finding the right RAM. I have no idea if there's specific laptop RAM, and what specs it should have.

Also, memtest says that it tests multiple things, including CPU. Isn't there a chance that RAM is not the error?

 

[Colif]

msi don't give me much to work with, their specs don't say what type of ram it takes. The Crucial link i dropped above was broken, and even it doesn't tell me that much. I know Laptop ram is different to normal size, but I don't know enough about it myself to find examples.

 

[LordMustang]

msi don't give me much to work with, their specs don't say what type of ram it takes. The Crucial link i dropped above was broken, and even it doesn't tell me that much. I know Laptop ram is different to normal size, but I don't know enough about it myself to find examples.

Is there any way to check which RAM type is installed?