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: In big need of BSOD minidump help!

24 Oct 2010   #1

Windows 7 Ultimate x64
 
 
In big need of BSOD minidump help!

My old computer got its mobo fried a couple of months ago.
I pretty much just bought a new and plugged in all the old parts in the new mobo.

Everything worked fine enough, except that I couldnt plug in all of my ddr2 mem
my new mobo only supported 2 slots of ddr2 and 4 ddr3 slots. To make a long story shorter it all ended with me buying new ddr3 mem new cpu and mobo(again)

Plugged it in, but everything was quite unstable, i had a lot of BSODs all the time, could pretty much only use the computer for up til 5 mins.
Dont think i had it even one time with the old system. I realized i needed to fix the registry or make a new windows install. It ended with a format and a new windows installation , thought everything was fine. I had no BSOD later that day, but one strange thing occured: when i tried to wake my system from hibernation/sleep mode, i noticed that it started running like normal, but my screen was black, it didnt get any signal.


Nothing helped with that, so ive just turned off hibernation/sleep mode.
One of the times it happened it actually helped to change the cable from the 1st dvi to the second dvi contact, only one time though and i think thats the only time anything have helped.


through all this when installing windows and programs afterwards, installing and updating would fail. First the windows install itself, had to retry 4 times, the 3 first said corrupt data in the install file(not on the cd, but on the harddrive), fourth time it worked. Win update afterwards was really problematic, think i had to reinstall several times with most updates especially the newer ones.

This has occured during several other program installations.


Mozilla crashes whenever u start using it "more than little"

Mostly my system crashes whenever its "busy", hdd, mem and cpu working for more than 50 %


i know there is a firmware update for my system drive but i havent dared to try and install it(when i tried bootablecd with memtest86 it hanged) and that would probably fry my disc.


I need help bad! Trying a lot of things, but idont seem to get anywhere.



my system is



AMD Phenom II X6 1090T

ASUS M4A89GTD PRO

(Corsair XMS3 DDR3 1333MHz 4GB CL9 2x2GB ) X2

ATI Radeon HD4850 not sure about manufacturer, just havent looked it up

Samsung W2443

ST31000333AS (SEAGATE) system disc(only half a year old with win 7 x64 ultimate)

MAXTOR 7Y250M0
WDC WD10EADS-00P8B0 (2,5 year old system disc with vista oem on)

MIST 550 W

My System SpecsSystem Spec
.

24 Oct 2010   #2

Windows 7 Ultimate 32 bit
 
 

Welcome to the forum. Sorry to hear you are having problems. You have quite a few dumps. I looked at your four dumps from today. They all indicate hardware/hardware related problems, particularly memory issues.

Are you sure that your RAM is compatible with your motherboard? Have you checked that on your motherboard's website?

Two of the dumps indicate possible hard drive problems as well as memory corruption.
Quote:
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Error code 24 (2X), NTFS_FILE_SYSTEM. Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel
Code:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e49e50
Debug session time: Sun Oct 24 11:57:16.212 2010 (GMT-4)
System Uptime: 0 days 0:47:09.148
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff901c2fcd05d, 0, fffff960000f5e1f, 5}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!draw_clrt_nf_ntb_o_to_temp_start+7b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff901c2fcd05d, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000f5e1f, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb40e0
 fffff901c2fcd05d 

