BSOD on HP Omen - Sysnative Forums BSOD Forum

URL: Sysnative Forums - (2) BSOD on HP Omen | Sysnative Forums 

The dump file is overflowing with NTSTATUS exception error code 0xc0000147 - which refers to the page file.

From Microsoft - 0xc147 -

Microsoft Docs said:

NTSTATUS 0xc0000147

Unable to Create Paging File.

The creation of the paging file %hs failed (%lx). The requested size was %ld.

Your page file may be corrupted. Turn page file (virtual memory) off via SYSTEM in Control Panel; delete pagefile (see CODE box below) - c:\pagefile.sys

Note - you may have to change file attributes and un-hide the pagefile. Bring up an Admin CMD prompt; Type/paste the following one line at a time; hit enter after each line) - check for pagefile first (1st command after "cd" command)l; then un-hide it (2nd command); then delete it (last command) - c: is assumed to be your Windows OS drive -

Code:

cd c:\

dir /a c:\pagefile.sys

attrib -h c:\pagefile.sys

del c:\pagefile.sys

Turn page file (virtual memory) back on - System managed - for all drives

Also, for info, a 0xc147 exception code could mean that there is a problem with the hard drive.

I would also advise you to run chkdsk from the CMD prompt as well - chkdsk /f /r - then reboot the system

PLEASE be sure to run Driver Verifier as @x BlueRobot has asked you to do.

Regards. . .

jcgriff2

​

