New
#1
BSOD "Custom Error"
Firstly, Windows says this:
Analysed the dump file(s) with WhoCrashed, report below:Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057
Additional information about the problem:
BCCode: 1000009f
BCP1: 0000000000000004
BCP2: 0000000000000258
BCP3: FFFFFA8005507B60
BCP4: FFFFF80000B9C510
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\032311-13587-01.dmp
C:\Users\Administrator\AppData\Local\Temp\WER-50637-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Not too worried about the DX error, but the others are annoying (and have also never happened whilst I've been physically at my laptop), and started relatively recently. I haven't updated/added/changed any drivers since before the first crash.On Wed 23/03/2011 19:13:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032311-13587-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x765DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8005507B60, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 23/03/2011 19:13:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA8005507B60, 0xFFFFF80000B9C510)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.
On Sun 20/03/2011 19:54:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032011-15038-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x765DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8005506040, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 19/03/2011 16:53:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031911-13400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x765DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8005507680, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 14/01/2011 20:52:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011411-19812-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA189C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004F4389C, 0xFFFFF88003C11790, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
I've run SFC since then, if it will have an effect I do not know. I have the log file created by it, it apparently found and fixed several errors.
Thanks,
Jake
Last edited by jakeythesnake; 24 Mar 2011 at 12:56.
Quote
