How to identify why new Windows 10 computer keeps restarting

January 18, 2016 at 00:01:30
Specs: Windows 10
Hello Guys,

I have an issue with a recently buyed Windows 10 system. It keeps rebooting every ~10 minutes or so. Weird thing is it generally do not happen if I am running an app, like for example watching a video or playing a game. But as soon as the video is finished, bam! reboot.

I have looked on the website already and generated this report (below).
Does it means that a specific device is causing it? Are there ways to identify the cause? I have already tried to install the latest drivers of my mouse/keyboard/sound system.

I also tried to reset the pc, which helped for a week before the issue occurred again.


Index : 18112
EntryType : Error
InstanceId : 1073742825
Message : The description for Event ID '1073742825' in Source 'BugCheck' cannot be found. The local computer may
not have the necessary registry information or message DLL files to display the message, or you may not
have permission to access them. The following information is part of the event:'0x000000d1
(0xfffff80062307838, 0x0000000000000002, 0x0000000000000008, 0xfffff80062307838)',
'C:\WINDOWS\MEMORY.DMP', 'ee7504f7-b59e-45bc-8765-938a1755e57f'
Category : (0)
CategoryNumber : 0
ReplacementStrings : {0x000000d1 (0xfffff80062307838, 0x0000000000000002, 0x0000000000000008, 0xfffff80062307838),
C:\WINDOWS\MEMORY.DMP, ee7504f7-b59e-45bc-8765-938a1755e57f}
Source : BugCheck
TimeGenerated : 1/18/2016 8:48:07 AM
TimeWritten : 1/18/2016 8:48:07 AM
UserName :

See More: How to identify why new Windows 10 computer keeps restarting

January 18, 2016 at 00:27:36
If it's less than 12 months it will be covered by the manufacturer's warranty so you should contact them (the manufacturer, not the vendor).

They are obliged to repair or replace it.

That's what warranties are for, so make use of it!

message edited by phil22

Report •

January 18, 2016 at 02:08:11
"Are there ways to identify the cause?"
Yes, need an Minidump ( MEMORY.DMP, is too large ) Change the setting to give you a minidump ( Small memory dump ) & when you get the problem again, you should have a minidump.

Copy & Paste the dump (.dmp ) file onto your desktop & then upload it using ZippyShare. No account/registration needed. Post the link please.
Instructions on how to use ZippyShare.
Minidump file is located in C:\Windows\Minidump
How to see hidden files in Windows

message edited by Johnw

Report •

January 18, 2016 at 04:07:38
@johnw: Thanks!
I'll be sure to do it.

@phil22: indeed. I would like to make sure it's not something I can easily solve before sending my computer to repair which takes a few weeks.

Report •

Related Solutions

January 18, 2016 at 07:14:34
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL would imply bad drivers, but the fact that your event viewer can't pull up the normal BSOD text is troubling. Right-click on the start button, run the Command Prompt (Admin), and run:
dism /online /cleanup-image /restoreHealth
Once that's done, run
sfc /scannow
If SFC says something about fixing something or requiring a reboot, do so. If that doesn't solve your issues, look in to updating your drivers. If you post your minidump, I'll see if I can't find which driver caused the system crash.

How To Ask Questions The Smart Way

Report •

January 18, 2016 at 09:13:15
Thanks for your answer, interesting!
It doesn't give anything though:

''Windows Resource Protection did not find any integrity violations.''

I contacted the manufacturer as well and they told me to first do a complete re-install (factory settings); which I did.
Last time it solved the issue for 3-4 days. (though I didn't do the complete reset). Though I fear the issue will re-appear.

Again thanks for all the interesting answers. I'll post the minidump should it happens.

message edited by Benzaa

Report •

January 18, 2016 at 11:00:48
Do not forget the possibility that this is a hardware fault.

Always pop back and let us know the outcome - thanks

Report •

January 19, 2016 at 00:21:03

So it happened again. Here's the minidump file:


Report •

January 19, 2016 at 00:36:33
* Bugcheck Analysis *
* *

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 kernel debugger is available get stack backtrace.
Arg1: fffff801fe3a7838, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff801fe3a7838, address which referenced memory

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes


fffff801`fe3a7838 ?? ???






TRAP_FRAME: ffffd0007a7a56f0 -- (.trap 0xffffd0007a7a56f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff801fe3a7838 rbx=0000000000000000 rcx=00001ffe12a7ffd8
rdx=ffffe001ed588970 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801fe3a7838 rsp=ffffd0007a7a5888 rbp=0000000000000000
r8=000000002016f837 r9=0000000001d15262 r10=ffffd0007a77a180
r11=fffff803596ec422 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff801`fe3a7838 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803595642e9 to fffff80359559770

fffff801`fe3a7838 ?? ???

ffffd000`7a7a55a8 fffff803`595642e9 : 00000000`0000000a fffff801`fe3a7838 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffd000`7a7a55b0 fffff803`59562ac7 : ffffe001`e9dbe8d0 fffff801`f9ea1367 ffffe001`f14c4760 ffffe001`f14c4760 : nt!KiBugCheckDispatch+0x69
ffffd000`7a7a56f0 fffff801`fe3a7838 : fffff801`faa52389 00000000`00000000 ffffe001`e9568010 ffffc001`00000002 : nt!KiPageFault+0x247
ffffd000`7a7a5888 fffff801`faa52389 : 00000000`00000000 ffffe001`e9568010 ffffc001`00000002 00000000`00000f45 : ICCWDT+0x7838
ffffd000`7a7a5890 fffff801`faa5223f : 00000000`00000000 00000000`00000000 ffffd000`7a7a5a10 00000000`00000000 : Wdf01000!FxTimer::TimerHandler+0xd5
ffffd000`7a7a58d0 fffff803`59460a16 : ffffd000`7a7a5a40 ffffd000`7a7a5a10 ffffd000`7a7a5a10 00000000`00000001 : Wdf01000!FxTimer::_FxTimerDpcThunk+0xef
ffffd000`7a7a5910 fffff803`5955c52a : 00000000`00000000 ffffd000`7a77a180 ffffd000`7a786bc0 ffffe001`f0086080 : nt!KiRetireDpcList+0x5f6
ffffd000`7a7a5b60 00000000`00000000 : ffffd000`7a7a6000 ffffd000`7a79f000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a




MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image



Followup: MachineOwner

*** Memory manager detected 32799 instance(s) of page corruption, target is likely to have memory corruption.

Report •

January 19, 2016 at 00:41:03
Some of the clues/possibles point to memory.

Remove the memory, clean the contacts & only try/test one stick at a time.

Trick To Clean Pins Of Physical Memory ( RAM ) From Dirt

message edited by Johnw

Report •

January 19, 2016 at 09:27:14
*** Memory manager detected 32799 instance(s) of page corruption, target is likely to have memory corruption.

That's a whole lot of corrupted pages right there.

In the text box on your task bar, type:

and select Windows Memory Diagnostic. From there, pick the Restart now and check for problems. Make sure the "Windows Memory Diagnostics Tool" screen pops up and starts doing its thing. Then just walk away.

Next time you log in to Windows, wait a few minutes. You should get a notification about the test results. If the report says there's memory issues, make note of the wording, and give it to the manufacturer. That report would be fairly definitive proof that the memory's bad.

How To Ask Questions The Smart Way

message edited by Razor2.3

Report •

Ask Question