BSOD Posting Instructions - Windows 10, 8.1, 8, 7 + Vista ` ` `Sysnative Driver Reference Table (DRT)

https://www.sysnative.com/
Sysnative Hex-Decimal-UNIX Date Conversion

Has Sysnative Forums helped you?
Please consider donating to help support the forum.
Thank You!

2 Dell Inspiron 7746 Laptops having PnP Detected Fatal Error - Bleeping Computer

 

https://www.bleepingcomputer.com/forums/t/748442/2-dell-inspiron-7746-laptops-having-pnp-detected-fatal-error/#entry5162721

Thanks for posting that.

 

I'm rather taken by the old timestamps on some of the 3rd party drivers.

 

 

stdcfltn.sys Fri Jul 13 19:30:14 2012 (5000AF86) - ST Microelectronics Disk Class Filter Driver for Accelerometer 


IntelPcc.sys Tue Apr 29 20:13:23 2014 (53604023) - Intel Collaborative Processor Performance Control (​CPPC) driver 


e1d65x64.sys Thu Jun 18 12:37:56 2015 (5582F3E4) - Intel Ethernet - Driver Reference Table (DRT) | e1d65x64.sys (sysnative.com)

O2FJ2w7x64.sys Tue May 13 21:46:47 2014 (5372CB07) -  O2Micro SD Reader Driver - Driver Reference Table (DRT) | O2FJ2w7x64.sys (sysnative.com)

dptf_acpi.sys Tue Jun 10 15:52:05 2014 (539761E5) - Intel Dynamic Platform Thermal Framework Driver - Driver Reference Table (DRT) | dptf_acpi.sys (sysnative.com)

ST_Accel.sys Sun Apr 20 23:28:44 2014 (5354906C) - STM 3-Axis Accelerometer driver

DellRbtn.sys Fri Aug  3 17:32:54 2012 (501C4386) - OSR Open Systems Resources Airplane Mode Switch Driver  - Driver Reference Table (DRT) | DellRbtn.sys (sysnative.com)
Netwtw04.sys Mon Dec 31 10:32:13 2018 (5C2A367D) - Intel wifi driver - Driver Reference Table (DRT) | Netwtw04.sys (sysnative.com)

The above all pre-date Windows 10, except for the last one. I noted it here because networking drivers are typically updated at least once per year and yours is 2+ years old. There are several other drivers from 2016, 7, 8, 9 as well, but they were written for W10 as their timestamps are >2015.

 

However, as W10's drivers are updated, so should 3rd party drivers.

 

All of the above listed drivers were loaded into RAM at the time of the BSODs and therefore could be involved in future BSODs.

 

Regards. . .

 

jcgriff2

BSOD - Caused by Acronis driver - file_protector.sys

 https://www.bleepingcomputer.com/forums/t/748188/bsod-invalid-file-protector/?p=5162544

Probable cause - Acronis driver file_protector.sys

_________________________________________________________________________________

The probable cause of your latest dump was file_protector.sys -

file_protector.sys Mon Oct 15 10:42:57 2018 (5BC4A771)

It is an Acronis driver - Acronis Cyber Protect Cloud: file_protector.sys consumes a lot of RAM | Knowledge Base

 

- Acronis File Protector causing BSOD PC Crash | Acronis Forum

 

Make sure that you have the most recent version of Acronis installed as your driver is from 2018.

 

Regards. . .

 

jcgriff2

DPC_WATCHDOG_VIOLATION everyday - 0x133

MBAM Forums - https://forums.malwarebytes.com/topic/256485-dpc_watchdog_violation-everyday/?do=findComment&comment=1364908



Test RAM and HDD.

Update NVIDIA driver

BSOD- Unexpected_Store_Exception

Hi. . .

It is likely that your hard drive is failing.

Your dumps -

BugCheck EF, {ffffbd8bef699140, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+115 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck EF, {ffffd98a3a8ce140, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+115 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 154, {ffff8e0b93ae8000, ffffc1884e8b9000, 2, 0}
Probably caused by : hardware_disk
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 154, {ffffc90f417c6000, fffffa0b18a20000, 2, 0}
Probably caused by : hardware_disk
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 154, {ffff8b8dc4e03000, ffff83094988a420, 2, 0}
Probably caused by : hardware_disk
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Run SeaTools for DOS, LONG test - https://www.sysnative.com/forums/threads/hard-drive-hdd-diagnostics-sea-tools-for-dos-ssd-test.4072/

Regards. . .

jcgriff2

BSODs since adding internal HD & RAM

Posted Today, 11:19 AM

Hi. . .

Your hard drives according to your msinfo32.nfo file found in the Sysnative folder in Documents, under Storage, Disks area -

You have a Western Digital 1 TB drive - not sure if SSD or HDD - 

Model WDC WD10EZEX-75M2NA0

You have a 4 TB drive - again - unsure of its type -

Model ST4000DM005-2DP166

Another 4 TB Seagate drive - unsure of its type - 

Model Seagate BUP BK SCSI Disk Device

Regards. . .

jcgriff2

Critical Process Died At Start Up Nothing Thus Far Seems To Fix

WMI Virtual Memory Usage

Posted Today, 12:19 PM

Gordefving, on 14 Dec 2019 - 08:29 AM, said:

For the past few days all of the browsers have been crashing (allegedly low memory which makes no sense considering the number of free gigs that I did have available),...

The "low memory" message could be referring to virtual memory and not to physical memory (RAM).

Virtual memory is the usage of the page file for memory instead of using physical RAM. Some apps (like Notepad, for example) writes directly to the page file (virtual memory) instead of writing to physical RAM. Sysinternals Process Monitor from Microsoft does the same thing.

With virtual memory, the system writes to and reads from the page file (c:\pagefile.sys) instead of RAM, making the system very, very slow.

You can run this Windows Management Instrumentation (WMI) app to check on your peak and current virtual memory usage - (I wrote the app, so it is safe) - 

http://www.sysnative.com/apps/jcgriff2/WMI_recoveros_pagefile_jcgriff2_txt.exe

Download and save to Desktop or Documents. RIGHT-click on the EXE, select "Run as Administrator". Upon completion, a Notepad will open (it may be located in the Taskbar). Scroll to the end of the file and you'll see this - 

AllocatedBaseSize=8704
Caption=C:\pagefile.sys
CurrentUsage=1311
Description=C:\pagefile.sys
InstallDate=20131220133842.488186-300
Name=C:\pagefile.sys
PeakUsage=1331
Status=
TempPageFile=FALSE

The two important numbers - 

1. CurrentUsage=1311 = I am currently using 1,311 MB (1.3 GB) of virtual memory (I have about 2 dozen Notepads open due to my BSOD Dump Processing App

2. PeakUsage=1331 = My peak virtual memory usage since the last system re-boot (~1.33 GB virtual memory) - again, likely due to the BSOD Dump Processing App

Anyway, you can use the WMI app to check your virtual memory usage at any time, but specifically when you get the "low memory" messages.

Regards. . .

jcgriff2

J. C. Griffith - Windows Insider MVP Profile Page

FocusRite USB Audio BSODs

Hi. . .



From your post -



[code]STACK_TEXT: 

00000000`00000000 : nt!KeBugCheckEx

