• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended
15t-dy200
Microsoft Windows 10 (64-bit)

This lapotp has been pixel freezing or crashes in the middle of watching moving or doing work. No log, no dump file. Ran the HP hardware diagnostics, didn't find anything.  Uninstalled video drive and reinstalled few times. Still same thing.  Also, BIOS, all drivers are most recent. There were a lot of same issues in the product reviews(1 stars) that have the same problem, has anyone found a solutions?  

6 REPLIES 6
HP Recommended

Hello,

to get the dump file you have to set this: in file explorer, you right-click on This PC and select properties, on the left side you have Advanced system settings and under tab Advanced you have another Settings button under Startup and Recovery. In this window under Write debugging information select Small memory dump(256 KB), next time your computer crashes you can open this file with WinDbg.exe, which you should run as administrator(and under file, you have the option to open crash dump) so you will see where the problem is and fix it or ask us more accurately. Looking forward to hearnig from you.

Regards

HP Recommended

Thanks for replying. I did set up small dump file before, but most crashes didn't dump files and just restarted computer after frozen for 20-30 seconds or so. It crashes at least 3 times since yesterday. And finally there's one dump file. The crash happens mostly in the middle of playing videos or youtube, but it's definitely random.  here's info from a dump file by running: !ananlyze -v:

 

For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff804`579f5a80 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff882`6f5bf130=000000000000000a
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8826f5c0560, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000c3, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80457a038a6, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3968

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on HP15IN

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12200

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 79

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: fffff8826f5c0560

BUGCHECK_P2: ff

BUGCHECK_P3: c3

BUGCHECK_P4: fffff80457a038a6

WRITE_ADDRESS: fffff804582fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8045820f330: Unable to get Flags value from nt!KdVersionBlock
fffff8045820f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 fffff8826f5c0560 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff8826f5bf270 -- (.trap 0xfffff8826f5bf270)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000001 rbx=0000000000000000 rcx=0000000100000400
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80457a038a6 rsp=fffff8826f5bf400 rbp=fffff8826f5bf480
 r8=0000000000000000  r9=0000000000000001 r10=ffff8f82284ec080
r11=00000062f09fdb60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!KiGeneralProtectionFault+0x2e6:
fffff804`57a038a6 8b85e0100000    mov     eax,dword ptr [rbp+10E0h] ss:fffff882`6f5c0560=????????
Resetting default scope

STACK_TEXT:  
fffff882`6f5bf128 fffff804`57a07a69     : 00000000`0000000a fffff882`6f5c0560 00000000`000000ff 00000000`000000c3 : nt!KeBugCheckEx
fffff882`6f5bf130 fffff804`57a03d69     : 00000000`0000003d fffff804`00000000 00000000`00000001 ffff8f82`284ec1c0 : nt!KiBugCheckDispatch+0x69
fffff882`6f5bf270 fffff804`57a038a6     : ffff8f82`284ec080 000001e3`73db0000 fffff882`6f5bf418 ffffffff`ffc42f80 : nt!KiPageFault+0x469
fffff882`6f5bf400 00007ffb`927e046d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x2e6
00007ffb`96d588d1 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`927e046d


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80457a038a9 - nt!KiGeneralProtectionFault+2e9
	[ 00:10 ]
1 error : !nt (fffff80457a038a9)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     memory_corruption
---------

 

 

HP Recommended

Hello,

according to your .dmp file, I would suggest reinstalling google chrome, if this doesn't work, check drivers and run the memory test. In the worst case, you will have to reinstall Windows, if even this doesn't solve the problem, it is probably physical damage to your hardware, then I recommend visiting service, but as I said, first try reinstalling chrome and memory test. I hope that this will work.

Regards

HP Recommended

I will use Firefox instead of chrome for few days. If it's not crashing, then it's chrome, otherwise, Reinstall OS will be the next step. I ran HP hardware Memory test, and it passed. Maybe I will find a third party Memory test software. This crash is a common problem with this model by reading the product review.  Anyway, thanks for the quick reply.

HP Recommended

Same issue here - happened even during the initial OS setup!  Sent back to HP after updating BIOS and video drivers failed to resolve.  They did not replace any hardware - just 'updated bios' and 'system operative reistalled' (not my typo).  Of course, this did nothing, and issue persists within first day of use after nearly 3 weeks w/o a PC.  New tech support case wants me to send back again.  Why am I skeptical? 🙂

HP Recommended

I have tried:

1. reset computer to factory setting with no user data via F11, updated all drivers and it crashes.

2. clean OS installation by downloading Windows 10 from Microsoft, updated all drivers and it crashes.

 

BIOS was updated. Intel website has the latest graphic card driver, but it still crashes. I am pretty sure it's hardware defected, but hardware scans can't find anything. Crash usually happens after few hours. I also used coreTemp to monitor CPU temp, but it's within stable range. HP warranty box is on its way. This is a  common fatal problem with this model, HP really should find out the root cause.

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.