1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

BSOD - whocrashed report

By Jk2k24
Aug 11, 2019
Post New Reply
  1. Hi,
    I have a bsod, I have up to date drivers, memory tests completed successfully and graphics card is fine and up to date. can anyone point me in the right direction please? Thanks in advance :)

    Report:

    Windows version: Windows 10 , 10.0, version 1903, build: 18362
    Windows dir: C:\WINDOWS
    Hardware: Qosmio X70-A, TOSHIBA, Type2 - Board Vendor Name1, Type2 - Board Product Name1
    CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel8664, level: 6
    8 logical processors, active mask: 255
    RAM: 34280136704 bytes (31.9GB)





    Crash Dump Analysis



    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\WINDOWS
    C:\WINDOWS\Minidump

    On Sun 11-Aug-19 10:33:23 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\081119-19390-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
    Bugcheck code: 0xA (0xFFFFF006AF013FA0, 0x2, 0x1, 0xFFFFF8035326987C)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 11-Aug-19 10:33:23 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: netwew01.sys (Netwew01+0x1EF9A5)
    Bugcheck code: 0xA (0xFFFFF006AF013FA0, 0x2, 0x1, 0xFFFFF8035326987C)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\drivers\netwew01.sys
    product: Intel® Wireless WiFi Link Adapter
    company: Intel Corporation
    description: Intel® Wireless WiFi Link Driver

    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwew01.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
    Google query: netwew01.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL



    On Sun 11-Aug-19 10:31:18 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\081119-18546-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8047766A39F, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
     
  2. Cycloid Torus

    Cycloid Torus Stone age computing - click on the rock below.. Posts: 4,111   +1,213

    Corrupt driver/software? Heat? RAM glitch?

    "memory tests completed successfully" - run >7 times, memtest86
    "graphics card is fine and up to date" - recent change / update? DDU and download/reinstall
    "up to date drivers" - go to safe mode and run sfc /scannow as per https://support.microsoft.com/en-us...er-tool-to-repair-missing-or-corrupted-system
    heat? last clean >2 yr; do a clean including under vent hood - might also replace TIM

    The Intel WiFi might be issue. @jobeard for best help.
     
  3. jobeard

    jobeard TS Ambassador Posts: 13,019   +1,561

    @Cycloid Torus noted First & Last DMPs are highly likely to be faulty memory.

    The second is a bad WiFi driver. Win/10 is complicit in network drivers.

    see https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/
     
    Cycloid Torus likes this.

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...