FAULTING_IP: 
win32k!draw_clrt_nf_ntb_o_to_temp_start+7b
fffff960`000f5e1f 41803b00        cmp     byte ptr [r11],0

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880098f8350 -- (.trap 0xfffff880098f8350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000095 rbx=0000000000000000 rcx=00000000ffffff64
rdx=0000000000000015 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000f5e1f rsp=fffff880098f84e8 rbp=0000000000000007
 r8=fffff900c22368d0  r9=fffff900c2fcd0cc r10=fffff960000f5da4
r11=fffff901c2fcd05d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
win32k!draw_clrt_nf_ntb_o_to_temp_start+0x7b:
fffff960`000f5e1f 41803b00        cmp     byte ptr [r11],0 ds:8190:fffff901`c2fcd05d=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cfb8c1 to fffff80002c7c740

STACK_TEXT:  
fffff880`098f81e8 fffff800`02cfb8c1 : 00000000`00000050 fffff901`c2fcd05d 00000000`00000000 fffff880`098f8350 : nt!KeBugCheckEx
fffff880`098f81f0 fffff800`02c7a82e : 00000000`00000000 fffff900`c0148394 fffff8a0`034d6c00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`098f8350 fffff960`000f5e1f : fffff900`c289a000 00000000`0000009c 00000000`00000090 00000000`00000015 : nt!KiPageFault+0x16e
fffff880`098f84e8 fffff960`0012aa58 : fffff900`c00bf010 fffff880`098f8ec0 fffff900`c2fcd0cc 00000000`00000090 : win32k!draw_clrt_nf_ntb_o_to_temp_start+0x7b
fffff880`098f8520 fffff960`00104e68 : 00000000`00000000 fffff900`c2fcd030 fffff900`c01482f0 00000000`00000090 : win32k!vExpandAndCopyText+0x268
fffff880`098f88b0 fffff960`00103a49 : fffff900`00000015 fffff880`00000028 fffff900`c1c48010 fffff880`098f8e00 : win32k!EngTextOut+0xe28
fffff880`098f8c40 fffff960`002d3682 : fffff900`c2921738 fffff880`00000093 fffff880`0000000c 00000000`01011513 : win32k!GreExtTextOutWLocked+0x1d29
fffff880`098f9060 fffff960`0014cecf : 00000000`757b6e30 fffff960`0014af80 fffff880`00000000 fffff900`00ffffff : win32k!GreBatchTextOut+0x26a
fffff880`098f9100 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!NtGdiFlushUserBatch+0x377


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!draw_clrt_nf_ntb_o_to_temp_start+7b
fffff960`000f5e1f 41803b00        cmp     byte ptr [r11],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!draw_clrt_nf_ntb_o_to_temp_start+7b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7dc13c

FAILURE_BUCKET_ID:  X64_0x50_win32k!draw_clrt_nf_ntb_o_to_temp_start+7b

BUCKET_ID:  X64_0x50_win32k!draw_clrt_nf_ntb_o_to_temp_start+7b

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

Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e47e50
Debug session time: Sun Oct 24 08:22:59.958 2010 (GMT-4)
System Uptime: 0 days 0:47:45.893
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800988ee78, fffff8800988e6e0, fffff80002f8c19b}

Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800988ee78
Arg3: fffff8800988e6e0
Arg4: fffff80002f8c19b

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


EXCEPTION_RECORD:  fffff8800988ee78 -- (.exr 0xfffff8800988ee78)
ExceptionAddress: fffff80002f8c19b (nt!CcPinRead+0x000000000000005f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000028
Attempt to read from address 0000000000000028

CONTEXT:  fffff8800988e6e0 -- (.cxr 0xfffff8800988e6e0)
rax=fffffa8006c83b60 rbx=fffff8a00db91c70 rcx=0000000000000000
rdx=fffff8800988f1b0 rsi=fffffa80087195e0 rdi=fffffa80087195e0
rip=fffff80002f8c19b rsp=fffff8800988f0b0 rbp=fffff8800988f820
 r8=0000000000000ffa  r9=0000000000000001 r10=0000000000000ffa
r11=fffff8800988f158 r12=0000000000000ffa r13=0000000000000000
r14=fffff8800988f1b0 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!CcPinRead+0x5f:
fffff800`02f8c19b 488b4128        mov     rax,qword ptr [rcx+28h] ds:002b:00000000`00000028=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  avgchsva.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000028

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb20e0
 0000000000000028 

FOLLOWUP_IP: 
Ntfs! ?? ::FNODOBFM::`string'+2cc9
fffff880`0126f3d8 cc              int     3

FAULTING_IP: 
nt!CcPinRead+5f
fffff800`02f8c19b 488b4128        mov     rax,qword ptr [rcx+28h]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f8c19b

STACK_TEXT:  
fffff880`0988de78 fffff880`0126f3d8 : 00000000`00000024 00000000`001904fb fffff880`0988ee78 fffff880`0988e6e0 : nt!KeBugCheckEx
fffff880`0988de80 fffff880`01267951 : fffff880`0129b1b4 fffff880`0988f820 fffff880`0988f7f0 fffff880`01290010 : Ntfs! ?? ::FNODOBFM::`string'+0x2cc9
fffff880`0988dec0 fffff800`02ca8d1c : 00000000`00680000 00000000`00000000 00000000`00017551 ffffffff`c0000102 : Ntfs! ?? ::FNODOBFM::`string'+0x1446
fffff880`0988df00 fffff880`01267775 : fffff880`0129b1bc fffff880`0988f7f0 fffff880`0988ee78 fffff880`0988f7f0 : nt!_C_specific_handler+0x8c
fffff880`0988df70 fffff800`02ca040d : fffff880`0129b1a8 00000000`00000000 fffff880`0124e000 00000000`00000000 : Ntfs!_GSHandlerCheck_SEH+0x75
fffff880`0988dfa0 fffff800`02ca7a90 : fffff880`0129b1a8 fffff880`0988e018 fffff880`0988ee78 fffff880`0124e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0988dfd0 fffff800`02cb49ef : fffff880`0988ee78 fffff880`0988e6e0 fffff880`00000000 fffffa80`087195e0 : nt!RtlDispatchException+0x410
fffff880`0988e6b0 fffff800`02c79d82 : fffff880`0988ee78 fffff8a0`0db91c70 fffff880`0988ef20 fffffa80`087195e0 : nt!KiDispatchException+0x16f
fffff880`0988ed40 fffff800`02c788fa : 00000000`00000000 fffff8a0`0db91c70 fffff880`0988f500 fffff8a0`0db91b40 : nt!KiExceptionDispatch+0xc2
fffff880`0988ef20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs! ?? ::FNODOBFM::`string'+2cc9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2cc9

BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2cc9

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

Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Sun Oct 24 07:31:04.918 2010 (GMT-4)
System Uptime: 0 days 5:52:44.215
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41289, 7fefc53c001, 731, 7f6fc53c005}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041289, The subtype of the bugcheck.
Arg2: 000007fefc53c001
Arg3: 0000000000000731
Arg4: 000007f6fc53c005

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


