Error 41 BSOD can't figure out

[ajpearl777]

Hi,

My computer keeps crashing almost every 20-45 minutes or whenever it gets left alone for over 10 minutes. I really can't figure out what's going on.

I haven't changed anything in my computer except the power supply in about a year. I keep getting this dump file and I can't figure it out. I thought it was my D drive failing, but I'm starting to think it's something else.

Here are my minidump files if that helps...

https://ufile.io/suo4r
https://ufile.io/qve55

I downloaded WhoCrashed and this is the description:

On Tue 10/23/2018 3:49:52 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102418-11609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x17FB90)
Bugcheck code: 0x7A (0xFFFFAC00A942ED18, 0xFFFFFFFFC0000185, 0x8019C2CC860, 0xFFFFF8054669F194)
Error: KERNEL_DATA_INPAGE_ERROR
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 the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

The Windows dump file:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 10/23/2018 3:29:24 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Alex
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" ></Provider>
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2018-10-23T10:29:24.627936900Z" ></TimeCreated>
<EventRecordID>16640</EventRecordID>
<Correlation ></Correlation>
<Execution ProcessID="4" ThreadID="8" ></Execution>
<Channel>System</Channel>
<Computer>Alex</Computer>
<Security UserID="S-1-5-18" ></Security>
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">true</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

 

[Colif]

event 41 is a reaction, not a cause. At startup, windows runs a report and checks that the previous shutdown went as expected. If it finds it was not expected, it creates event 41.

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

KERNEL_DATA_INPAGE_ERROR

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

try this
search cortana for Command prompt
on the control panel result, right click it and choose run as admin
if you have an ssd, type chkdsk c: /f and press enter
If you have an hdd, type chkdsk c: /f /r and press enter (main difference is ssd don't have sectors so can't run repair on them)
PC will show 2 paragraphs, type y and press enter to run it at startup
restart PC and let chkdsk run

Another option if storage doesn't show any errors
download memtest86 and run it to make a bootable USB. Use it to scan 1 stick of ram at a time, up to 8 passes. Only error count you want is 0, any higher shows likely cause of BSOD. remove/replace any ram sticks that get errors.

Run an AV Scan

I will get someone to look at minidumps and convert them into a form I can read

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/prJc.html

File: 102418-11609-01.dmp (Oct 23 2018 - 06:49:52)
BugCheck: [KERNEL_DATA_INPAGE_ERROR (7A)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 20 Min(s), and 34 Sec(s)

File: 102318-17531-01.dmp (Oct 23 2018 - 04:17:10)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)]
Probably caused by: hardware_disk (Process: MemCompression)
Uptime: 0 Day(s), 0 Hour(s), 54 Min(s), and 23 Sec(s)

Possible Motherboard page: https://www.evga.com/articles/00571/
Possible PDF Manual: https://www.evga.com/support/manuals/files/131-GT-E767.pdf

Comment: 3 RAM modules, 4 GB each, 12 GB total.
Comment: BIOS from 2010.

I can't help you with this. Wait for additional replies. Good luck.

 

[johnbl]

it looks like some service was killed and during the clean up process (involving network sockets) it resulted in a bugcheck I would suspect the old teamviewervpn.sys as the cause. (most likely) or a bug in the network driver.

suspect very old driver:
\SystemRoot\System32\drivers\teamviewervpn.sys Thu Dec 13 01:22:09 2007

Creative Camera Class Upper Filter Driver
\SystemRoot\system32\DRIVERS\CtClsFlt.sys Thu Mar 25 22:37:36 2010
(drivers before 2012 tend to cause problems)

old driver:
CD-ROM Class Filter Driver by Gear Software.
Also comes with iTunes
\SystemRoot\system32\DRIVERS\GEARAspiWDM.sys Thu May 3 12:56:17 2012

other driver not used often:
https://carrona.org/drivers/driver.php?id=IntelHaxm.sys
\SystemRoot\system32\DRIVERS\IntelHaxm.sys Thu Jan 29 18:02:09 2015
(android emulation driver)
----------
10: kd> !error 0xC0000185
Error code: (NTSTATUS) 0xc0000185 (3221225861) - The I/O device reported an I/O error.

you will want to check your hard drive data and power connections.
then run crystaldiskinfo.exe to see if the drive is having errors

windows 8.x and 10 will do low level repairs on your drive but if you have windows 7 you have to do the repairs yourself.
---------
i would also atart cmd.exe or powershell as an admin then run
dism.exe /online /cleanup-image /restorehealth
(3 of the windows core files had their date and time stamp removed, it can indicate a hacked version)