Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD

13 Aug 2010   #1

windows 7 x64

randomly getting BSOD when playing games or closing a program, some help would be appreciated.

Crash dumps...

My System SpecsSystem Spec
13 Aug 2010   #2

Windows 10 Pro x64

The bulk of these are problems with the kernel attempting to read from memory addresses that are invalid - and by that, I mean corrupted PTEs, page faults when running in nonpaged pool, etc. This would indicate you might have bad RAM, so checking your RAM at this point is a very wise idea.
My System SpecsSystem Spec
13 Aug 2010   #3

Microsoft Window 7 Professional 32 bit

Quote   Quote: Originally Posted by Ash119 View Post
randomly getting BSOD when playing games or closing a program, some help would be appreciated.

Crash dumps...

Hi and Welcome to SF!

Cluberti is right, memory corruption was mentioned in the DMP so please check your RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

In addition to RAM, I suspect your graphic card as well because dxgmms1.sys was blamed in the DMP with stop code 7E, which can be graphic card issue. I would suggest you to re-install the graphic card driver first. When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

When re-install graphic card driver, update directx as well:
Download details: DirectX End-User Runtime

BugCheck 1A, {411, fffff680000356e8, a7c85884, fffff680000156e9}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6051 )

Followup: MachineOwner

BugCheck A, {28, 2, 0, fffff80002b03518}

Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )

Followup: MachineOwner
BugCheck 1000007E, {ffffffffc0000005, fffff88004431d0c, fffff88002130868, fffff880021300d0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+94 )

Followup: MachineOwner
Run system file check please:
SFC /SCANNOW Command - System File Checker

as well as Malware check:


My System SpecsSystem Spec

14 Aug 2010   #4

windows 7 x64

thanks for the quick reply.

memtest - 5passes 0 error

malware check - Trojan.agent

reinstalled gfx drivers.
My System SpecsSystem Spec
15 Aug 2010   #5

windows 7 x64

New blue screen dump
My System SpecsSystem Spec
15 Aug 2010   #6

Microsoft Window 7 Professional 32 bit

I still suspect the graphic card. However, let's turn on driver verifier to know exactly what is causing all of these
Beyond that, please run Verifier with these settings:
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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
BugCheck A, {fffff900c21a600a, c, 1, fffff80002ad8ec1}

Probably caused by : hardware ( win32k!AllocateObject+dd )

Followup: MachineOwner
My System SpecsSystem Spec
15 Aug 2010   #7

Windows 7 Professional x64

Do you have another graphics card you can use? See if a friend has one, or rob one from another computer.
My System SpecsSystem Spec
15 Aug 2010   #8

windows 7 x64

no can do
My System SpecsSystem Spec
15 Aug 2010   #9

windows 7 x64

verifier blue screen

An exception happened while executing a system service routine.
Arg1: 00000000c0000094, Exception code that caused the bugcheck
Arg2: fffff80002db4e43, Address of the instruction which caused the bugcheck
Arg3: fffff88005cda770, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.

fffff800`02db4e43 f7b718060000 div eax,dword ptr [rdi+618h]

CONTEXT: fffff88005cda770 -- (.cxr 0xfffff88005cda770)
rax=00000000197728e6 rbx=0000000000000000 rcx=00000000197728e6
rdx=0000000000000000 rsi=0000000000000011 rdi=fffff8a00039c010
rip=fffff80002db4e43 rsp=fffff88005cdb140 rbp=fffff8a0005f82f3
r8=0000000000000000 r9=000000000000fffe r10=0000000000000000
r11=fffff88005cdb2d8 r12=fffff8a0015474a8 r13=0000000000000001
r14=fffff8a000131130 r15=fffff8a000131130
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffff800`02db4e43 f7b718060000 div eax,dword ptr [rdi+618h] ds:002b:fffff8a0`0039c628=00000000
Resetting default scope



PROCESS_NAME: SearchIndexer.


LAST_CONTROL_TRANSFER: from fffff80002db3d08 to fffff80002db4e43

fffff880`05cdb140 fffff800`02db3d08 : fffff880`05cdb2d8 fffff880`00000005 fffff880`05cdb6c8 fffff880`05cdb6e0 : nt!CmpKcbCacheLookup+0x8d3
fffff880`05cdb230 fffff800`02db1f61 : fffff8a0`01be5510 fffff880`05cdb6e0 fffff880`05cdb718 fffff880`05cdb700 : nt!CmpBuildHashStackAndLookupCache+0x328
fffff880`05cdb610 fffff800`02dd1e84 : fffff800`02db1cc0 00000000`00000000 fffffa80`06064b10 00000000`00000001 : nt!CmpParseKey+0x2a1
fffff880`05cdb8e0 fffff800`02dd6e4d : fffffa80`06064b10 fffff880`05cdba40 00000000`00000040 fffffa80`03d19a50 : nt!ObpLookupObjectName+0x585
fffff880`05cdb9e0 fffff800`02db5dcc : 00000000`02046000 00000000`00000000 fffff8a0`01be5501 fffff880`05cdbaa8 : nt!ObOpenObjectByName+0x1cd
fffff880`05cdba90 fffff800`02db7f0f : 00000000`0137df10 00000000`0002001f 00000000`0137df98 00000000`00000000 : nt!CmOpenKey+0x28a
fffff880`05cdbbe0 fffff800`02ad7993 : fffffa80`0720e490 fffff880`05cdbca0 00000000`ff420cd0 fffffa80`072a2240 : nt!NtOpenKeyEx+0xf
fffff880`05cdbc20 00000000`77b10caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0137dea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b10caa

fffff800`02db4e43 f7b718060000 div eax,dword ptr [rdi+618h]


SYMBOL_NAME: nt!CmpKcbCacheLookup+8d3



IMAGE_NAME: ntkrnlmp.exe


STACK_COMMAND: .cxr 0xfffff88005cda770 ; kb

FAILURE_BUCKET_ID: X64_0x3B_VRF_nt!CmpKcbCacheLookup+8d3

BUCKET_ID: X64_0x3B_VRF_nt!CmpKcbCacheLookup+8d3

Followup: MachineOwner
My System SpecsSystem Spec
15 Aug 2010   #10

Windows 7 Professional x64

Update your SATA drivers: ASUSTeK Computer Inc.-Support-

Time to test hardware. First comes RAM.
Quote   Quote: Originally Posted by JK
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 6 passes.
Next hard drive: HD Diagnostic

Let us know the results, and we may do some more tests.

If the BSODs persist, please use these directions to post them:

...Summary of the Dumps:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 15 13:33:20.201 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:13.027
BugCheck 3B, {c0000094, fffff80002db4e43, fffff88005cda770, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+8d3 )
PROCESS_NAME:  SearchIndexer.
My System SpecsSystem Spec


Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 20:46.
Twitter Facebook Google+