New
#11
well i will run some of the test he said to use an see if i can find what is! i dont think its the drivers since i have them all up to date or so windows tells me! everything is under warranty u think i should get it all changed???
well i will run some of the test he said to use an see if i can find what is! i dont think its the drivers since i have them all up to date or so windows tells me! everything is under warranty u think i should get it all changed???
How much longer are you warranties? I would test each piece of hardware at a time to determine what it is if you have the time. Otherwise, it may be worth sending in the older pieces first.
there all brand new they just arrived monday from the company i bought them off online!!tbh i aint sure how long they are but there barnd new so i wud say a year or more
See if you can narrow down the hardware more over the next few days. We'll be here to help you figure out what the likely hardware pieces are.
well its after happing again just 5 minutes ago!! was just surfing the internet this time. will attach crash file! i updated the motherboard bios an drivers for the graphics card but no luck i guess.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [H:\BSODDmpFiles\Moteo\Windows_NT6_BSOD_jcgriff2\012612-28189-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`0349e670 Debug session time: Thu Jan 26 14:38:04.404 2012 (UTC - 7:00) System Uptime: 0 days 1:01:23.136 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa8184fd7418, 2, 0, fffff8000335eb55} Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffffa8184fd7418, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000335eb55, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003508100 fffffa8184fd7418 CURRENT_IRQL: 2 FAULTING_IP: nt!MiGetTopLevelPfn+65 fffff800`0335eb55 4c8b4928 mov r9,qword ptr [rcx+28h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: svchost.exe TRAP_FRAME: fffff88009721390 -- (.trap 0xfffff88009721390) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000081a9d15 rbx=0000000000000000 rcx=fffffa8184fd73f0 rdx=fffffff55587b5c8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000335eb55 rsp=fffff88009721528 rbp=0000000000000005 r8=fffffe0009721560 r9=00000000081a9d15 r10=fffff880097215d8 r11=0000000000000001 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!MiGetTopLevelPfn+0x65: fffff800`0335eb55 4c8b4928 mov r9,qword ptr [rcx+28h] ds:0100:fffffa81`84fd7418=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032d51e9 to fffff800032d5c40 STACK_TEXT: fffff880`09721248 fffff800`032d51e9 : 00000000`0000000a fffffa81`84fd7418 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`09721250 fffff800`032d3e60 : 00000000`00000000 fffffa80`0efd4000 00000000`42506650 000fffff`ffffffff : nt!KiBugCheckDispatch+0x69 fffff880`09721390 fffff800`0335eb55 : fffff800`03381482 00000000`081a9d15 fffffa80`0efd4cb8 00000000`42506600 : nt!KiPageFault+0x260 fffff880`09721528 fffff800`03381482 : 00000000`081a9d15 fffffa80`0efd4cb8 00000000`42506600 fffff800`035c173f : nt!MiGetTopLevelPfn+0x65 fffff880`09721530 fffff800`03381c7b : 00000000`00000000 00000000`00000004 fffffa80`0efd4cb8 fffffa80`0efd4000 : nt!MiIdentifyPfn+0x722 fffff880`097215d0 fffff800`036e67e5 : fffffa80`0efd4000 fffff880`09721b60 fffff880`097216a8 00000000`00000000 : nt!MmQueryPfnList+0xbb fffff880`09721610 fffff800`036294c8 : 00000000`00000006 00000000`00000000 fffffa80`0efd4000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115 fffff880`09721660 fffff800`035dfbd3 : 00000000`00000000 00000000`00000000 00000000`64496d4d 00000000`64496d01 : nt! ?? ::NNGAKEGL::`string'+0x4810d fffff880`097216f0 fffff800`035e0449 : 00000000`01ecbca8 fffff800`032e1f58 00000000`01ecbd00 00000000`01ecbcc8 : nt!ExpQuerySystemInformation+0x1193 fffff880`09721aa0 fffff800`032d4ed3 : 00000000`00000005 fffff880`09721b60 00000000`0c218de0 00000000`037a1c20 : nt!NtQuerySystemInformation+0x4d fffff880`09721ae0 00000000`778f167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`01ecbbc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778f167a STACK_COMMAND: kb FOLLOWUP_IP: nt!MiGetTopLevelPfn+65 fffff800`0335eb55 4c8b4928 mov r9,qword ptr [rcx+28h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MiGetTopLevelPfn+65 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MiGetTopLevelPfn+65 BUCKET_ID: X64_0xA_nt!MiGetTopLevelPfn+65 Followup: MachineOwner ---------
well am after moving to using the labtop.....last nite after using chkdsk it was taking so long on part 5 i went to sleep came back this moring an it had crashed it was stuck on the blue screen restart copy all the files for the carsh it crashed again wen i was using this....tried again same thing happend could be the harddrive?? the problem seems to have gotten a lot worse now it seems to restart every few minutes!! here are the files an thank again
Code:
- Loading Dump File [K:\BSODDmpFiles\Moteo\Windows_NT6_BSOD_jcgriff2\012712-27144-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 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03264000 PsLoadedModuleList = 0xfffff800`034a9670 Debug session time: Fri Jan 27 00:34:03.579 2012 (GMT-7) System Uptime: 0 days 0:05:17.422 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa80102f8b30, fffffa80102f8e10, fffff800035e48b0} Probably caused by : csrss.exe Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa80102f8b30, Terminating object Arg3: fffffa80102f8e10, Process image file name Arg4: fffff800035e48b0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: fffffa80102f8b30 IMAGE_NAME: csrss.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: csrss FAULTING_MODULE: 0000000000000000 PROCESS_NAME: csrss.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. BUGCHECK_STR: 0xF4_IOERR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff880`0edb9438 fffff800`0366b5e2 : 00000000`000000f4 00000000`00000003 fffffa80`102f8b30 fffffa80`102f8e10 : nt!KeBugCheckEx fffff880`0edb9440 fffff800`0361899b : ffffffff`ffffffff fffffa80`11628060 fffffa80`102f8b30 fffffa80`102f8b30 : nt!PspCatchCriticalBreak+0x92 fffff880`0edb9480 fffff800`03598448 : ffffffff`ffffffff 00000000`00000001 fffffa80`102f8b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6 fffff880`0edb94d0 fffff800`032dfed3 : fffffa80`102f8b30 fffff800`c0000006 fffffa80`11628060 00000000`013d0f40 : nt!NtTerminateProcess+0xf4 fffff880`0edb9550 fffff800`032dc470 : fffff800`0332c67f fffff880`0edba038 fffff880`0edb9d90 fffff880`0edba0e0 : nt!KiSystemServiceCopyEnd+0x13 fffff880`0edb96e8 fffff800`0332c67f : fffff880`0edba038 fffff880`0edb9d90 fffff880`0edba0e0 00000000`013d1c50 : nt!KiServiceLinkage fffff880`0edb96f0 fffff800`032e02c2 : fffff880`0edba038 00000000`0001e102 fffff880`0edba0e0 00000000`013d1728 : nt! ?? ::FNODOBFM::`string'+0x49874 fffff880`0edb9f00 fffff800`032dee3a : 00000000`00000000 000007fe`fe1e1330 fffffa80`11628001 00000000`0001e102 : nt!KiExceptionDispatch+0xc2 fffff880`0edba0e0 00000000`77ac9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a 00000000`013d1670 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ac9c12 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe Followup: MachineOwner ---------
- Loading Dump File [K:\BSODDmpFiles\Moteo\Windows_NT6_BSOD_jcgriff2\012712-23337-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 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0321e000 PsLoadedModuleList = 0xfffff800`03463670 Debug session time: Thu Jan 26 21:30:00.826 2012 (GMT-7) System Uptime: 0 days 0:05:32.670 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa80105d9b30, fffffa80105d9e10, fffff8000359e8b0} Probably caused by : wininit.exe Followup: MachineOwner --------- 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa80105d9b30, Terminating object Arg3: fffffa80105d9e10, Process image file name Arg4: fffff8000359e8b0, Explanatory message (ascii) Debugging Details: ------------------ PROCESS_OBJECT: fffffa80105d9b30 IMAGE_NAME: wininit.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 PROCESS_NAME: wininit.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. BUGCHECK_STR: 0xF4_IOERR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 STACK_TEXT: fffff880`07701e38 fffff800`036255e2 : 00000000`000000f4 00000000`00000003 fffffa80`105d9b30 fffffa80`105d9e10 : nt!KeBugCheckEx fffff880`07701e40 fffff800`035d299b : ffffffff`ffffffff fffffa80`1004db60 fffffa80`105d9b30 fffffa80`105d9b30 : nt!PspCatchCriticalBreak+0x92 fffff880`07701e80 fffff800`03552448 : ffffffff`ffffffff 00000000`00000001 fffffa80`105d9b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6 fffff880`07701ed0 fffff800`03299ed3 : fffffa80`105d9b30 fffff800`c0000006 fffffa80`1004db60 00000000`00c80d00 : nt!NtTerminateProcess+0xf4 fffff880`07701f50 fffff800`03296470 : fffff800`032e667f fffff880`07702a38 fffff880`07702790 fffff880`07702ae0 : nt!KiSystemServiceCopyEnd+0x13 fffff880`077020e8 fffff800`032e667f : fffff880`07702a38 fffff880`07702790 fffff880`07702ae0 00000000`7750f928 : nt!KiServiceLinkage fffff880`077020f0 fffff800`0329a2c2 : fffff880`07702a38 00000000`00d00000 fffff880`07702ae0 00000000`7751bed8 : nt! ?? ::FNODOBFM::`string'+0x49874 fffff880`07702900 fffff800`03298e3a : 00000000`00000000 00000000`774d0c34 00000000`776a8d01 00000000`00d00000 : nt!KiExceptionDispatch+0xc2 fffff880`07702ae0 00000000`77598f55 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a 00000000`00c81420 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77598f55 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe Followup: MachineOwner ---------
- A windows system process was terminated unexpectedly. Possible causes are hard disk errors... Viruses... Lack of Windows updates... Drivers...
- A windows system process was terminated unexpectedly. Possible causes are hard disk errors... Viruses... Lack of Windows updates... Drivers...
Each of those crashes occurred probably 3-4 times each at least.
Definitely points to the hard drive being bad. I would also run Memtest86+ to make sure you do not have multiple hardware problems.
i cant run it cause the computer crashes every ten minutes its impossible i barely get enuf time to get the crash files! its after gettin a whole lot worse! even wen its idle after ten minutes it crashes. so i have an external hard drive would i be able to install windows on it?? just to see if it resolves the problem?? again thanks for the help
Unfortunately, Windows will not install to an external. Probably not a fast enough interface via the connection.
Memtest86+ does not require Windows to run, so you should be able to run it. You may need to download and burn the CD on another machine if the current one is that unstable, though.