Hi guys, I'll try to keep things brief. I have a custom DAW laptop for music production that started random BSOD soon after I got it 
. I was advised it was likely that Windows had "gone weird" and to re-install windows. The problem seemed to be gone for a while but is back and causing real headaches. I have been trying to debug the problems and have searched all over the internet for solutions and need some tech help. (Hoping its not a hardware issues that came with it new). Sometimes I can go for hours of heavy processing with out any issues and other times I just turn it on, leave it sitting on the table and anything from 5 minutes to 2 hours and the system randomly crashes while sitting idol. ---- the real kicker is my old work laptop that was on XP was upgraded to SSD and win 7 never crashes but doesn't have the spec I need.
Systems Specs:
OS: Windows 8.1 pro
Processor: Intel Core I7 -4800MQ CPU 2.70GHz
RAM: 32 GB
Graphics: AMD Radeon HD 8970M
--------------------------------------------------------------------------------------------------
Here is what I have tried and done:
(a) Used Who crashed and driver verifier to find out what's causing BSOD:
AMD drivers fixed - complete uninstall, updated Intel drivers, reinstalled AMD - this defiantly solved some issues , but new issues started showing.
Removed PQLabs Mutitouch driver,
Removed display link core usb driver,
Removed Yamaha (stienberg) fire-wire driver.
(b) carried out sfc/scannow command x3 times - results clear,
(c) carried out disk check - results clear,
(d) anti virus and malware scans - results clear,
(e) tried expand.exe on one of the drivers but won't work - was advised on some forms as a fix on one of the drivers I was trying to debug.
(f) I got a message that a file "NIwin..something" caused a crash so I disabled its service - it is a Native Instruments virtual drive left over file (as far as I can tell) --- this file was not on the system when the first BSODs started.
* ntoskrnl.exe sometimes shows as the cause for the crash.
** The system does seem to be a bit better after these fixes but still getting totally random crashes. The system can be left idol doing nothing and will crash randomly.
*** Driver verifier crashes the system really badly when you set it from safe mode and boot as normal - usually 2 cashes on start up before needing to do a system restore. The same problem does not seem to always happen when verifier is set in normal boot mode.
-----------------------------------------------------------------------------------------------------
-----------------------------------
WHOCRASHED ANALYSIS
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: P17SM , Notebook
CPU: GenuineIntel Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 34272923648 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 05/04/2015 02:43:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040515-5796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0x2, 0x2, 0x0, 0xFFFFF80273115C45)
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 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 Sun 05/04/2015 02:43:03 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP!ClassCompleteRequest+0x446)
Bugcheck code: 0xA (0x2, 0x2, 0x0, 0xFFFFF80273115C45)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 standard 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 Sun 05/04/2015 01:34:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040515-5203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8021476CDCF, 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 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 Sun 05/04/2015 00:41:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040515-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x139 (0x3, 0xFFFFF80340FAD540, 0xFFFFF80340FAD498, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
-------------------------------------------------------------------------------------
* End of WHOCRASHESD.
-------------------------------------------------------------------------------------
Does anyone have any lead or advice on what try or try again even, or do you think a technician would be able to solve this? I am thinking to try a system repair, but the thought of the time lost on a full clean install is harrowing. My system is fully backed up so I can thinker away.
Anyway, any help, thoughts, leads or advice will be hugely appreciated.
Thanks and respect.
. I was advised it was likely that Windows had "gone weird" and to re-install windows. The problem seemed to be gone for a while but is back and causing real headaches. I have been trying to debug the problems and have searched all over the internet for solutions and need some tech help. (Hoping its not a hardware issues that came with it new). Sometimes I can go for hours of heavy processing with out any issues and other times I just turn it on, leave it sitting on the table and anything from 5 minutes to 2 hours and the system randomly crashes while sitting idol. ---- the real kicker is my old work laptop that was on XP was upgraded to SSD and win 7 never crashes but doesn't have the spec I need.Systems Specs:
OS: Windows 8.1 pro
Processor: Intel Core I7 -4800MQ CPU 2.70GHz
RAM: 32 GB
Graphics: AMD Radeon HD 8970M
--------------------------------------------------------------------------------------------------
Here is what I have tried and done:
(a) Used Who crashed and driver verifier to find out what's causing BSOD:
AMD drivers fixed - complete uninstall, updated Intel drivers, reinstalled AMD - this defiantly solved some issues , but new issues started showing.
Removed PQLabs Mutitouch driver,
Removed display link core usb driver,
Removed Yamaha (stienberg) fire-wire driver.
(b) carried out sfc/scannow command x3 times - results clear,
(c) carried out disk check - results clear,
(d) anti virus and malware scans - results clear,
(e) tried expand.exe on one of the drivers but won't work - was advised on some forms as a fix on one of the drivers I was trying to debug.
(f) I got a message that a file "NIwin..something" caused a crash so I disabled its service - it is a Native Instruments virtual drive left over file (as far as I can tell) --- this file was not on the system when the first BSODs started.
* ntoskrnl.exe sometimes shows as the cause for the crash.
** The system does seem to be a bit better after these fixes but still getting totally random crashes. The system can be left idol doing nothing and will crash randomly.
*** Driver verifier crashes the system really badly when you set it from safe mode and boot as normal - usually 2 cashes on start up before needing to do a system restore. The same problem does not seem to always happen when verifier is set in normal boot mode.
-----------------------------------------------------------------------------------------------------
-----------------------------------
WHOCRASHED ANALYSIS
System Information (local)
--------------------------------------------------------------------------------
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: P17SM , Notebook
CPU: GenuineIntel Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 34272923648 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 05/04/2015 02:43:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040515-5796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0x2, 0x2, 0x0, 0xFFFFF80273115C45)
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 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 Sun 05/04/2015 02:43:03 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP!ClassCompleteRequest+0x446)
Bugcheck code: 0xA (0x2, 0x2, 0x0, 0xFFFFF80273115C45)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 standard 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 Sun 05/04/2015 01:34:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040515-5203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8021476CDCF, 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 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 Sun 05/04/2015 00:41:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040515-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x139 (0x3, 0xFFFFF80340FAD540, 0xFFFFF80340FAD498, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
-------------------------------------------------------------------------------------
* End of WHOCRASHESD.
-------------------------------------------------------------------------------------
Does anyone have any lead or advice on what try or try again even, or do you think a technician would be able to solve this? I am thinking to try a system repair, but the thought of the time lost on a full clean install is harrowing. My system is fully backed up so I can thinker away.
Anyway, any help, thoughts, leads or advice will be hugely appreciated.
Thanks and respect.
Facebook
Twitter
Instagram