New
#1
win 7x64 random BSOD's
hello all,
My system is 7 x64 home premium oem.
It's new, clean, the first OS installation on complete new hardware
Memtest PASSED 31 rounds.
Please help me to find course to solution..
Thanks, Gad
hello all,
My system is 7 x64 home premium oem.
It's new, clean, the first OS installation on complete new hardware
Memtest PASSED 31 rounds.
Please help me to find course to solution..
Thanks, Gad
Gadgar
In two of these it is still saying memory corruption. I see 31 passes. Did you run one stick at a time, and then one mobo slot as well.
There are a couple of other things that may be causing the memory to become corrupt
For example old drivers. The below ssport driver is a samsung printer driver and is known to cause problems. the rest of the old drivers should also be updated.
How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
Code:SSPORT.sys fffff880`06300000 fffff880`06308000 0x00008000 0x42fbda34 8/11/2005 19:07:32 LVUSBS64.sys fffff880`05ecb000 fffff880`05ed5980 0x0000a980 0x488b3d7c 7/26/2008 11:06:36 LV302V64.SYS fffff880`0267f000 fffff880`028fe180 0x0027f180 0x488b3e14 7/26/2008 11:09:08 spldr.sys fffff880`0191f000 fffff880`01927000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 spsys.sys fffff880`0651e000 fffff880`0658f000 0x00071000 0x4a085e7a 5/11/2009 13:20:58Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\100610-14960-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Mini Kernel Dump does not have process information 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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50 Debug session time: Wed Oct 6 16:25:40.529 2010 (GMT-4) System Uptime: 0 days 0:06:13.996 Loading Kernel Symbols ............................................................... ................................................................ ......................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80002d6922c, 0, ffffffffffffffff} Probably caused by : memory_corruption ( nt!MiApplyCompressedFixups+40 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002d6922c, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception 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!MiApplyCompressedFixups+40 fffff800`02d6922c 0fb603 movzx eax,byte ptr [rbx] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb90e0 ffffffffffffffff CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E CURRENT_IRQL: 0 EXCEPTION_RECORD: fffff8800708bf38 -- (.exr 0xfffff8800708bf38) ExceptionAddress: fffff80002d6922c (nt!MiApplyCompressedFixups+0x0000000000000040) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff8800708bfe0 -- (.trap 0xfffff8800708bfe0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8a0076bf000 rbx=0000000000000000 rcx=fffffa80055e3110 rdx=fffff88002a6f000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002d6922c rsp=fffff8800708c170 rbp=000000000000000a r8=ff7ff8a0076c02f2 r9=ffffffffffc90000 r10=0000000000000fff r11=fffff88002a6f000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!MiApplyCompressedFixups+0x40: fffff800`02d6922c 0fb603 movzx eax,byte ptr [rbx] ds:42b0:00000000`00000000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002abba39 to fffff80002a81740 STACK_TEXT: fffff880`0708b768 fffff800`02abba39 : 00000000`0000001e ffffffff`c0000005 fffff800`02d6922c 00000000`00000000 : nt!KeBugCheckEx fffff880`0708b770 fffff800`02a80d82 : fffff880`0708bf38 ff7ff8a0`076c02f2 fffff880`0708bfe0 ffffffff`ffc90000 : nt!KiDispatchException+0x1b9 fffff880`0708be00 fffff800`02a7f68a : 00000000`00000000 fffffa80`04084340 fffffa80`00000000 00001f80`01013110 : nt!KiExceptionDispatch+0xc2 fffff880`0708bfe0 fffff800`02d6922c : fffff880`0708c178 fffffa80`045624e0 fffffa80`035542b0 ffffffff`ffc90000 : nt!KiGeneralProtectionFault+0x10a fffff880`0708c170 fffff800`02d690b1 : fffff880`02a6f000 ffffffff`ffc90000 00000000`0016d000 fffffa80`010f78e0 : nt!MiApplyCompressedFixups+0x40 fffff880`0708c1c0 fffff800`02d56344 : 00000000`00000000 00000000`00000000 fffff6fc`40015308 fffff800`00000000 : nt!MiPerformFixups+0x65 fffff880`0708c210 fffff800`02a6368d : 00000000`0005a7da 00000000`0000016d fffff8a0`076b4f20 00000000`00000002 : nt!MiRelocateImagePfn+0x114 fffff880`0708c270 fffff800`02d6900d : fffffa80`03789bd0 fffff6fc`40015308 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x2bd fffff880`0708c310 fffff800`02d68720 : ffffffff`ffffffff 00000000`00000001 fffff8a0`076bf000 00000000`000000f3 : nt!MiSwitchBaseAddress+0x61 fffff880`0708c340 fffff800`02d7c7ce : 00000000`00000004 00000000`01000000 00000000`00000000 00000000`00000000 : nt!MiRelocateImageAgain+0x100 fffff880`0708c390 fffff800`02d72013 : fffff880`0708c5f0 00000000`00000000 fffff880`0708c698 fffff880`0708c5e8 : nt!MmCreateSection+0x302 fffff880`0708c5a0 fffff800`02edea23 : 00000000`00000000 fffff8a0`07602250 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x162 fffff880`0708c620 fffff800`02edefb1 : 00000000`00000000 fffff8a0`07602250 fffffa80`0549b110 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163 fffff880`0708c710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PfpPrefetchFilesTrickle+0x121 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiApplyCompressedFixups+40 fffff800`02d6922c 0fb603 movzx eax,byte ptr [rbx] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!MiApplyCompressedFixups+40 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x1E_nt!MiApplyCompressedFixups+40 BUCKET_ID: X64_0x1E_nt!MiApplyCompressedFixups+40 Followup: MachineOwner ---------
Last edited by zigzag3143; 26 Jan 2011 at 03:54.
After installed fresh x32 7
The BSOD`s follows up
The memory modouls separetlly scanned
Here are the additional BSOD`s.
Thanks
Is there ANY lead about the problem from the new BSODs?
I'm so confused...
Thanks, Gad