00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xdf

00000000`00000002 : nt!VerifierFreeTrackedPool+0x41

01000000`00100000 : nt!ExFreeHeapPool+0x1b5247

ffffa005`d76f71c0 : nt!ExFreePool+0x9

ffffa004`d4ca03d0 : FocusriteUSBAudio+0x6d3f[/code]



FocusriteUSBAudio.sys (Focusrite USB Audio driver) is on the last line of the stack. Given that it is the

only 3rd party driver on the stack, there is no doubt whatsoever that it is

at fault/ the cause of the BSOD.



Also. . .



[code]MODULE_NAME: FocusriteUSBAudio

IMAGE_NAME:  FocusriteUSBAudio.sys



DEBUG_FLR_IMAGE_TIMESTAMP:  5d14e2e4[/code]



Driver timestamp = [b]0x5d14e2e4[/b] converts to [b]Thu, 27 Jun 2019 15:38:12 GMT[/b]



So, the driver is nearly 6 months old.



Regards. . .



jcgriff2

Driver Identification Help

Posted Today, 08:58 AM

Hi - 

ntoskrnl.exe is the Windows kernel and can never be the actual cause of a BSOD. It is merely listed as a default because the real culprit cannot be identified.

hall.dll = Windows Hardware Abstract Layer and again, is not the actual cause.

Your BSODs are being caused by unknown hardware failure, although the failure of Prime95 points us in the direction of the CPU.

Multiple bugchecks (stop codes) verifies the fact that hardware is at fault.

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems for software and driver developers. No dump will ever say "replace your CPU".

Regards. . .

jcgriff2

J. C. Griffith - Windows Insider MVP Profile Page

Bugcheck 0x119 - new pc, frequent BSoD

Bleeping Computer



https://www.bleepingcomputer.com/forums/t/709482/new-pc-frequent-bsod/

Hi. . .

Your system parts link returns an HTTP 404 error (page not found) - https://pcpartpicker.com/list/YCLntp)

I know you said this is a new system and I see the words "custom build" listed. Exactly how old is it? i.e., a week. a moth, 6 months, etc...??

The reason that I ask is because depending in which state that you live in, you MAY be entitled to a brand new system versus the manufacturer/builder attempting to fix your current system.

I would demand a brand new system -- do not allow them to talk you into fixing this system otherwise I fear that you will be stuck with a system that you will have problems with for as long as you own it.

For info, I generally see 1 (one) NVIDIA BSOD for every 1,000 ATI video BSODs. NVIDIA writes some of the finest drivers in the world; ATI for whatever reason, does not.

The Sysnative zip file attachment contained just 3 dump files, yet a Windows app, executed by the Sysnative app -  msinfo32 - WERCON (Windows Error Reporting) section lists a total of 8 (eight) BSODs starting on 5 December 2019 through 9 December 2019. Any idea what happened to the missing 5 dumps?

The date of the BSOD is contained in the file name -

C:\Windows\Minidump\120919-6718-01.dmp
C:\Windows\Minidump\120919-6718-01.dmp
C:\Windows\Minidump\120819-6515-01.dmp
C:\Windows\Minidump\120819-6515-01.dmp
C:\Windows\Minidump\120619-6593-01.dmp
C:\Windows\Minidump\120619-6593-01.dmp
C:\Windows\Minidump\120519-6015-01.dmp
C:\Windows\Minidump\120519-6015-01.dmp

Per the Windows app systemunfo.exe, again, executed by the Sysnative app, shows your initial Windows boot date (the date when Windows was installed and/or first booted) to be:

