New
#11
this is my only thread ive ever made here
this is my only thread ive ever made here
Here, have you made threads on other sites??
In case you have not (despite the name) here is a repeat
You have a memory problem. Running memtest has shown us that. Here is the usual cause of the crash you had
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.
Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Of course you need to fix the memory problem and you might also want to run a chkdsk
CHKDSK /R /F:
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 Win7) (winlogon for XP).
Copy/paste the results into your next post.
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\Windows_NT6_BSOD_jcgriff2\092110-35568-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path element 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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50 Debug session time: Tue Sep 21 11:31:08.288 2010 (GMT-4) System Uptime: 0 days 0:00:54.474 Loading Kernel Symbols ............................................................... ................................................................ ................................... Loading User Symbols Loading unloaded module list ... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff88007e2a1c8, fffff88007e29a30, fffff80002ee67ab} Probably caused by : Ntfs.sys ( Ntfs!NtfsCreateFcb+211 ) Followup: MachineOwner --------- 7: 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: fffff88007e2a1c8 Arg3: fffff88007e29a30 Arg4: fffff80002ee67ab Debugging Details: ------------------ EXCEPTION_RECORD: fffff88007e2a1c8 -- (.exr 0xfffff88007e2a1c8) ExceptionAddress: fffff80002ee67ab (nt!RtlInsertElementGenericTableFullAvl+0x0000000000000097) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88007e29a30 -- (.cxr 0xfffff88007e29a30) rax=effff8a000fd1790 rbx=fffff8a001b89010 rcx=effff8a000fd1790 rdx=0000000000000001 rsi=fffffa8006f99640 rdi=0000000000000000 rip=fffff80002ee67ab rsp=fffff88007e2a400 rbp=0000000000000000 r8=fffff8a0011b7010 r9=00000000ffffffff r10=fffffa800395e148 r11=0000000000000001 r12=fffff8a001b59674 r13=0000000000000010 r14=fffff88007e2a4c0 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!RtlInsertElementGenericTableFullAvl+0x97: fffff800`02ee67ab 4c394008 cmp qword ptr [rax+8],r8 ds:002b:effff8a0`00fd1798=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: explorer.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: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f80e0 ffffffffffffffff FOLLOWUP_IP: Ntfs!NtfsCreateFcb+211 fffff880`016f97c9 41830c2440 or dword ptr [r12],40h FAULTING_IP: nt!RtlInsertElementGenericTableFullAvl+97 fffff800`02ee67ab 4c394008 cmp qword ptr [rax+8],r8 BUGCHECK_STR: 0x24 LAST_CONTROL_TRANSFER: from fffff880016f97c9 to fffff80002ee67ab STACK_TEXT: fffff880`07e2a400 fffff880`016f97c9 : 00010000`0000a24c fffffa80`094bc550 fffffa80`096dfb30 fffff8a0`01b59670 : nt!RtlInsertElementGenericTableFullAvl+0x97 fffff880`07e2a440 fffff880`016c5cf6 : fffffa80`096dfb30 fffffa80`06f99180 fffffa80`096dfb30 00010000`0000a24c : Ntfs!NtfsCreateFcb+0x211 fffff880`07e2a520 fffff880`016e9b04 : fffff880`07e2aab0 fffffa80`094bc550 fffffa80`096dfb30 00000000`00000000 : Ntfs!NtfsOpenFile+0x1ca fffff880`07e2a700 fffff880`01652c0d : fffffa80`096dfb30 fffffa80`094bc550 fffff880`07e2aab0 00000000`00000b00 : Ntfs!NtfsCommonCreate+0xc54 fffff880`07e2a8e0 fffff800`02ecfe5a : fffff880`07e2aa20 fffff880`0124cd5a fffffa80`094eee10 fffff880`07e2a9c8 : Ntfs!NtfsCommonCreateCallout+0x1d fffff880`07e2a910 fffff880`01652b2f : fffff880`01652bf0 fffff880`07e2aa20 fffff880`07e2aa00 fffff880`016f432d : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`07e2a9f0 fffff880`016ef9c0 : 00000000`00000000 00000000`00000000 fffff880`07e2ac40 fffffa80`094bc550 : Ntfs!NtfsCommonCreateOnNewStack+0x4f fffff880`07e2aa50 fffff880`0124023f : fffffa80`06f99030 fffffa80`094bc550 00000000`00000000 fffffa80`04b03de0 : Ntfs!NtfsFsdCreate+0x1b0 fffff880`07e2ac00 fffff880`0125f2b9 : fffffa80`094bc550 fffffa80`04c39010 fffffa80`094bc500 fffffa80`04b03de0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`07e2ac90 fffff800`031c3807 : 00000000`00000005 fffff800`031c3260 fffffa80`091e2010 00000000`00000000 : fltmgr!FltpCreate+0x2a9 fffff880`07e2ad40 fffff800`031b9e84 : fffffa80`04c39bd0 00000000`00000000 fffffa80`091df010 00000000`00000701 : nt!IopParseDevice+0x5a7 fffff880`07e2aed0 fffff800`031bee4d : fffffa80`091df010 fffff880`07e2b030 fffff880`00000040 fffffa80`039ecf30 : nt!ObpLookupObjectName+0x585 fffff880`07e2afd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByName+0x1cd SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: Ntfs!NtfsCreateFcb+211 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f STACK_COMMAND: .cxr 0xfffff88007e29a30 ; kb FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsCreateFcb+211 BUCKET_ID: X64_0x24_Ntfs!NtfsCreateFcb+211 Followup: MachineOwner ---------
old drivers
Code:GEARAspiWDM.sys fffff880`031ed000 fffff880`031f6000 0x00009000 0x47a3274b 2/1/2008 10:06:03 adfs.SYS fffff880`08071000 fffff880`08089000 0x00018000 0x48640195 6/26/2008 16:52:37 iaStorV.sys fffff880`014ba000 fffff880`015d8000 0x0011e000 0x49dcd76d 4/8/2009 12:57:17 spldr.sys fffff880`01bce000 fffff880`01bd6000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 amdxata.sys fffff880`01232000 fffff880`0123d000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59 HookCentre.sys fffff880`08b61000 fffff880`08b70000 0x0000f000 0x4a3b67f8 6/19/2009 06:27:04 ATSwpWDF.sys fffff880`0666f000 fffff880`06728000 0x000b9000 0x4a4d062e 7/2/2009 15:10:38 gdwfpcd64.sys fffff880`030e0000 fffff880`030f0000 0x00010000 0x4a529fc9 7/6/2009 21:07:21
Here are the results of CHKDSK:
Ill hear what to do next=)Code:Logboeknaam: Application Bron: Microsoft-Windows-Wininit Datum: 28-9-2010 19:03:51 Gebeurtenis-id:1001 Taakcategorie: Geen Niveau: Informatie Trefwoorden: Klassiek Gebruiker: n.v.t. Computer: Mark-PC Beschrijving: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 185088 file records processed. File verification completed. 101 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 241192 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 185088 file SDs/SIDs processed. Cleaning up 627 unused index entries from index $SII of file 0x9. Cleaning up 627 unused index entries from index $SDH of file 0x9. Cleaning up 627 unused security descriptors. Security descriptor verification completed. 28053 data files processed. CHKDSK is verifying Usn Journal... 33885992 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 185072 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 124780299 free clusters processed. Free space verification is complete. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. 625033215 KB total disk space. 125522204 KB in 149645 files. 84428 KB in 28054 indexes. 0 KB in bad sectors. 305383 KB in use by the system. 65536 KB occupied by the log file. 499121200 KB available on disk. 4096 bytes in each allocation unit. 156258303 total allocation units on disk. 124780300 allocation units available on disk. Internal Info: 00 d3 02 00 2c b6 02 00 cd e0 04 00 00 00 00 00 ....,........... 9c 26 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 .&..,........... 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. Gebeurtenis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-09-28T17:03:51.000000000Z" /> <EventRecordID>6237</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Mark-PC</Computer> <Security /> </System> <EventData> <Data> Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 185088 file records processed. File verification completed. 101 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 241192 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 185088 file SDs/SIDs processed. Cleaning up 627 unused index entries from index $SII of file 0x9. Cleaning up 627 unused index entries from index $SDH of file 0x9. Cleaning up 627 unused security descriptors. Security descriptor verification completed. 28053 data files processed. CHKDSK is verifying Usn Journal... 33885992 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 185072 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 124780299 free clusters processed. Free space verification is complete. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. 625033215 KB total disk space. 125522204 KB in 149645 files. 84428 KB in 28054 indexes. 0 KB in bad sectors. 305383 KB in use by the system. 65536 KB occupied by the log file. 499121200 KB available on disk. 4096 bytes in each allocation unit. 156258303 total allocation units on disk. 124780300 allocation units available on disk. Internal Info: 00 d3 02 00 2c b6 02 00 cd e0 04 00 00 00 00 00 ....,........... 9c 26 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 .&..,........... 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. </Data> </EventData> </Event>
Thanks!
last 2 days got some new BSODs:
0x0A IRQL_NOT_LESS_OR_EQUAL
0x1E
0x19 BAD_POOL_HEADER
0x50 PAGE_FAULT_IN_NONPAGED_AREA
Any results yet on my CHKDSK?
0x0A IRQL_NOT_LESS_OR_EQUAL
0x1E
0x19 BAD_POOL_HEADER
0x50 PAGE_FAULT_IN_NONPAGED_AREA
I think all these are related to bad memory. These are what I got when my memory went bad. As ZIGZAG said RMA it back to OCZ. Seems as though there are a lot of people with bad memory from OCZ. I found one stick out of 3 to be bad. So went and bought some ram from a trusted manufacturer (Crucial).
I was told that OCZ is one of the best but after all these problems I think ill buy memory from kingston of geil.
Ill go back to the shop this saterday so Ill see if i can get my money back=)
Today I went back to the store and changed my 4GB of OCZ memory for 6 GB tri-kit GeIL memory!
So far no BSODs =D hope it stays this way.
Thanks for the help!!
btw already results for my CHKDSK?