BSOD error 0x3B

[sparky17]

Hi,

Having lots of issues with BSOD errors. Have tried a number of fixes but can't find anything that works. I'm hoping that the very nice people here might be able to help.

I'm also pretty PC illiterate so please don't hold that against me.

I've posted what info I have but let me know if there is anything else I can add that will help with diagnosis.

Many thanks

System details

computer name: MARK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., P8B75-M LX
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8526385152 total

Crash Dump Analysis from WhoCrahsed v5.03

On Fri 24/07/2015 17:49:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072415-17347-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034857C5, 0xFFFFF8800999FC10, 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 Fri 24/07/2015 17:49:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x789DB)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034857C5, 0xFFFFF8800999FC10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 that cannot be identified at this time.

 

[sparky17]

Hi,

Would be grateful for any help you can manage - about to throw my PC out the window.....

Thanks in advance

 

[Boozad]

Hi mate, sorry for the wait.

There's only one dump in your logs (please don't use CCleaner while we're troubleshooting as it will erase all of your dump files) which is a 0x3B. As there are no drivers showing in the stack can you test your RAM using the guide below. Read carefully and follow the steps to the letter for the optimum results.

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

[COLOR=Blue]SYSTEM_SERVICE_EXCEPTION (3b)[/COLOR]
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800034857c5, Address of the instruction which caused the bugcheck
Arg3: fffff8800999fc10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------
[COLOR=Red]EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s[/COLOR]

 

[sparky17]

Many thanks for coming back. I've started running the test and it is showing up with some errors.

I'll continue to run as per your link to try to ascertain if it is a RAM or Motherboard issue.

Thanks again for your help with this.

 

[Boozad]

You're welcome. Hopefully it's RAM and not the motherboard, keep us posted.

 

[sparky17]

After running checks, the tests seem to indicate that it is just one stick of RAM that has failed.

PC seems to be running fine on just one stick this morning, will keep monitoring and report back.

Thanks again for the diagnosis.

 

[Boozad]

You're welcome, glad to hear it looks like you've found the culprit.