Persistent BSODs 3b code

Hello all,

I've been getting these BSODs for over a year now and can't seem to find the problem. I've tried updating all the drivers and ran memtest which showed no errors and driver verifier which increased the frequency of BSODs but I don't know where to go from here.

Any help would be most appreciated.

Here is my system information:

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ALFA1-PC
System Manufacturer Packard Bell
System Model ixtreme M3720
System Type x64-based PC
Processor Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz, 2500 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date AMI P01-A3, 21/07/2009
SMBIOS Version 2.5
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name ALFA1-PC\ALFA1
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.75 GB
Available Physical Memory 2.28 GB
Total Virtual Memory 7.50 GB
Available Virtual Memory 5.98 GB
Page File Space 3.75 GB
Page File C:\pagefile.sys

Hello croc,

*1. Symantec is a frequent cause of BSOD's.
Please remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows


*2. Your crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Hi JMH,

Many thanks for your response, most appreciated. I've now removed Norton and installed MSE, I ran Memtest overnight through 16 passes which found no errors. I've just enabled driver verifier this morning and will post back with any crashes later.

Thanks again for your help.

You are welcome.

Hi again,

Just had my first crash with driver verifier enabled. I have turned off verifier now and uploaded the dump files. Or would it be best to leave verifier on for a while?

Thanks in advance for your help.

Using Driver Verifier is an iffy proposition.
Most times it'll crash and will tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
{ This happened in your case.}

Keep running Verifier again as per instructions earlier.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Hi,

I enabled verifier again yesterday morning and have since had 4 blue screens I think. I've uploaded the dump files. Hopefully, these will show the culprit.

Thanks in advance for any help.

croc83 said:

Hi,

I enabled verifier again yesterday morning and have since had 4 blue screens I think. I've uploaded the dump files. Hopefully, these will show the culprit.

Thanks in advance for any help.

Most recent three crashes show no consistent cause. You may not be verififying all the drivers on the machine. Lets try this for a bit.

Hi, its been a while since I've posted but I'm still having problems. I'm trying the above suggestion now but it makes everything run very slowly but I'm hoping to produce some BSODs to upload with verifier enabled to verify all drivers.

Heres what I have done so far:

removed Norton
ran Memtest86 for 16 passes - no errors
ran chkdsk /r/f - no errors
ran sfc scannow
updated all drivers - I think!

If you're around zigzag or JMH or anyone please take a look at the dumps attached. As soon as I get a BSOD with verifier enabled I will post.

Problematic software:

Code:

Start Menu\Programs\SlimDrivers	Public:Start Menu\Programs\SlimDrivers	Public
Start Menu\Programs\Uniblue	Public:Start Menu\Programs\Uniblue	Public

We do not recommend automated driver update software. It often finds drivers for devices similar to but not exactly the same as the hardware actually on the system. This can lead to conflicts and blue screen crashes. If you need help finding driver updates for a certain device, please start a thread in Drivers - Windows 7 Forums instead of using software. Driver updates are not always necessary and some updates can actually decrease system stability rather than increase it, so it is usually better not to update unless a device or its driver is causing problems with the system. If it ain't broke, don't fix it.

What software do you have installed from Uniblue?

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\croc83\Windows_NT6_BSOD_jcgriff2\042912-36223-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e4f650
Debug session time: Sun Apr 29 10:07:15.507 2012 (UTC - 6:00)
System Uptime: 0 days 0:31:33.536
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f53b5e, fffff88003c8b6e0, 0}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002f53b5e, Address of the instruction which caused the bugcheck
Arg3: fffff88003c8b6e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!CmpKcbCacheLookup+1de
fffff800`02f53b5e 418b45f4        mov     eax,dword ptr [r13-0Ch]

CONTEXT:  fffff88003c8b6e0 -- (.cxr 0xfffff88003c8b6e0)
rax=fffff8a00005a000 rbx=0000000000000000 rcx=0000000000000489
rdx=0000000011099e5e rsi=fffff88003c8c2a0 rdi=0000000064139db8
rip=fffff80002f53b5e rsp=fffff88003c8c0c0 rbp=fffff8a000020410
 r8=0000000000000006  r9=0000000000000000 r10=0000000000000008
r11=fffff88003c8c270 r12=fffff8a000020a08 r13=0000000000000010
r14=0000000000000002 r15=0000000000000002
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!CmpKcbCacheLookup+0x1de:
fffff800`02f53b5e 418b45f4        mov     eax,dword ptr [r13-0Ch] ds:002b:00000000`00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x3B

PROCESS_NAME:  wininit.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f53b5e

STACK_TEXT:  
fffff880`03c8c0c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x1de


FOLLOWUP_IP: 
nt!CmpKcbCacheLookup+1de
fffff800`02f53b5e 418b45f4        mov     eax,dword ptr [r13-0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpKcbCacheLookup+1de

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

STACK_COMMAND:  .cxr 0xfffff88003c8b6e0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_nt!CmpKcbCacheLookup+1de

BUCKET_ID:  X64_0x3B_VRF_nt!CmpKcbCacheLookup+1de

Followup: MachineOwner
---------

The above crash was rather inconclusive, but it may implicate your graphics card or its drivers. Download the latest drivers for your display card from Drivers - GeForce

• Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
  
  
  1. Download the drivers you want for your display card(s)
  2. Click Start Menu
  3. Click Control Panel
  4. Click Uninstall a program
  5. For NVIDIA:
     • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
     • Restart your computer
     • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
     • If any remain of the above, uninstall one at a time
     • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
  6. For AMD:
     • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
     • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
       1. Click Start Menu
       2. Right Click My Computer/Computer
       3. Click Manage
       4. Click Device Manager from the list on the left
       5. Expand Display adapters
       6. Do the following for each adapter (in case you have multiple display cards)
          
          • Right click the adapter
          • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
          • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
          
          
          Alternatively:
          
          1. Login as an adminstrative user
          2. Click Start Menu
          3. Click Control Panel
          4. Click Hardware and Sound
          5. Click Device Manager (the last link under Devices and Printers)
          6. Expand Display adapters
          7. Do the following for each adapter (in case you have multiple display cards)
             
             • Right click the adapter
             • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
             • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
     • Restart your computer after uninstalling drivers for all display cards
     • Install the driver you selected for the display cards once Windows starts