New
#41
I have speedfan running and it says my voltage on the 12v is 11.9. Is this a bad thing or is it normal?
BSOD's/Restarts have me stumped
-
-
New #42
A tenth of a volt may simply be the plus or minus error of SpeedFan. Try CPUZ to verify the voltage reading.
I looked at your last six dumps.
1. While you are troubleshooting, I suggest that you uninstall SuperAntiSpyware just in case it is causing interference and conflict.Bugcheck 1E, KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.
Bugcheck A (2X), IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Bugcheck 109, CRITICAL_STRUCTURE_CORRUPTION. Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular).
Bugcheck 101 (2X), CLOCK_WATCHDOG_TIMEOUT. Usual causes: Device driver, BIOS bug, hardware defect.
2. Two instances of bugcheck 101 are pretty significant. Read these to articles on this bugcheck:
https://www.sevenforums.com/crash-loc...tml#post567135
https://www.sevenforums.com/crashes-d...tml#post356791
3. Go to your motherboard's website and check your version of your BIOS. See if there are any problems you are having that are solved by a a later version. I do not often recommend flashing the BIOS because there is a risk involved. If there is problem addressed by a BIOS that applies to your computer, consider flashing your BIOS to the latest version. If you choose to do this, flash you BIOS outside of Windows.
4. Run Prime 95 again to test your CPU and your ram. Carefully the instructions in this tutorial: https://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
Code:Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0280c000 PsLoadedModuleList = 0xfffff800`02a49e50 Debug session time: Mon Jan 31 20:39:46.190 2011 (GMT-5) System Uptime: 0 days 0:13:33.000 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000096, fffff80002867710, 0, 0} Probably caused by : memory_corruption Followup: memory_corruption --------- 3: 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: ffffffffc0000096, The exception code that was not handled Arg2: fffff80002867710, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction. FAULTING_IP: nt!MiDereferenceControlAreaBySection+30 fffff800`02867710 440f22c0 mov cr8,rax EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 0 EXCEPTION_RECORD: fffff880054677e8 -- (.exr 0xfffff880054677e8) ExceptionAddress: fffff80002867710 (nt!MiDereferenceControlAreaBySection+0x0000000000000030) ExceptionCode: c0000096 ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff88005467890 -- (.trap 0xfffff88005467890) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000fe13 rbx=0000000000000000 rcx=fffffa8002a0d8e0 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002867710 rsp=fffff88005467a28 rbp=0000000000000002 r8=fffffa80029ba6c0 r9=fffff880054678c8 r10=fffffa80024d43c0 r11=fffff88005467ab0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di ng nz na po nc nt!MiDereferenceControlAreaBySection+0x30: fffff800`02867710 440f22c0 mov cr8,rax Resetting default scope LAST_CONTROL_TRANSFER: from fffff800028b6a39 to fffff8000287c740 STACK_TEXT: fffff880`05467018 fffff800`028b6a39 : 00000000`0000001e ffffffff`c0000096 fffff800`02867710 00000000`00000000 : nt!KeBugCheckEx fffff880`05467020 fffff800`0287bd82 : fffff880`054677e8 fffffa80`02a0d8e0 fffff880`05467890 fffffa80`024cca30 : nt!KiDispatchException+0x1b9 fffff880`054676b0 fffff800`0287a68a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`05467890 fffff800`02867710 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a fffff880`05467a28 00000000`00000000 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : nt!MiDereferenceControlAreaBySection+0x30 STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 31 errors : !nt (fffff800028676cc-fffff800028677bd) fffff800028676c0 33 c0 4c 33 c8 4c 33 d0 4c 33 d8 33 *04 *00 be ff 3.L3.L3.L3.3.... fffff800028676d0 ff ff 90 48 83 c4 28 c3 90 90 90 90 *00 *00 90 90 ...H..(......... fffff800028676e0 48 89 5c 24 10 48 89 6c 24 18 48 89 *c8 *4c 20 57 H.\$.H.l$.H..L W fffff800028676f0 41 54 41 55 41 56 41 57 48 83 ec 30 *90 *90 fa 48 ATAUAVAWH..0...H fffff80002867700 8b d9 44 0f 20 c0 48 89 44 24 60 b8 *13 *fe 00 00 ..D. .H.D$`..... fffff80002867710 44 0f 22 c0 65 48 8b 34 25 20 00 00 00 *4b 8b 25 D.".eH.4% ...K.% fffff80002867720 20 3f 1a 00 33 ff 41 c1 ec 10 41 80 *49 *8b 0f 85 ?..3.A...A.I... fffff80002867730 31 3b 09 00 45 33 ed 45 33 f6 ff 86 *b8 *00 00 00 1;..E3.E3....... fffff80002867740 f0 0f ba 69 48 1f 72 4c 8b 4b 48 81 *ce *75 00 00 ...iH.rL.KH..u.. fffff80002867750 80 0f 85 26 3b 09 00 85 ff 75 46 45 *70 *48 0f 85 ...&;....uFEpH.. fffff80002867760 46 3b 09 00 8a 54 24 60 48 ff 4b 18 *c5 *30 7b 30 F;...T$`H.K..0{0 fffff80002867770 48 8b cb 48 8b 5c 24 68 48 8b 6c 24 *ff *8b 8b 74 H..H.\$hH.l$...t fffff80002867780 24 78 48 83 c4 30 41 5f 41 5e 41 5d *4b *01 5f e9 $xH..0A_A^A]K._. fffff80002867790 dc 5b 02 00 48 83 c1 48 e8 ff 85 fd *01 *c3 f8 eb .[..H..H........ fffff800028677a0 a7 ff 86 04 4b 00 00 01 be 08 4b 00 *08 *f0 ac 90 ....K.....K..... fffff800028677b0 90 90 90 90 90 90 90 90 f0 83 41 04 *00 *00 90 90 ..........A..... MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: STRIDE FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE Followup: memory_corruption --------- Debug session time: Mon Jan 31 20:46:53.298 2011 (GMT-5) System Uptime: 0 days 0:06:40.108 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 1, fffff800028be313} Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+433 ) Followup: MachineOwner --------- 0: 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: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff800028be313, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002af10e0 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiDeferredReadyThread+433 fffff800`028be313 4c8900 mov qword ptr [rax],r8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff80003bf53d0 -- (.trap 0xfffff80003bf53d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80024df680 rdx=fffff88002f67750 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800028be313 rsp=fffff80003bf5560 rbp=0000000000000002 r8=fffffa80053c0100 r9=000000000000000d r10=fffff80002849000 r11=fffff80003bf55b0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KiDeferredReadyThread+0x433: fffff800`028be313 4c8900 mov qword ptr [rax],r8 ds:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800028b8ca9 to fffff800028b9740 STACK_TEXT: fffff800`03bf5288 fffff800`028b8ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff800`03bf5290 fffff800`028b7920 : fffff880`00000000 fffff880`02f63180 fffffa80`04e21b60 fffffa80`04e21c68 : nt!KiBugCheckDispatch+0x69 fffff800`03bf53d0 fffff800`028be313 : ffffffff`fffdb610 fffff800`028c529e 00000000`00000001 fffff800`00000000 : nt!KiPageFault+0x260 fffff800`03bf5560 fffff800`028c4e67 : fffffa80`050f6820 fffffa80`053c0168 fffffa80`053c0168 00000000`00000000 : nt!KiDeferredReadyThread+0x433 fffff800`03bf55e0 fffff800`028c54be : 00000000`ee7bbabe fffff800`03bf5c58 00000000`0000642f fffff800`02a36868 : nt!KiProcessExpiredTimerList+0x157 fffff800`03bf5c30 fffff800`028c4cb7 : 00000000`37ccecc5 00000000`0000642f 00000000`37ccec33 00000000`0000002f : nt!KiTimerExpiration+0x1be fffff800`03bf5cd0 fffff800`028c1eea : fffff800`02a33e80 fffff800`02a41c40 00000000`00000000 fffff880`010ddf44 : nt!KiRetireDpcList+0x277 fffff800`03bf5d80 00000000`00000000 : fffff800`03bf6000 fffff800`03bf0000 fffff800`03bf5d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDeferredReadyThread+433 fffff800`028be313 4c8900 mov qword ptr [rax],r8 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiDeferredReadyThread+433 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+433 BUCKET_ID: X64_0xA_nt!KiDeferredReadyThread+433 Followup: MachineOwner --------- Debug session time: Mon Jan 31 21:03:44.800 2011 (GMT-5) System Uptime: 0 days 0:02:00.000 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d8941fdaf6, 0, b763ed0ef0c9ba82, 101} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d8941fdaf6, Reserved Arg2: 0000000000000000, Reserved Arg3: b763ed0ef0c9ba82, Failure type dependent information Arg4: 0000000000000101, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8000287a740 STACK_TEXT: fffff880`031805d8 00000000`00000000 : 00000000`00000109 a3a039d8`941fdaf6 00000000`00000000 b763ed0e`f0c9ba82 : nt!KeBugCheckEx STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: BAD_STACK Followup: MachineOwner --------- Debug session time: Mon Jan 31 19:29:11.432 2011 (GMT-5) System Uptime: 0 days 0:03:22.633 Loading Kernel Symbols ............................................................... ................................................................ ............ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff88002f63180, 2} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002f63180, The PRCB address of the hung processor. Arg4: 0000000000000002, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffff880`009a9768 fffff800`0283a453 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx fffff880`009a9770 fffff800`02894de7 : 00000000`00000000 fffff800`00000002 00000000`00026161 fffffa80`00101a8e : nt! ?? ::FNODOBFM::`string'+0x4dfe fffff880`009a9800 fffff800`02e02895 : fffff800`02e273c0 fffff880`009a99b0 fffff800`02e273c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`009a9900 fffff800`02888c33 : 00000000`4680bf88 fffff800`02a06e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d fffff880`009a9930 fffff800`028c1dbb : fffffa80`00000000 00000000`00000001 00000000`00000000 fffffa80`00000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`009a9ac0 fffff800`0289a63c : 00000000`00000000 fffff6fc`40004308 c3816675`e5e1f4e2 4398c2b1`e2758729 : nt!KxFlushEntireTb+0x93 fffff880`009a9b00 fffff800`028d3b79 : fffff6fc`40004308 00000000`0000003e fffff800`02a06e80 00000000`00000040 : nt!KeFlushMultipleRangeTb+0x28c fffff880`009a9bd0 fffff800`028d374f : 00000000`0001ac00 00000000`0000003f 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e fffff880`009a9c10 fffff800`02b30c06 : fffffa80`024b5b60 00000000`00000080 fffffa80`024b5040 fffff800`0286ac19 : nt!MmZeroPageThread+0x7da fffff880`009a9d40 fffff800`0286ac26 : fffff800`02a06e80 fffffa80`024b5b60 fffff800`02a14c40 4127733c`5d3b0000 : nt!PspSystemThreadStartup+0x5a fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9890 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner ---------
-
New #43
I think it was a problem with the motherboard because it stopped powering on entirely. I hooked up a different power supply and same symptoms. The fans kick on but it doesnt boot at all. That is with my ram and hard drives hooked up and without. I cant even get a POST if I unplug everything so I assume that it means my mobo is dead. Thanks for all the help.
-
New #44
If you completely remove all the ram from your motherboard and power it on, it should start beeping or lighting up error leds like crazy on the board. If that does not occur, you are likely looking at a serious motherboard hardware issue. I would contact dell at this stage, and hope a return is still an option.
-
-
New #46
Yea no ram no hd's just the cpu and it powers up the fans spin and it stays like that for like 5-10 seconds and then turns off and repeats. I get no POST or anything. Yellow light on the front of the case instead of the normal blue. And I bought this PC over 3 years ago so Im pretty sure they won't do anything for me.
-
-
New #48
Yea it seems that way is there any chance it would be the CPU instead? If there was something wrong with the CPU and I put it in a friend's computer could it damage his motherboard?
-
New #49
I have some darker spots on my CPU could it be the cause of my problems? Heres a pic.
-
New #50
odd place for it to get tinged, that cpu has been pulled out before is the only reason I could think for that happening. A replacement cpu will be fairly cheap actually. That may be your last shot at this, if it really is the motherboard replacement could be nearly as expensive as getting a mid level acer or something to just replace it with. Are any of the contact points in the socket discolored as well?
Quote
Related Discussions