BSOD error after hdd partition

[quartaela]

hi there. i decided to partition my hdd to install ubuntu, and i can't managed it from windows own disk management tool cause it doesn't allow me to shrink enough space for create another one. so i used "Acronis*Disk Director Suite" and created one 100gbyte primary volume with EXT3 file format. after i restart my computer i get first BSOD and today when i opened windows i get an another one. i made the instructions except i can't managed save the performance report as .html format so take a screenshot of it. this is all about i can say. also i include the system configurations as a screeshot. and thanks for your help. : )

 

[richc46]

All of your reports show memory corrupiton.


Take memtest86
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Run for 8 passes
If passes try a good stick in each slot for 3 passes
If fails do the same for 8 passes.

 

[quartaela]

well i tried this memtest nearly 2 month ago for another BSOD errors and it showed lots of errors in that test. but i have intel sandy bridge processor and i used the latest memtest version which is beta and not fully compatible with sandy bridge. so i know i will have lots of memtest errors again : ). what shoud i do_? and thanks for your help richc46

 

[richc46]

I only have the report to go by and it shows memory problems. Sandy bridge or not, it appers that you have to get the memory repaired. What I would do is remove the ram sticks and test in another computer. If the sticks are OK, I would guess its your MB.
I can tell you this too, the reports that you gave me usually only give conflicting clues, you had 3 and they all say memory.

 

[quartaela]

well ok : ). but when i faced with BSOD errors 2 months ago i contacted with my technical service and he said that memtest doesn't give true information always, so he gave an advice about using windows recognizing tool for memory. the problem is how i can convince him about i have corrupted memories.

 

[richc46]

He could still be right, about not having a memory problem, until proven wrong. I differ from him in that I think if done properly and given the right amount of time Memtest is accurate. You need to run it for at least 8 passes and then check each MB slot, for at least four passes.

 

[richc46]

Just had a thought, show him this. Tell him three BSODs and all reference memory

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temporary Internet Files\Content.IE5\SWLNFIOJ\BSOD\Windows_NT6_BSOD_jcgriff2\032011-14648-01.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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03259e50
Debug session time: Sun Mar 20 06:44:27.471 2011 (GMT-4)
System Uptime: 0 days 0:01:05.798
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff88010b8b582, fffff8800699d320, 0}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[B]Probably caused by : memory_corruption[/B]
[B]Followup: memory_corruption[/B]
---------
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: fffff88010b8b582, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800699d320, 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: 
dxgkrnl!DXGK_VIDPNTARGETMODESET_INTERFACE_V1_IMPL::ReleaseModeInfo+52
fffff880`10b8b582 ff1531f2f5ff    call    qword ptr [dxgkrnl!_imp_WdLogEvent5+0x1 (fffff880`10aea7b9)]
CONTEXT:  fffff8800699d320 -- (.cxr 0xfffff8800699d320)
rax=fffffa8004e3ad40 rbx=fffff8a001edaf60 rcx=0000000000000005
rdx=fffffa8004e3ad40 rsi=fffff8a001f2bc60 rdi=fffff8a001f2bc60
rip=fffff88010b8b582 rsp=fffff8800699dd00 rbp=0000000000000002
 r8=0000000000012bf5  r9=000000000000000f r10=0000000000000000
r11=fffff8800185e120 r12=fffffa8004ea1000 r13=fffff8a001634bf0
r14=fffff8a0089914f0 r15=fffffa80054fa000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
dxgkrnl!DXGK_VIDPNTARGETMODESET_INTERFACE_V1_IMPL::ReleaseModeInfo+0x52:
fffff880`10b8b582 ff1531f2f5ff    call    qword ptr [dxgkrnl!_imp_WdLogEvent5+0x1 (fffff880`10aea7b9)] ds:002b:fffff880`10aea7b9=2200000000000efe
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff8800ffebe62 to fffff88010b8b582
STACK_TEXT:  
fffff880`0699dd00 fffff880`0ffebe62 : fffff880`000004e5 fffff880`0699e2f0 fffff880`0699de70 fffff880`0699de70 : dxgkrnl!DXGK_VIDPNTARGETMODESET_INTERFACE_V1_IMPL::ReleaseModeInfo+0x52
fffff880`0699dd30 fffff880`000004e5 : fffff880`0699e2f0 fffff880`0699de70 fffff880`0699de70 fffff880`0699dd60 : nvlddmkm+0x175e62
fffff880`0699dd38 fffff880`0699e2f0 : fffff880`0699de70 fffff880`0699de70 fffff880`0699dd60 00000000`000007ff : 0xfffff880`000004e5
fffff880`0699dd40 fffff880`0699de70 : fffff880`0699de70 fffff880`0699dd60 00000000`000007ff fffff8a0`08983ee0 : 0xfffff880`0699e2f0
fffff880`0699dd48 fffff880`0699de70 : fffff880`0699dd60 00000000`000007ff fffff8a0`08983ee0 00000000`00001b7c : 0xfffff880`0699de70
fffff880`0699dd50 fffff880`0699dd60 : 00000000`000007ff fffff8a0`08983ee0 00000000`00001b7c fffff880`0699e1d4 : 0xfffff880`0699de70
fffff880`0699dd58 00000000`000007ff : fffff8a0`08983ee0 00000000`00001b7c fffff880`0699e1d4 00000000`00000000 : 0xfffff880`0699dd60
fffff880`0699dd60 fffff8a0`08983ee0 : 00000000`00001b7c fffff880`0699e1d4 00000000`00000000 fffff8a0`01634bf0 : 0x7ff
fffff880`0699dd68 00000000`00001b7c : fffff880`0699e1d4 00000000`00000000 fffff8a0`01634bf0 fffff880`0699e620 : 0xfffff8a0`08983ee0
fffff880`0699dd70 fffff880`0699e1d4 : 00000000`00000000 fffff8a0`01634bf0 fffff880`0699e620 fffff880`0699e2e0 : 0x1b7c
fffff880`0699dd78 00000000`00000000 : fffff8a0`01634bf0 fffff880`0699e620 fffff880`0699e2e0 fffff880`0ffebf24 : 0xfffff880`0699e1d4
 
CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgkrnl
    fffff88010b8b584 - dxgkrnl!DXGK_VIDPNTARGETMODESET_INTERFACE_V1_IMPL::ReleaseModeInfo+54
 [ 30:31 ]
1 error : !dxgkrnl (fffff88010b8b584)
MODULE_NAME: memory_corruption
IMAGE_NAME:  memory_corruption
FOLLOWUP_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
MEMORY_CORRUPTOR:  ONE_BIT
STACK_COMMAND:  .cxr 0xfffff8800699d320 ; kb
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------

 

[quartaela]

ok then i will try again all steps of the test again and if i face with any problems i will contact with technical service and show this thread. so thanks for your help : )

 

[richc46]

Your welcome,
Dont forget, you had 3 BSODs and all pointed to memory. Although not a guanrantee, memory cannot be ignored.