Re: Blue Screen
Geplaatst: 21 sep 2018 17:11
Gisteren weer een BSOD op de desktop. Was toevallig-niet toevallig? weer net even op Soulseek. Heb nu Soulseek ook in de exclusion list van BullGuard gezet. Misschien bijten MBAM en BG elkaar bij het scannen van Soulseek? Hieronder BSOD Collection en WhoCrashed. Kunnen we een patroon ontdekken? En kan iemand me vertellen waar ikzelf kan kijken bij de BSOD Collection zodat ik weer wat bijleer.
http://www.filedropper.com/sysnativefilecollectionapp_1
==================================================
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: USER-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: p7-1423w, Hewlett-Packard, Foxconn, 2ADA
CPU: GenuineIntel Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8466694144 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 19-9-2018 18:26:43 GMT your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091918-7332-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001AD4EAA, 0xFFFFF880070D3480, 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 Tue 4-9-2018 12:45:57 GMT your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090418-6333-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001AD6EAA, 0xFFFFF88008F94480, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 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.
http://www.filedropper.com/sysnativefilecollectionapp_1
==================================================
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: USER-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: p7-1423w, Hewlett-Packard, Foxconn, 2ADA
CPU: GenuineIntel Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8466694144 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 19-9-2018 18:26:43 GMT your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\091918-7332-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001AD4EAA, 0xFFFFF880070D3480, 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 Tue 4-9-2018 12:45:57 GMT your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090418-6333-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001AD6EAA, 0xFFFFF88008F94480, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 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.