Windows 10: BSOD in a Brand New Desktop

HI


I have been having BSOD on my Dell All in One since the the beginning. I am still in the warranty but before I contact Dell, I want a Microsoft technician to have a look on the Minidump file analysis. I have updated all drivers and reinstalled Windows couple of times but these BSOD keep coming. I would be grateful to you.


Thanks in Advance

Mudher


Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff801`3cc1f000 PsLoadedModuleList = 0xfffff801`3d039a50
Debug session time: Mon Jan 14 03:11:34.469 2019 (UTC - 5:00)
System Uptime: 0 days 4:48:27.233
*******************************************************************************
* *
* 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: ffffd4ea40000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8013cd29440, 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
ffffd4ea40000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!MI_READ_PTE_LOCK_FREE+0
fffff801`3cd29440 488b01 mov rax,qword ptr [rcx]

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

TRAP_FRAME: fffffd8cf8a2f2e0 -- (.trap 0xfffffd8cf8a2f2e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd4ea40000000
rdx=ffffd4ea753a9000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8013cd29440 rsp=fffffd8cf8a2f478 rbp=fffffd8cf8a2f589
r8=ffff9d8dae69a300 r9=0000007ffffffff8 r10=0000000000000001
r11=fffffd8cf8a2f718 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MI_READ_PTE_LOCK_FREE:
fffff801`3cd29440 488b01 mov rax,qword ptr [rcx] ds:ffffd4ea`40000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8013cde2369 to fffff8013cdd0b40

STACK_TEXT:
fffffd8c`f8a2f198 fffff801`3cde2369 : 00000000`0000000a ffffd4ea`40000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffd8c`f8a2f1a0 fffff801`3cdde78e : 00000000`00000002 00000000`00000034 ffffd4e2`00cd13a0 00000000`00000075 : nt!KiBugCheckDispatch+0x69
fffffd8c`f8a2f2e0 fffff801`3cd29440 : fffff801`3cc790be ffffc401`9a274000 fffffd8c`f8a2f589 00000000`00001000 : nt!KiPageFault+0x44e
fffffd8c`f8a2f478 fffff801`3cc790be : ffffc401`9a274000 fffffd8c`f8a2f589 00000000`00001000 fffffd8c`f8a2f589 : nt!MI_READ_PTE_LOCK_FREE
fffffd8c`f8a2f480 fffff801`3cd59389 : ffff9d8d`b0d55b20 fffff800`546e6f43 ffff95cc`cec15c8b 00000000`00000000 : nt!MmFreeContiguousMemory+0x3e
fffffd8c`f8a2f4f0 fffff800`86065457 : ffff9d8d`b088b810 fffff800`85f2c855 ffff9d8d`b088b810 ffff9d8d`b0889010 : nt!HvlpFreeOverlayPages+0x9
fffffd8c`f8a2f520 fffff800`85f9fe20 : ffff9d8d`c30f502a ffff9d8d`b0889010 00000000`00000000 00000000`00000000 : storport!StorPortExtendedFunction+0x23437
fffffd8c`f8a2f5f0 fffff800`85fba3d3 : ffff9d8d`b0940f60 fffff800`8604d2d7 ffff9d8d`b08e11a0 ffffc401`94759180 : iaStorAVC!Wcdl::Allocator::freeContiguous+0x20
fffffd8c`f8a2f630 fffff800`85fb1d67 : ffffc401`9a87f440 fffff800`85f3c834 ffff9d8d`b08330d0 ffff9d8d`b0940f60 : iaStorAVC!readSmartAttribsCompletion+0x2bf
fffffd8c`f8a2f6e0 fffff800`85fae81c : ffff9d8d`b0940f60 fffffd8c`f8a2f901 ffffc401`9a87f440 fffff800`8601c820 : iaStorAVC!NvmRequest::complete+0x1b7
fffffd8c`f8a2f720 fffff800`85fad2ef : ffff9d8d`b0940f60 fffffd8c`f8a2f910 00000000`00000000 ffff9d8d`be623000 : iaStorAVC!NvmePort:rocessCompletionQueueForSharedInterrupt+0x144
fffffd8c`f8a2f7b0 fffff801`3ccde3a7 : ffffc401`9475bf80 fffffd8c`f8a2f910 ffff9d8d`b08ae018 00000000`00000000 : iaStorAVC!NvmePort::dpc+0x47
fffffd8c`f8a2f810 fffff801`3ccdd9ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x2e7
fffffd8c`f8a2f950 fffff801`3cdd455a : ffffffff`00000000 ffffc401`94759180 00000000`00000000 ffffc401`94769200 : nt!KiRetireDpcList+0x1ae
fffffd8c`f8a2fb60 00000000`00000000 : fffffd8c`f8a30000 fffffd8c`f8a29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
storport!StorPortExtendedFunction+23437
fffff800`86065457 0f1f440000 nop dword ptr [rax+rax]

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: storport!StorPortExtendedFunction+23437

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: storport

IMAGE_NAME: storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_AV_storport!StorPortExtendedFunction+23437

BUCKET_ID: X64_AV_storport!StorPortExtendedFunction+23437

Followup: MachineOwner
---------

:)

 

Brand new PC BSoD

Hi,

Corrupted drivers and system files are one of the possible reasons why this issue is happening. We'd like to get additional information to help resolve the issue. Kindly answer the following questions below:

• What is the stop error code showing on the screen whenever you experience BSoD? (e.g.: 0x0000000A, 0x0000003B, and 0x000000EF)
  
• Did you installed any third-party applications on your new computer before the issue started?
  
• Is there a specific action you're doing on the computer that triggers BSoD?
  

In the meantime, we suggest performing the possible solutions in this
article
to help resolve blue screen errors.

We'll keep an eye out for your response.

 

HELP ! BSOD with brand new computer.

Hi,

I just bought a brand new computer running with Windows 10.

When I first turned it on, I had a BSOD within 1min. I had to do a "hard" restart because it crashed again when it restarted.

While I was doing the initial configuration, it may have crashed 3 times more. Then, I started to install the usual software (Office, Adobe, Anti-virus...) and it crashed again at least twice.

I did all the steps that are listed here.

Below is the OneDrive link to the zipped folder:

Files_dmp.zip

There should be the last three .dmp file, the system info and the computer specification.

If you need any other information, please let me know.

Thank you for your help !

 

brand new lap top battery

I ran the troubleshoot power option and it said “Display brightness setting is too high”

but it’s a brand new laptop, i should think I could expect the most from it.

I haven’t tried the next steps uou have suggested yet.