BUGCHECK_STR:  0x1a_41289

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cca379 to fffff80002c75740

STACK_TEXT:  
fffff880`0aa8b7e8 fffff800`02cca379 : 00000000`0000001a 00000000`00041289 000007fe`fc53c001 00000000`00000731 : nt!KeBugCheckEx
fffff880`0aa8b7f0 fffff800`02ce8cc3 : fffffa80`05d88f50 73100001`f2da7025 000007fe`fc537000 66600001`f45b0025 : nt! ?? ::FNODOBFM::`string'+0x4a49
fffff880`0aa8b830 fffff800`02ca8df9 : 00000000`00000000 000007fe`fc586fff fffffa80`00000000 fffff800`02c84b7c : nt! ?? ::FNODOBFM::`string'+0x3360b
fffff880`0aa8b9f0 fffff800`02f8e1d0 : fffffa80`09725350 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0aa8bb10 fffff800`02f8e5db : 00000000`00000000 000007fe`fc530000 fffffa80`00000001 fffffa80`0969c5b0 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0aa8bbd0 fffff800`02c74993 : fffffa80`097db320 fffff880`0aa8bca0 fffffa80`0a1cab30 00000000`0030df02 : nt!NtUnmapViewOfSection+0x5f
fffff880`0aa8bc20 00000000`771ffffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012c1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771ffffa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4a49
fffff800`02cca379 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4a49

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a49

BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a49

Followup: MachineOwner
---------
I recommend that you uninstall AVG antivirus using this tool: Tool (64 bit). AVG has been know to cause BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place. I you have installed AVG Identity Protection, uninstall it with this tool: Tool


Run Disk Check to test your hard drive -
Quote:

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

Test your RAM with Memtest. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Post your results.

I find one out of date driver on your system. Update this driver.
Quote:
AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD
My System SpecsSystem Spec
25 Oct 2010   #3

Windows 7 Ultimate x64
 
 

Thanks for the welcome and the fast reply.
Uninstalled Avg and Avg Identity protection, not without problems, had to use the normal uninstall also.


Searched the registry afterwards for "avg" and i found there are some values left, dont know if this is gonna cause trouble?

Moving forward.
My System SpecsSystem Spec
.


25 Oct 2010   #4

Windows 7 Ultimate 32 bit
 
 

Those should not cause a problem. However, you can download and run Ccleaner using the registry cleaner module. If it picks up those keys and you are certain those keys relate to AVG, you can have Ccleaner delete them. But first backup your registry and create a restore point. Keep us updated.
My System SpecsSystem Spec
25 Oct 2010   #5

