Windows 10: BSOD ntoskrnl.exe, ntkrnlmp.exe driver errors, can't identify the 3rd

Hi There,
Who can assist me with identifying the 3rd party driver that is causing my PC to crash with a BSOD. I have had several crashes, and for as much as I can identify all caused by one or more faulty/buggy driver(s).

Much appreciated, rene

Attachment 105591

:)

 

BSOD ntoskrnl.exe+142480, 0x00000101, did test: DRIVER_VERIFIER_DETECTED_VIOLATION (avc3.sys)

Hello guys!

I have a lot of trouble with BSOD atm. Always while playing csgo after some hours I got a crash.

Crash says: CLOCK_WATCHDOG_TIMEOUT

I have analyzed the .dmp and did the driver test with the verifier.

Thats the result:

With the Verifier:

DRIVER_VERIFIER_DETECTED_VIOLATION (avc3.sys)

With bluescreenview

1. Bug Check Code: 0x00000101

2. Caused By Driver: ntoskrnl.exe

3. Caused By Address: ntoskrnl.exe+142480

With "whoCrashed":

This was probably caused by the following module:
ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD0009EC00180, 0x6)

Error: CLOCK_WATCHDOG_TIMEOUT

p.s I did run prime95 with focus on ram, 3hours, no bad result.

Do you have any idea about my problem? Can you help me ?

Thanks!

 

Getting BSOD randomly...

Sometimes i get random BSOD while playing or even on the start up.

On Thu 3/1/2018 1:56:51 PM your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\030118-20843-01.dmp

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

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8029372790E, 0xFFFFEF0370096BF8, 0xFFFFEF0370096440)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

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 system thread generated an exception which the error handler did not catch.

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

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

On Thu 3/1/2018 1:56:51 PM your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x4046)

Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8029372790E, 0xFFFFEF0370096BF8, 0xFFFFEF0370096440)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.

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

The crash report.

Anyone can help ?

 

You have 3 different kinds of memory installed. This can lead to problems like you are seeing (Bugcheck A for instance).

Code: [Memory Device (Type 17) - Length 27 - Handle 0010h] Physical Memory Array Handle 000eh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 2048MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM0 Bank Locator BANK0 Memory Type 01h - Other Type Detail 0080h - Synchronous Speed 1066MHz Manufacturer FF04000000000000 Serial Number Asset Tag Number Part Number RMB2GB484CA4-13HC [Memory Device (Type 17) - Length 27 - Handle 0011h] Physical Memory Array Handle 000eh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 2048MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM1 Bank Locator BANK1 Memory Type 01h - Other Type Detail 0080h - Synchronous Speed 1066MHz Manufacturer FF04000000000000 Serial Number Asset Tag Number Part Number RMB2GB484CA4-13HC [Memory Device (Type 17) - Length 27 - Handle 0012h] Physical Memory Array Handle 000eh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 2048MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM2 Bank Locator BANK2 Memory Type 01h - Other Type Detail 0080h - Synchronous Speed 1066MHz Manufacturer CE80000000000000 Serial Number Asset Tag Number Part Number M378B5673FH0-CH9 [Memory Device (Type 17) - Length 27 - Handle 0013h] Physical Memory Array Handle 000eh Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 2048MB Form Factor 09h - DIMM Device Set [None] Device Locator DIMM3 Bank Locator BANK3 Memory Type 01h - Other Type Detail 0080h - Synchronous Speed 1066MHz Manufacturer 4F01000000000000 Serial Number Asset Tag Number Part Number TS256MLK64V3U[/quote] Try removing the DIMMs in BANK 2 and BANK 3 and run for awhile, see how things are if okay theneither stay with 4GB or find 4 matching memory modules to run with.

You could also try testing memory before doing this, to see what it shows you:

===================================================
RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information


MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
===================================================

Even if no errors, remove the 2 memory modules and test.

Also, the BIOS in this PC is old, BIOS Release Date 07/21/2009 There are nor drivers for anything above Windows 7 and no drivers at all available on the HP web site for this PC.