Original Install Date:     02/12/2019, 01:32:42

That would equate to 2 December 2019, just 3 days prior to the first BSOD per the files that I have examined thus far.

Do you recall the exact date that you took delivery of the system? i.e., did you take delivery of the system between 2 December and 9 December 2019? I'm trying to figure out if the system builder had the system during the BSODs and therefore would have known that they were delivering a defective system to you or not. This would not be the first time where I have seen a systm builder deliver a new system to a client that they knew was BSOD'ing. Shameful if true!

Here are the bugchecks and "probably caused by" for the 3 dumps submitted - 

BugCheck 119, {1, 57d90, 57d92, ffffa604ae98d000}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+1249f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 45900, 45902, ffff9283125eb000}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+1249f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 119, {1, 3eb2, 3eb4, ffffac85e7c54000}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrCompletedPacket+1249f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Bugcheck 0x119 = The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119. This indicates that the video scheduler has detected a fatal violation. This is most likely a hardware failure problem.

"Probably caused by : dxgmms2.sys" =  dxgmms2.sys is a Microsoft DirectX component (driver) and is not the rel culprit here --- it just caught the blame because the real culprit could not be identified.

As I said earlier - contact the system builder immediately and report the fact that you are experiencing BSODs likely caused by something related to video or other unknown hardware failure.

Also mentioned in each of the 3 dumps - your ATI video driver.

I checked the timestamps (dates) on the ATI drivers as found in the BSOD dumps and the drivers are very new, so I doubt that the video drivers are the problem. Here are the two ATI video drivers currently loaded in your system:

atikmdag.sys Tue Nov 26 16:59:33 2019 (5DDDCA75)
atikmpag.sys Tue Nov 26 16:49:59 2019 (5DDDC837)

As you can see - they are just 15 days old.

Again - contact the system builder immediately.

Regards. . .

jcgriff2

Edited by jcgriff2, Today, 04:48 PM.

J. C. Griffith - Windows Insider MVP Profile Page

p.s. I checked the SYSTEM Event Viewer log and found evidence of 5 (five) BSODs starting on 5 December 2019.

Again - the date of system delivery to you is very important here.

Do you recall the date that you took delivery of the system?

To be honest, my curiosity is peaked right now as well! 

Regards. . .

jcgriff2

WHEA Uncorrectable Error - Bugcheck 0x124

Bleeping Computer



WHEA Uncorrectable Error - Bugcheck 0x124

Posted Today, 12:36 PM

Hi. . .

