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 again...............

21 May 2011   #1
edeyejedi

Windows 7 Pro x64
 
 
BSOD again...............

Ive attached the .dmp file and would greatly appreciate it if some one could tell what is going on. I tried to open it with windows debugging tools but Im afraid I failed. So if there is a cruisader out there who has more of an idea than I do then please let me know what is wrong with my machine.

Cheers


My System SpecsSystem Spec
.
21 May 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by edeyejedi View Post
Ive attached the .dmp file and would greatly appreciate it if some one could tell what is going on. I tried to open it with windows debugging tools but Im afraid I failed. So if there is a cruisader out there who has more of an idea than I do then please let me know what is wrong with my machine.

Cheers
Memory corruption caused by your ccc. I would:

Re-install your video driver (just the driver not ccc) using this

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

Or Phyxion.net - Driver Sweeper

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




AND


Run memtest to check your memory.

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

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.


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Dump.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Fri May 21 00:56:32.254 2010 (GMT-4)
System Uptime: 0 days 6:24:05.767
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff9600022cace, fffff880054541b0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

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

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
win32k!NtGdiDdDDIOpenAdapterFromHdc+e2
fffff960`0022cace c7              ???

CONTEXT:  fffff880054541b0 -- (.cxr 0xfffff880054541b0)
rax=fffff900c2965010 rbx=fffff900c00bf010 rcx=fffff9600034cc40
rdx=fffffa8004579810 rsi=00000000c000000d rdi=0000000000000000
rip=fffff9600022cace rsp=fffff88005454b80 rbp=fffff88005454ca0
 r8=000000000000000b  r9=fffff9600034cc40 r10=0000000000000000
r11=fffff900c2102010 r12=000000001b34da20 r13=0000000000000010
r14=000000001c0d3ea0 r15=000000000116cbb0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!NtGdiDdDDIOpenAdapterFromHdc+0xe2:
fffff960`0022cace c7              ???
Resetting default scope

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002abd993 to fffff9600022cace

STACK_TEXT:  
fffff880`05454b80 fffff800`02abd993 : fffffa80`0234bb60 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!NtGdiDdDDIOpenAdapterFromHdc+0xe2
fffff880`05454c20 000007fe`fd8283fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1b34d9e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd8283fa


CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
8 errors : !win32k (fffff9600022cac5-fffff9600022cafd)
fffff9600022cac0  63  38  11  72  5b *00  8b  83  c8  09  00  00  48 *f8  c7  74 c8.r[.......H..t
fffff9600022cad0  0e  8b  80  a8  00 *f8  00  c1  e8  17  83  e0  01 *f8  02  8b ................
fffff9600022cae0  c7  3b  c7  74  3b *00  8b  93  c8  09  00  00  8b *00  10  01 .;.t;...........
fffff9600022caf0  00  00  89  84  24 *f8  00  00  00  48  8d  4c  24 *fa  ff  15 ....$....H.L$...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff880054541b0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
My System SpecsSystem Spec
25 Jun 2011   #3
edeyejedi

Windows 7 Pro x64
 
 

Thanks for your reply on the last one. Finaly got round to sorting the graphics drivers out. was all good, but had a couple of BSOD's in the last few days.

If some one could check this dmp to see the prob, hopefully graphics drivers arnt coming up then i know its MB or RAM.

I really need to learn how to look at thee dmp files myself. Bit beyond me at the mo though

cheers!
My System SpecsSystem Spec
.

Reply

 BSOD again...............




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 11:25.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App