Harib0x
Member
- Joined
- Oct 29, 2015
- Messages
- 24
- Thread Author
-
- #1
Hi, since a few weeks, I keep having some BSOD with either Error: SYSTEM_SERVICE_EXCEPTION or Error: IRQL_NOT_LESS_OR_EQUAL.
Here are the descriptions from "Who Crashed":
On Thu 29/10/2015 12:37:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102915-35031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8013152BB45, 0xFFFFD001CCA277E0, 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 Thu 29/10/2015 12:37:17 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: 0x3B (0xC000001D, 0xFFFFF8013152BB45, 0xFFFFD001CCA277E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Sun 25/10/2015 13:31:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102515-62015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801F6AFBBA8, 0xFFFFD00020621590, 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 Sun 25/10/2015 11:39:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102515-40437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8009B65A9C3)
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.
I'm also attaching the dump files of the BSOD.
Thank you for any help you could provide.
Here are the descriptions from "Who Crashed":
On Thu 29/10/2015 12:37:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102915-35031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8013152BB45, 0xFFFFD001CCA277E0, 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 Thu 29/10/2015 12:37:17 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: 0x3B (0xC000001D, 0xFFFFF8013152BB45, 0xFFFFD001CCA277E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Sun 25/10/2015 13:31:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102515-62015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801F6AFBBA8, 0xFFFFD00020621590, 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 Sun 25/10/2015 11:39:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102515-40437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8009B65A9C3)
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.
I'm also attaching the dump files of the BSOD.
Thank you for any help you could provide.
Attachments
Last edited:
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c000001d, fffff8013152bb45, ffffd001cca277e0, 0}
Probably caused by : hardware ( nt!SepNormalAccessCheck+4c5 )
Followup: MachineOwner
all your dump files were similar to the above apart from one which blamed memory corruption. The above Bugcheck can be caused by...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
The 'boot override'? I'm not familiar with this term but basically you need to change the 'Boot order' so that the USB is first.boot override so that it boots the USB drive instead of the OS
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Ok cool.. I'm unsure as to why the USB method won't work for you although other users have said the same thing before now. Sometimes a user will have a problem running from either disk or usb but not both so it's worth trying the disk method.
I take it you've had no bsod's since running the scan? If that's the case I wouldn't bother running memtest86 unless you bsod again.
I take it you've had no bsod's since running the scan? If that's the case I wouldn't bother running memtest86 unless you bsod again.
Yes.For the disk, which memtest do I need to use ?
The "Link Removed
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
We already did..Hmm, just a thought and I don't want to interfere, but with all those bad sectors and hardware related crashes it won't be a bad idea to run seatools and check your disks....
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Yup that's bad memory alright. It's possible the resulting bsod's caused the corruption on the HDD but in any case you'll need to change that RAM. How many sticks are you running?I think that it is a memory problem.
Similar threads
- Article
- Replies
- 0
- Views
- 17
- Replies
- 0
- Views
- 426
- Solved
- Replies
- 21
- Views
- 4K
- Replies
- 1
- Views
- 1K
- Replies
- 4
- Views
- 2K