First off, for info, I am NOT a hardware expert and sit on the software side of the fence. Hopefully, a true hardware expert will see this thread and be able to help. I have never built a system and purchase only OEM laptops (HP, Fujitsu, Toshiba, etc...

The bugcheck on both dumps that you submitted was in fact was 0x124 = WHEA = Windows Hardware Error Architecture, a/k/a "Machine Check Exception".

https://en.wikipedia.org/wiki/Machine-check_exception

0x124 BSODs are notoriously difficult to solve because the cause is simply "unknown hardware failure". 

Unfortunately, the dumps are incapable of telling us which piece of hardware has failed (except sometimes for hard drives as the dumps can record I/O errors,  which usually pertain to internal hard drives. Dumps are really only good for figuring out software problems as they can identify the exact line of code that failed, which would aid a software/ driver developer.

All I can really do here is to give you some hardware diagnostic programs to run.

Since it does look like the CPU is involved here and you have an Intel CPU, please run the Intel CPU Diagnostic Test.

Please see post #2 for the Intel CPU test - https://www.sysnative.com/forums/threads/cpu-stress-testing-mersenne-org-prime95-and-intel-processor-diagnostic-tool-ipdt.3908/#post-136620

Before running the Intel diagnostic test, close ALL windows. In fact, it is best to download the CPU test to your Desktop so that you will not have any Windows open at all while running the diagnostic test.

Have you told the shop where you purchased the motherboard from that all is well until you activate (turn on) the turbo mode? Maybe they have some ideas.

You also mentioned having "Clock Watchdog Timeout" errors. In Windows, "WATCHDOG" usually refers to video, but not always.

I therefore would recommend running a video diagnostic test as well - Furmark.

FurMark video card test - https://www.sysnative.com/forums/hardware-tutorials/3907-furmark-display-card-stress-test.html

 

Just out of curiosity, please check the "watchdog directory" (the place where 0x117 WATCHDOG dumps are stored) and obtain an estimate of how many dumps there are in this directory (folder). A WATCHDOG error is also referred to as a "Live Kernel Event" with bugcheck 0x117. A 0x117 is just short of a full-fledged 0x116 BSOD.

 

The location for 0x117 Live Kernel Report dumps = C:\Windows\LiveKernelReports

The easiest way to obtain a quick count - bring up an elevated Admin CMD Prompt screen - https://www.sysnative.com/forums/threads/open-an-elevated-administrative-command-prompt-cmd-windows-10.11712/

Then type/paste - 

dir "C:\Windows\LiveKernelReports\watchdog"  /a >c:\0 & start notepad c:\0

A Notepad will open. Look at the second-to-last line - (this is from my system) -

 Volume in drive C is Windows 8.1 x64
 Volume Serial Number is C8D9-F1EF
 
 Directory of C:\Windows\LiveKernelReports\watchdog
 
01/02/2019  07:33 PM    <DIR>          .
01/02/2019  07:33 PM    <DIR>          ..
06/23/2014  04:41 PM           422,484 WD-20140623-1741.dmp
07/05/2014  11:03 AM           454,679 WD-20140705-1203.dmp
07/10/2014  05:00 PM           425,921 WD-20140710-1800.dmp
07/15/2014  12:39 PM           454,814 WD-20140715-1339.dmp
01/06/2015  06:36 PM           422,603 WD-20150106-1836.dmp
01/16/2015  07:20 AM           423,392 WD-20150116-0720.dmp
01/21/2015  10:07 AM           422,597 WD-20150121-1007.dmp
01/24/2015  04:23 PM           423,664 WD-20150124-1623.dmp
01/25/2015  04:11 PM           420,584 WD-20150125-1611.dmp
05/28/2015  09:39 AM           420,422 WD-20150528-1039.dmp
06/04/2015  11:12 PM           416,696 WD-20150605-0012.dmp
06/16/2015  06:53 PM           422,479 WD-20150616-1953.dmp
08/31/2015  04:02 PM           420,325 WD-20150831-1702.dmp
09/17/2015  06:04 AM           420,298 WD-20150917-0704.dmp
10/19/2015  07:49 PM           420,441 WD-20151019-2049.dmp
10/27/2015  08:14 PM           420,441 WD-20151027-2114.dmp
04/15/2016  01:29 PM           422,613 WD-20160415-1429.dmp
07/16/2016  12:11 PM           422,627 WD-20160716-1311.dmp
08/02/2016  03:48 AM           422,573 WD-20160802-0447.dmp
08/16/2016  10:30 PM           422,543 WD-20160816-2330.dmp
11/29/2016  01:36 PM           422,622 WD-20161129-1336.dmp
07/09/2017  11:52 AM           422,589 WD-20170709-1252.dmp
12/25/2017  01:37 AM           422,580 WD-20171225-0137.dmp
05/14/2018  07:31 PM           422,415 WD-20180514-2031.dmp
05/29/2018  07:13 PM           422,527 WD-20180529-2013.dmp
06/11/2018  07:55 AM           423,323 WD-20180611-0855.dmp
07/26/2018  06:18 PM           423,437 WD-20180726-1918.dmp
08/28/2018  12:11 PM           423,430 WD-20180828-1311.dmp
10/09/2018  05:32 PM           422,575 WD-20181009-1832.dmp
01/02/2019  07:33 PM           423,603 WD-20190102-1933.dmp
              30 File(s)     12,731,297 bytes
               2 Dir(s)  59,301,023,744 bytes free

Second to the last line tells you the number of files (dumps) currently in the directory (folder), so in my case, it is 30.

If you have any problems obtaining the dump count, please let me know. 

Thank you.

Regards. . .

jcgriff2

`

J. C. Griffith - Windows Insider MVP Profile Page