Windows 7 Ultimate x64
 
 

Im waiting for the last disk to finish, from all except first disk(system) ive had a lot of
"The disk does not have enough space to replace bad clusters
detected in file 5152 of name ."

For a lot of files that is, ranging between several thousands, some of them are named though!
Some of the partitions are really full, one with only 73,7 MB ...

I will upload log as soon as possible
My System SpecsSystem Spec
25 Oct 2010   #6

Windows 7 Ultimate 32 bit
 
 

We will be here. A few bad disk clusters is normal; a lot of them can well mean a failing hard drive.
My System SpecsSystem Spec
25 Oct 2010   #7

Windows 7 Ultimate x64
 
 

Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
The first attribute offset 0x30 in file 0xec94 is incorrect.
Deleting corrupt file record segment 60564.
Deleted corrupt attribute list entry
with type code 128 in file 36858.
Unable to find child frs 0xec94 with sequence number 0x9.
The first attribute offset 0x30 in file 0xf36c is incorrect.
Deleting corrupt file record segment 62316.
Deleted corrupt attribute list entry
with type code 128 in file 57785.
Unable to find child frs 0xf36c with sequence number 0x4.
The first attribute offset 0x30 in file 0xec95 is incorrect.
Deleting corrupt file record segment 60565.
The first attribute offset 0x30 in file 0xec96 is incorrect.
Deleting corrupt file record segment 60566.
The first attribute offset 0x30 in file 0xec97 is incorrect.
Deleting corrupt file record segment 60567.
The first attribute offset 0x30 in file 0xf36d is incorrect.
Deleting corrupt file record segment 62317.
The first attribute offset 0x30 in file 0xf36e is incorrect.
Deleting corrupt file record segment 62318.
The first attribute offset 0x30 in file 0xf36f is incorrect.
Deleting corrupt file record segment 62319.
145664 file records processed. File verification completed.
286 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The object id index entry in file 0x19 points to file 0xec95
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
Index entry GH18C7~1.TXT of index $I30 in file 0x56 points to unused file 0xf36d.
Deleting index entry GH18C7~1.TXT in index $I30 of file 86.
Index entry GH24CF~1.TXT of index $I30 in file 0x56 points to unused file 0xf36e.
Deleting index entry GH24CF~1.TXT in index $I30 of file 86.
Index entry WER-14~1.XML of index $I30 in file 0x5b points to unused file 0xf36d.
Deleting index entry WER-14~1.XML in index $I30 of file 91.
Index entry WER888~1.XML of index $I30 in file 0x5b points to unused file 0xf36e.
Deleting index entry WER888~1.XML in index $I30 of file 91.
Index entry WER8F9~1.CAB of index $I30 in file 0x5b points to unused file 0xf36e.
Deleting index entry WER8F9~1.CAB in index $I30 of file 91.
Index entry WER8F9~1.XML of index $I30 in file 0x5b points to unused file 0xf36d.
Deleting index entry WER8F9~1.XML in index $I30 of file 91.
Index entry WER8FCB.tmp.cab.tmp of index $I30 in file 0x5b points to unused file 0xf36d.
Deleting index entry WER8FCB.tmp.cab.tmp in index $I30 of file 91.
Index entry WER8FC~1.TMP of index $I30 in file 0x5b points to unused file 0xf36d.
Deleting index entry WER8FC~1.TMP in index $I30 of file 91.
Index entry WER8FD~1.TXT of index $I30 in file 0x5b points to unused file 0xf36e.
Deleting index entry WER8FD~1.TXT in index $I30 of file 91.
Index entry RUNONC~2.PF of index $I30 in file 0xe16b points to unused file 0xf36e.
Deleting index entry RUNONC~2.PF in index $I30 of file 57707.
Index entry USERIN~1.PF of index $I30 in file 0xe16b points to unused file 0xf36e.
Deleting index entry USERIN~1.PF in index $I30 of file 57707.
Index entry WERFAU~1.PF of index $I30 in file 0xe16b points to unused file 0xf36e.
Deleting index entry WERFAU~1.PF in index $I30 of file 57707.
Index entry statecache.lock of index $I30 in file 0xe387 points to unused file 0xf36e.
Deleting index entry statecache.lock in index $I30 of file 58247.
Index entry STATEC~1.LOC of index $I30 in file 0xe387 points to unused file 0xf36e.
Deleting index entry STATEC~1.LOC in index $I30 of file 58247.
Index entry AP52BA~1.EXE of index $I30 in file 0xe389 points to unused file 0xf36e.
Deleting index entry AP52BA~1.EXE in index $I30 of file 58249.
Index entry APC3A9~1.EXE of index $I30 in file 0xe389 points to unused file 0xf36e.
Deleting index entry APC3A9~1.EXE in index $I30 of file 58249.
Index entry SESSIO~1.JS of index $I30 in file 0xe3cc points to unused file 0xf36e.
Deleting index entry SESSIO~1.JS in index $I30 of file 58316.
Index entry SESSIO~2.JS of index $I30 in file 0xe3cc points to unused file 0xf36e.
Deleting index entry SESSIO~2.JS in index $I30 of file 58316.
Index entry SESSIO~3.JS of index $I30 in file 0xe3cc points to unused file 0xf36e.
Deleting index entry SESSIO~3.JS in index $I30 of file 58316.
Index entry CACHE~1.TRA of index $I30 in file 0xe3d3 points to unused file 0xf36e.
Deleting index entry CACHE~1.TRA in index $I30 of file 58323.
Index entry 6c821b.msi of index $I30 in file 0xe9ed points to unused file 0xec97.
Deleting index entry 6c821b.msi in index $I30 of file 59885.
Index entry {F30F3A63-0DF7-42F7-F96F-A6AFAE169802} of index $I30 in file 0xe9ed points to unused file 0xec95.
Deleting index entry {F30F3A63-0DF7-42F7-F96F-A6AFAE169802} in index $I30 of file 59885.
Index entry {F30F3~1 of index $I30 in file 0xe9ed points to unused file 0xec95.
Deleting index entry {F30F3~1 in index $I30 of file 59885.
Index entry helpzh-CHT.enc of index $I30 in file 0xec93 points to unused file 0xec94.
Deleting index entry helpzh-CHT.enc in index $I30 of file 60563.
Index entry HELPZH~1.ENC of index $I30 in file 0xec93 points to unused file 0xec94.
Deleting index entry HELPZH~1.ENC in index $I30 of file 60563.
Index entry usage_colose_d.bmp of index $I30 in file 0xf320 points to unused file 0xf36f.
Deleting index entry usage_colose_d.bmp in index $I30 of file 62240.
Index entry USAGE_~1.BMP of index $I30 in file 0xf320 points to unused file 0xf36f.
Deleting index entry USAGE_~1.BMP in index $I30 of file 62240.
Index entry POA24C~1.BMP of index $I30 in file 0xf368 points to unused file 0xf36d.
Deleting index entry POA24C~1.BMP in index $I30 of file 62312.
Index entry POB2F7~1.BMP of index $I30 in file 0xf368 points to unused file 0xf36e.
Deleting index entry POB2F7~1.BMP in index $I30 of file 62312.
Index entry pop_big_small_d.bmp of index $I30 in file 0xf368 points to unused file 0xf36c.
Deleting index entry pop_big_small_d.bmp in index $I30 of file 62312.
Index entry pop_big_small_n.bmp of index $I30 in file 0xf368 points to unused file 0xf36d.
Deleting index entry pop_big_small_n.bmp in index $I30 of file 62312.
Index entry pop_big_small_o.bmp of index $I30 in file 0xf368 points to unused file 0xf36e.
Deleting index entry pop_big_small_o.bmp in index $I30 of file 62312.
Index entry POP_BI~4.BMP of index $I30 in file 0xf368 points to unused file 0xf36c.
Deleting index entry POP_BI~4.BMP in index $I30 of file 62312.
Index entry 8EE3C9~1 of index $I30 in file 0xf985 points to unused file 0xf36d.
Deleting index entry 8EE3C9~1 in index $I30 of file 63877.
Index entry A3BB87~1 of index $I30 in file 0xf985 points to unused file 0xec94.
Deleting index entry A3BB87~1 in index $I30 of file 63877.
Index entry B2D73C~1 of index $I30 in file 0xf985 points to unused file 0xf36c.
Deleting index entry B2D73C~1 in index $I30 of file 63877.
Index entry DF9BA6~1 of index $I30 in file 0xf985 points to unused file 0xf36e.
Deleting index entry DF9BA6~1 in index $I30 of file 63877.
Index entry KERNEL~2 of index $I30 in file 0x10f21 points to unused file 0xf36e.
Deleting index entry KERNEL~2 in index $I30 of file 69409.
The two index entries of length 0x70 and 0x68 are either identical
or appear in the wrong order.
1b 22 01 00 00 00 01 00 70 00 5a 00 00 00 00 00 ."......p.Z.....
2b 21 01 00 00 00 01 00 00 dc 90 57 0e 38 cb 01 +!.........W.8..
00 dc 90 57 06 38 cb 01 be f0 35 0c 55 6d cb 01 ...W.8....5.Um..
be f0 35 0c 55 6d cb 01 00 60 00 00 00 00 00 00 ..5.Um...`......
e9 54 00 00 00 00 00 00 20 00 00 00 00 00 00 00 .T...... .......
0c 02 53 00 4f 00 55 00 52 00 43 00 45 00 7e 00 ..S.O.U.R.C.E.~.
31 00 2e 00 52 00 45 00 32 00 00 00 00 00 00 00 1...R.E.2.......
2e 00 6a 00 73 00 00 00 65 00 6e 00 69 00 7a 00 ..j.s...e.n.i.z.
----------------------------------------------------------------------
1c 22 01 00 00 00 01 00 68 00 58 00 00 00 00 00 ."......h.X.....
2b 21 01 00 00 00 01 00 00 dc 90 57 0e 38 cb 01 +!.........W.8..
00 dc 90 57 0e 38 cb 01 ce 17 36 0c 55 6d cb 01 ...W.8....6.Um..
ce 17 36 0c 55 6d cb 01 00 70 00 00 00 00 00 00 ..6.Um...p......
f4 64 00 00 00 00 00 00 20 00 00 00 00 00 00 00 .d...... .......
0b 02 53 00 47 00 55 00 52 00 43 00 45 00 7e 00 ..S.G.U.R.C.E.~.
32 00 2e 00 4a 00 53 00 1e 22 01 00 00 00 01 00 2...J.S.."......
70 00 5a 00 00 00 00 00 2b 21 01 00 00 00 01 00 p.Z.....+!......
Sorting index $I30 in file 74027.
Unable to locate the file name attribute of index entry SGURCE~2.JS
of index $I30 with parent 0x1212b in file 0x1221c.
Deleting index entry SGURCE~2.JS in index $I30 of file 74027.
The two index entries of length 0x78 and 0x70 are either identical
or appear in the wrong order.
78 21 01 00 00 00 01 00 78 00 5a 00 01 00 00 00 x!......x.Z.....
4c 21 01 00 00 00 01 00 00 dc 90 57 0e 38 cb 01 L!.........W.8..
00 dc 90 57 0e 38 cb 01 8e 10 87 0b 55 6d cb 01 ...W.8......Um..
8e 10 87 0b 55 6d cb 01 00 10 00 00 00 00 00 00 ....Um..........
9a 0e 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ .......
0c 02 47 00 4c 00 4f 00 53 00 53 00 59 00 7e 00 ..G.L.O.S.S.Y.~.
33 00 2e 00 50 00 4e 00 47 00 00 00 00 00 00 00 3...P.N.G.......
04 00 00 00 00 00 00 00 64 00 50 00 72 00 65 00 ........d.P.r.e.
73 00 73 00 65 00 64 00 2e 00 70 00 6e 00 67 00 s.s.e.d...p.n.g.
----------------------------------------------------------------------
79 21 01 00 00 00 01 00 70 00 5a 00 00 00 00 00 y!......p.Z.....
4c 21 01 00 00 00 01 00 00 dc 90 57 0e 38 cb 01 L!.........W.8..
00 dc 90 57 0e 38 cb 01 f3 b5 8c 0b 55 6d cb 01 ...W.8......Um..
f3 b5 8c 0b 55 6d cb 01 00 10 00 00 00 00 00 00 ....Um..........
9b 0e 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ .......
0c 02 47 00 44 00 4f 00 53 00 53 00 59 00 7e 00 ..G.D.O.S.S.Y.~.
34 00 2e 00 50 00 4e 00 47 00 00 00 00 00 00 00 4...P.N.G.......
7a 21 01 00 00 00 01 00 68 00 58 00 00 00 00 00 z!......h.X.....
Sorting index $I30 in file 74060.
Unable to locate the file name attribute of index entry GDOSSY~4.PNG
of index $I30 with parent 0x1214c in file 0x12179.
Deleting index entry GDOSSY~4.PNG in index $I30 of file 74060.
Unable to locate the file name attribute of index entry graphDabelCalloutLeft&png
of index $I30 with parent 0x1214c in file 0x1217b.
Deleting index entry graphDabelCalloutLeft&png in index $I30 of file 74060.
Index entry VERSIO~1.HTM of index $I30 in file 0x18b9f points to unused file 0xf36e.
Deleting index entry VERSIO~1.HTM in index $I30 of file 101279.
Index entry ADSADC~1.TXT of index $I30 in file 0x1da9f points to unused file 0xf36e.
Deleting index entry ADSADC~1.TXT in index $I30 of file 121503.
Index entry Y1MLA5~1.JPG of index $I30 in file 0x1da9f points to unused file 0xec94.
Deleting index entry Y1MLA5~1.JPG in index $I30 of file 121503.
Index entry Y1MHNU~1.JPG of index $I30 in file 0x1dc92 points to unused file 0xec94.
Deleting index entry Y1MHNU~1.JPG in index $I30 of file 122002.
Index entry Y1MN8S~1.JPG of index $I30 in file 0x1dc92 points to unused file 0xf36e.
Deleting index entry Y1MN8S~1.JPG in index $I30 of file 122002.
204596 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file GLOSSY~4.PNG (74105) into directory file 74060.
Recovering orphaned file graphLabelCalloutLeft.png (74107) into directory file 74060.
Recovering orphaned file SOURCE~2.JS (74268) into directory file 74027.
22 unindexed files scanned. CHKDSK is recovering remaining unindexed files.
19 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
145664 file SDs/SIDs processed. Cleaning up 11 unused index entries from index $SII of file 0x9.
Cleaning up 11 unused index entries from index $SDH of file 0x9.
Cleaning up 11 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 36858.
Inserting data attribute into file 57785.
29469 data files processed. CHKDSK is verifying Usn Journal...
10417344 USN bytes processed. Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

976759807 KB total disk space.
93177512 KB in 106581 files.
77328 KB in 29471 indexes.
0 KB in bad sectors.
252619 KB in use by the system.
65536 KB occupied by the log file.
883252348 KB available on disk.

4096 bytes in each allocation unit.
244189951 total allocation units on disk.
220813087 allocation units available on disk.

Internal Info:
00 39 02 00 7e 13 02 00 a8 fc 03 00 00 00 00 00 .9..~...........
1d 52 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 .R..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
25 Oct 2010   #8

Windows 7 Ultimate x64
 
 

Sorry brother, realised it was the wrong one....
Seems none with the right date and time are there.
If it goes on the windows or bios clock, it should display the right time unless i see the wrong time.

Any idea?

Gonna try memtest.
My System SpecsSystem Spec
25 Oct 2010   #9

Windows 7 Ultimate x64
 
 

sure was problem with memory had 10%pass with 1800 errors of memory adress failure and no passes
gonna try memtest all the way....
My System SpecsSystem Spec
25 Oct 2010   #10

Windows 7 Ultimate 32 bit
 
 

Basically, Check Disk found a lot of file errors and indexing errors. It apparently has corrected the problems. You have no bad sectors on the disk.

You can shut down Memtest. You have a RAM problem. Remember that bad RAM can a be a faulty stick of RAM, a bad RAM slot, or incompatible RAM. Remove all of your RAM but one stick. Test that stick with Memtest for at least 7 passes. If that stick passes, mark it as good, remove it and test the next stick. Do this for each RAM stick. Now take a known good stick and test each RAM slot. Let us know the results.
My System SpecsSystem Spec
Reply

 In big need of BSOD minidump help!




Thread Tools



Similar help and support threads for2: In big need of BSOD minidump help!
Thread Forum
BSOD 1E Minidump BSOD Help and Support
bsod and minidump BSOD Help and Support
BSOD Minidump BSOD Help and Support
bsod minidump BSOD Help and Support
Minidump BSOD BSOD Help and Support
BSOD Minidump BSOD Help and Support
BSOD Minidump Help BSOD Help and Support

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:28 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33