Are these crash dumps anything to worry about?

[Antoine]

Or are they just random occurances? I havent even had the laptop 2 months yet and it crashed once 3 days ago then again today. Here is the dump info:

On Thu 9/27/2018 2:40:41 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092718-16031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0xD1 (0xFFFFF8077D24A956, 0x2, 0x8, 0xFFFFF8077D24A956)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 9/27/2018 2:40:41 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x74A9)
Bugcheck code: 0xD1 (0xFFFFF8077D24A956, 0x2, 0x8, 0xFFFFF8077D24A956)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 9/24/2018 10:49:34 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092418-18656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9380)
Bugcheck code: 0x50 (0xFFFFF800AFCEDAC9, 0x10, 0xFFFFF800AFCEDAC9, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: [Microsoft® Windows® Operating System](‘Google Search Windows® Operating System’)
company: [Microsoft Corporation](‘Google Search Corporation’)
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I also checked reliablity history and noticed I get critcal errors everyday since day one. All of hich asid from the crashes liste above and the one Hardware error I had a long time ago, the rest are ALL from CMStatus stopped working, that ones been happening since day one according to the report but its never effected my pc in any way (i.e I woulda never known about it if i hadnt checked the reliablity due to these crashes that started)

[jmarket]

Please download the Sysnative BSOD Dump + System File Collection App - save to Documents folder.

Run the app - Double-click on the downloaded EXE file
Output = new folder created in Documents + a zipped version – SysnativeFileCollectionApp folder + SysnativeFileCollectionApp.zip.

Please note that the app averages ~3 minutes to run on most systems; other systems - it my take as long as 10-15 minutes to run. Please be patient.

Also note: The app auto-zips the SysnativeFileCollectionApp output folder. It is located in your Documents folder.
Windows Explorer should open and highlight the zipped folder

Please attach the SysnativeFileCollectionApp.zip to your post and await further instructions

[Antoine]

here ya go (took under a minute on my beast of a machine lol). Soo it says the3 file is too large for the server to process

[jmarket]

Can you try uploading it to Dropbox or Google Drive and posting the link?

[Antoine]

https://drive.google.com/open?id=1uPGnO2FZOs6uuGyHb3Z9ae09f5iJOTYd

[Antoine]

just chrashed again

[Antoine]

quieter than usual >.> (btw just ran an sfc /scannow and it said WIndows found some currpted files and repaired them (the were not corrupt files it couldnt repair)

[jmarket]

Hey @Antoine sorry about the delay.

I was just about to suggest a SFC scan lol.

Can you upload any and all new dump files?

[Antoine]

updated dump (only new crash was the one i previously posted about a week ago)

[jmarket]

The file you uploaded has no dump files.

[Antoine]

hmm well i ran the program agan and thats what it gave me sooooo what shoudl I be doing to get the most recent dump file?

[jmarket]

The file probably erased itself. Nothing you can do unless it blue screens again.

[veeg]

Any updates for us?

[veeg]

Any updates for us? After 48 hrs this thread will be closed.

[jmarket]

Can I get you to post fresh BSOD logs for me to analyze?

Also do me a favor and do the below as well please:

[ul]
[li]Click on the Start button and in the search box, type Command Prompt[/li][li]When you see Command Prompt on the list, right-click on it and select Run as administrator[/li][li]When command prompt opens, copy and paste the following command into it, press Enter. [/li]
[ICODE]sfc /scannow[/ICODE]
[li]Wait for this to finish before you continue[/li][li]Copy and paste the following command, press Enter.[/li]
[ICODE]findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\Desktop\sfc.txt[/ICODE]
[/ul]
That will create sfc.txt on your Desktop. Please attach sfc.txt to your next post:
[ul]
[li]Open Reply window. Click ‘More Reply Options’.[/li][li]Go to the end of your text (if any).[/li][li]Click ‘Choose Files..’[/li][li]For ‘File name’ paste this: %userprofile%\Desktop\sfc.txt[/li][li]Click the ‘Add to Post’ link which will appear on the right when the file has been uploaded.[/li][li]Click ‘Add Reply’.[/li][/ul]

Let’s test your RAM to ensure your RAM is OK

[ul]
[li]Click Start, type mdsched.exe in the Search box, and then press Enter.[/li][li]Choose whether to restart the computer and run the tool immediately or schedule the tool to run at the next restart.[/li][li]Windows Memory Diagnostics runs automatically after the computer restarts and performs a standard memory test automatically. If you want to perform fewer or more tests, press F1, use the Up and Down arrow keys to set the Test Mix as Basic, Standard, or Extended, and then press F10 to apply the desired settings and resume testing.[/li][li]When testing is completed, the computer restarts automatically. You’ll see the test results when you log on.[/li][/ul]