Windows 10: Problems with Game, BSOD, Driver Identifier, DUMPS, Memtest? ; Identifying broken driver...

Hello there people, as seen in the Subject, it is a very complicated one and I will split it up in the parts I have in the subject. Link to the dump files so you can read while downloading: https://workupload.com/archive/msqLSVcQ password is dumpydump as I didn't want anybody just lurking on these files Short summary: The Game I have problems with is PUBG Playerunknown's Battlegrounds My PC: Ryzen 7 3700x 32GB RAM DDR4-3000, not in XMP right now x570 MSI MPG Gaming Edge Wifi Motherboard ZOTAC GTX 1070 PSU: 550w bequiet Straight Power 11 1TB NVMe and 1.5TB HDD 1. Problems with Game PUBG playerunknown's battlegrounds I just wanna say: I play a lot of games. Graphically heavy ones aswell. NONE, I mean literally NONE have problems on running on my system. I have never had such Problems with the game. The problems started about 2 months ago, without any clue on why they could've started no trigger installation or anything Well. I have constant crashes at random points in the game. It is mostly not in the main menu though it has happened, so it is mostly while being out on the field. When crashing it is not giving me a specific error code. so I started to try some troubleshooting. Basic troubleshooting such as: getting rid of OC, driver updating, downgrading and installation of new ones. MANY other stuff. I tried finding answers in the PUBG Forum, and I got some troubleshooting answers which failed aswell. I even reinstalled windows AND even reinstalled windows on a newly bought NVMe drive. Nothing is working. [If you have any new ideas that I probably didn't come up with, please just write them in the Comments. I'll try everything. ] 2. BSOD I got in total 5 BSODs from the Game. Some were: PAGE_FAULT_IN_NONPAGED_AREA, and one was: "IRQL_GT_ZERO_AT_SYSTEM_SERVICE" All of these BSODs MiniDump I have uploaded. It's in the minidumps.rar I of course googled what the BSODs meant, and with the second BSOD "IRQL ... " I found the driver identifier. So I just wanted to try out. Maybe something did went wrong while installing some drivers. I found this: microsoft community link So I just wanted to try the driver identifier. 3. Driver Identifier I have tried the driver identifier now as described in this post: driver identifier link And it instantly crashes on startup with 2 kinds of codes: First it started with: "DRIVER_VERIFIED_DETECTED_VIOLATION" but then this one came. I tried multiple boots and didn't get any other than: "DRIVER_VERIFIER_IOMANAGER_VIOLATION" Now it sadly didn't say after the code which driver was causing this code. So I need the help of you to find out what there is. I uploaded the big MEMORY.dmp because I didn't find the appropriate minidump to the driver identifier so I hope it should be in there. If of course I should look somewhere else for the Dump file of the verifier please let me know, I used this walkthrough : microsoft link @zigzag 4. Memtest? I am writing this in the evening of my timezone. I am going to run memtest through the night. Maybe tomorrow not today, but it will definitely run through at least a night. I hope I could help you out with all the information you need to help me. If you have any questions, please feel free. I don't know if this will work but since I mainly used this guys' stuff, I wanna try to @ him. @ZigZag3143 MS -MVP

:)

 

Identifying driver causing BSOD

My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states ntoskrnl.exe. I have the dump files available, will it be helpful in identifying the driver that is causing this
issue?

 

Help with identifying cause of BSODs - dumps included

These are my memory dumps just from yesterday. Can you please help me identify the cause of these?

012020-8593-01.dmp

012020-9015-01.dmp

012020-9156-01.dmp

012020-10000-01.dmp

https://drive.google.com/open?id=19Z9SfokvWX7zAVXj60cxn38yX80p0QCX

https://drive.google.com/open?id=1XK55k4qOB-1Opfd5ZDQEwM4xJ2mE4M2k

https://drive.google.com/open?id=1lyHE10SjoIAivs8YR20vgX0fQSz5uV4X

https://drive.google.com/open?id=1gPZKoTSebP70RbwZF5oVzxPEDWzvJQgy

My system is fairly new and up to date. I've run numerous tests in the past such as memtest, graphics and cpu testers. I also keep my drivers up to date with Driver Easy.

 

BSOD due to ntoskrnl.exe, can't identify which drivers are causing the problem.

So ı have used verifier and this is the minidump file with report

Report:

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 8.03.2018 18:30:33 your computer crashed

crash dump file: C:\WINDOWS\Minidump\030818-41687-01.dmp

This was probably caused by the following module: wmbenum.sys (WmBEnum+0x1F0)

Bugcheck code: 0xC4 (0x2004, 0xFFFFD7838F0CF958, 0xFFFFF80ACCF601F0, 0xFFFFFC003F2610C8)

Error: DRIVER_VERIFIER_DETECTED_VIOLATION

file path: C:\WINDOWS\system32\drivers\wmbenum.sys

product: Logitech Gaming Software

company: Logitech Inc.

description: Logitech WingMan Virtual Bus Enumerator Driver

Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

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: wmbenum.sys (Logitech WingMan Virtual Bus Enumerator Driver, Logitech Inc.).

Google query: Logitech Inc. DRIVER_VERIFIER_DETECTED_VIOLATION

On Wed 7.03.2018 17:24:25 your computer crashed

crash dump file: C:\WINDOWS\Minidump\030718-42625-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)

Bugcheck code: 0x1A (0x403, 0xFFFFB1814FA77FB0, 0x8000000159167867, 0xFFFFB1F30339E798)

Error: MEMORY_MANAGEMENT

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 severe memory management error occurred.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Minidump: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. (it contains system info and old minidump files as well. old minidumps have their own folder. )