• Now's your chance win big! Join our community and get entered to win a RTX 2060 GPU, plus more! Join here.

    Meet Stan Dmitriev of SurrogateTV on the Pi Cast TODAY! The show is live August 11th at 2:30 pm ET (7:30 PM BST). Watch live right here!

    Professional PC modder Mike Petereyns joins Scharon on the Tom's Hardware Show live on Thursday, August 13th at 3:00 pm ET (8:00 PM BST). Click here!

Question BSODs ntoskrnl.exe (nt+ ...). Windows 8.1

Jun 11, 2020
4
0
10
0
Hello!
I have BSOD problems with ntoskrnl.exe mainly on my laptop.

Usually BSOD appears when I work with DAW.

Tested by sfc /scannow - I fixed some errors before, in this moment it's ok, but BSODs still appears. No errors with memory tests.

Could you help with it?

Here is my dump files:
https://drive.google.com/file/d/1LbSJPJ_VJzML9N0aRU3LL_LR4i7FoE-a/view?usp=sharing

Computer name: PETER
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: 3570R/370R/470R/450R/510R/4450RV, SAMSUNG ELECTRONICS CO., LTD., NP470R5E-X01RU
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 17059901440 bytes (15,9GB)

Crash Dump Analysis

Crash dumps are enabled on your computer.

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

On Wed 10.06.2020 22:33:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061020-5796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x3B (0xC0000046, 0xFFFFF8023F755A9C, 0xFFFFD0002424EBF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 10.06.2020 22:33:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ks.sys (ks!KsRecalculateStackDepth+0x1D7)
Bugcheck code: 0x3B (0xC0000046, 0xFFFFF8023F755A9C, 0xFFFFD0002424EBF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 08.06.2020 23:16:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060820-5687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x3B (0xC0000046, 0xFFFFF80328B4CA9C, 0xFFFFD00037893BF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 06.06.2020 0:52:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060620-5906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x3B (0xC0000046, 0xFFFFF80006EEDA9C, 0xFFFFD000205E3BF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 03.06.2020 15:26:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060320-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x19 (0xD, 0xFFFFE00034132AE0, 0xE4990620DFBB10ED, 0xF616609C7DFF6670)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. 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.



On Sat 30.05.2020 2:02:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\053020-32796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x143316)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00179CFB880, 0xFFFFD001AB1F9980)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. The power state transition timed out waiting to synchronize with the PnP subsystem.
This is 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 Mon 25.05.2020 15:16:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052520-29953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1404C0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001029757F0, 0xFFFFD00102975748, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Last edited:
Jun 11, 2020
4
0
10
0
Do you have a video camera? Ks.sys is a kernel file tied to video camera on PC. I don't see an obvious camera driver on laptop website. tbh, I am not sure what it would be on there.

Non RU model of laptop (only so I can read it) - https://www.samsung.com/hk_en/support/model/NP470R5E-X01HK/

I have asked a friend to convert dumps
Thanks for your reply.
I have only built-in Webcam SC-10HDD12636P on my laptop. It works normally. Driver vers. 6.3.9600.17217 (21.06.2006). Try to update it, but not successfully.
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://unsecuredspermwhale.htmlpasta.com/
File information:061020-5796-01.dmp (Jun 10 2020 - 15:33:13)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Driver warnings:*** WARNING: Unable to verify timestamp for emusba10.sys
Probably caused by:emusba10.sys (Process: Cubase LE AI E)
Uptime:1 Day(s), 6 Hour(s), 48 Min(s), and 21 Sec(s)

File information:060820-5687-01.dmp (Jun 8 2020 - 16:16:59)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Driver warnings:*** WARNING: Unable to verify timestamp for emusba10.sys
Probably caused by:emusba10.sys (Process: Cubase LE AI E)
Uptime:0 Day(s), 0 Hour(s), 49 Min(s), and 11 Sec(s)

File information:060620-5906-01.dmp (Jun 5 2020 - 17:52:30)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Driver warnings:*** WARNING: Unable to verify timestamp for emusba10.sys
Probably caused by:emusba10.sys (Process: Cubase LE AI E)
Uptime:2 Day(s), 7 Hour(s), 01 Min(s), and 47 Sec(s)

File information:060320-5265-01.dmp (Jun 3 2020 - 08:26:23)
Bugcheck:BAD_POOL_HEADER (19)
Driver warnings:
Probably caused by:Pool_Corruption (Process: Cubase LE AI E)
Uptime:0 Day(s), 0 Hour(s), 39 Min(s), and 09 Sec(s)

File information:053020-32796-01.dmp (May 29 2020 - 19:02:38)
Bugcheck:DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:
Probably caused by:usbccgp.sys (Process: System)
Uptime:1 Day(s), 4 Hour(s), 59 Min(s), and 23 Sec(s)

File information:052520-29953-01.dmp (May 25 2020 - 08:16:51)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Driver warnings:
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 0 Hour(s), 54 Min(s), and 15 Sec(s)
Comment: I'm seeing 2 different motherboards so these dump files are from 2 different systems. I also got the "2 or more types of RAMs" notice which likely just means each motherboard had a different type of RAM (they didn't match between the 2 boards).

The first 4 dumps are probably from the newer system while the rest are from the older system.

We can't debug 2 different systems at the same time.

Possible current motherboard: SEC_SW_REVISION_1234567890ABCD ?

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Reactions: Peter M.

Colif

Win 10 Master
Moderator
the errors on 6th, 8th & 10th (if on newest board) all blame E-MU USB-Audio 1.0 Driver
Nov 26 2007emusba10.sysE-MU USB-Audio 1.0 driver (E-MU Systems)

its getting a little long in the tooth. Even for win 8.1 standards. See if anything newer.

2 computers? one install? What you doing? moving installs?
 
Reactions: Peter M.
Jun 11, 2020
4
0
10
0
Thanks to all for your answers!
At the beginning of June I upgraded my laptop with new bigger memory RAM (AMD instead Samsung) and also installed another modification of BIOS. The motherboard is the same. Sorry that I forgot to mention it.

You are absolutely right, because usually problems appears with Cubase DAW and EMU-0404 USB external sound card. The main sin was on old driver (2007) and I have found beta-version (2010) for this audio card EMUU_PCAppDrv_US_1_40_00_BETA.exe and updated old driver a few days ago. No I'm testing how it works.

For my disappointed this good quality sound card is out of support too many years and there is not enough good stability drivers.
 
Jun 11, 2020
4
0
10
0
By the way could you suppose what does
usbccgp.sys (dump #5, May 29) mean ?
I connect my EMU-0404usb on USB-2.0.
Maybe problem with USB-2.0 also? But any others devices works always normally with it.
 

Colif

Win 10 Master
Moderator
That error mentions ks again, so it looks like its the webcam again

Best way to figure out what is using that driver would be to look in system information/Components and look at the areas like sound devices or inputs as that is most likely devices to use the USB driver as this is just a default driver for USB devices.
 
Reactions: Peter M.

ASK THE COMMUNITY