Hi guys. I am having major fu**ing issues my pc. The problem is if I turn off the pc for hours when I go to bed or go or (whatever ever else) and turn it back on it will lock up all together in a matter of 3-5 minutes. And every time I reboot my pc by holding the power to turn it off (that's how bad it gets) it will repeat that a few times until I get a system crash (BSOD) that creates a dump file. I have ran every scan and diagnostic that I could find and no reports come back bad for my hardware and I KNOW it's not the software considering this happens with a fresh format and no software installed at all except the windows 7 updates. When the pc finally stops the locking up and system crash it will stay on all night and as much as anyone could want. So that makes no sense to me because if it's hardware malfunction then why work at any point? I am on windows 7 (obviously) a quadcore 2.20 ghz, a nvidia gt 240, 5 gbs of ram (no idea why it's 5 that's how the pc came built from the place I got it) and yes I have updated all my drivers I could. I am pretty sure m8530f is my mother board model if someone needs that. Someone I am talking to thinks this issue, especially the bsod, might be an issue with win7 and my mother board, no idea. I will post this big wall of text with the information from the system crash dump file. I was gonna give a link but the forum doesn't allow me to do so with out 20 post. Sorry for the flood in advance but I wanna get this issue figured out asap instead of spamming post. So if anyone can tell me what's wrong or what to do I will be so damn grateful. I hope someone will be able to help. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\060112-22198-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\Symbols*(had to erase the link) Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504 Machine Name: Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`0305f670 Debug session time: Fri Jun 1 17:01:25.849 2012 (UTC - 4:00) System Uptime: 0 days 0:04:02.504 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff80000b9c120, 0, 0, fffff80002e9661b} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+6b ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff80000b9c120 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff80002e9661b Debugging Details: ------------------ CONTEXT: fffff80000b9c120 -- (.cxr 0xfffff80000b9c120) rax=000000000001a3a3 rbx=0000000000000000 rcx=fffffa800617d060 rdx=fffffa80063af078 rsi=fffff80003433460 rdi=0000000000000001 rip=fffff80002e9661b rsp=fffff80000b9cb08 rbp=fffff80000b9cb88 r8=0000000000000000 r9=000000001a62123e r10=00000000000157d4 r11=0000000000000000 r12=fffffa80063af050 r13=fffffa80063afd00 r14=fffffa80063af000 r15=0000000000000000 iopl=0 nv up di pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210046 nt!KiInterruptDispatchNoLock+0x6b: fffff800`02e9661b 0f2945f0 movaps xmmword ptr [rbp-10h],xmm0 ss:0018:fffff800`00b9cb78=00000000000000000000000000000000 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff80002e9661b STACK_TEXT: fffff800`00b9cb08 00000000`00000010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x6b 00000000`00000018 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x10 FOLLOWUP_IP: nt!KiInterruptDispatchNoLock+6b fffff800`02e9661b 0f2945f0 movaps xmmword ptr [rbp-10h],xmm0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiInterruptDispatchNoLock+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c STACK_COMMAND: .cxr 0xfffff80000b9c120 ; kb FAILURE_BUCKET_ID: X64_0x3D_nt!KiInterruptDispatchNoLock+6b BUCKET_ID: X64_0x3D_nt!KiInterruptDispatchNoLock+6b Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff80000b9c120 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff80002e9661b Debugging Details: ------------------ CONTEXT: fffff80000b9c120 -- (.cxr 0xfffff80000b9c120) rax=000000000001a3a3 rbx=0000000000000000 rcx=fffffa800617d060 rdx=fffffa80063af078 rsi=fffff80003433460 rdi=0000000000000001 rip=fffff80002e9661b rsp=fffff80000b9cb08 rbp=fffff80000b9cb88 r8=0000000000000000 r9=000000001a62123e r10=00000000000157d4 r11=0000000000000000 r12=fffffa80063af050 r13=fffffa80063afd00 r14=fffffa80063af000 r15=0000000000000000 iopl=0 nv up di pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210046 nt!KiInterruptDispatchNoLock+0x6b: fffff800`02e9661b 0f2945f0 movaps xmmword ptr [rbp-10h],xmm0 ss:0018:fffff800`00b9cb78=00000000000000000000000000000000 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff80002e9661b STACK_TEXT: fffff800`00b9cb08 00000000`00000010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x6b 00000000`00000018 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x10 FOLLOWUP_IP: nt!KiInterruptDispatchNoLock+6b fffff800`02e9661b 0f2945f0 movaps xmmword ptr [rbp-10h],xmm0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiInterruptDispatchNoLock+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c STACK_COMMAND: .cxr 0xfffff80000b9c120 ; kb FAILURE_BUCKET_ID: X64_0x3D_nt!KiInterruptDispatchNoLock+6b BUCKET_ID: X64_0x3D_nt!KiInterruptDispatchNoLock+6b Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff80000b9c120 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff80002e9661b Debugging Details: ------------------ CONTEXT: fffff80000b9c120 -- (.cxr 0xfffff80000b9c120) rax=000000000001a3a3 rbx=0000000000000000 rcx=fffffa800617d060 rdx=fffffa80063af078 rsi=fffff80003433460 rdi=0000000000000001 rip=fffff80002e9661b rsp=fffff80000b9cb08 rbp=fffff80000b9cb88 r8=0000000000000000 r9=000000001a62123e r10=00000000000157d4 r11=0000000000000000 r12=fffffa80063af050 r13=fffffa80063afd00 r14=fffffa80063af000 r15=0000000000000000 iopl=0 nv up di pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210046 nt!KiInterruptDispatchNoLock+0x6b: fffff800`02e9661b 0f2945f0 movaps xmmword ptr [rbp-10h],xmm0 ss:0018:fffff800`00b9cb78=00000000000000000000000000000000 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff80002e9661b STACK_TEXT: fffff800`00b9cb08 00000000`00000010 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x6b 00000000`00000018 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x10 FOLLOWUP_IP: nt!KiInterruptDispatchNoLock+6b fffff800`02e9661b 0f2945f0 movaps xmmword ptr [rbp-10h],xmm0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiInterruptDispatchNoLock+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f76721c STACK_COMMAND: .cxr 0xfffff80000b9c120 ; kb FAILURE_BUCKET_ID: X64_0x3D_nt!KiInterruptDispatchNoLock+6b BUCKET_ID: X64_0x3D_nt!KiInterruptDispatchNoLock+6b Followup: MachineOwner ---------
hi Kolz, my compliments for providing sufficient information. you documented the software issue very thoroughly. unfortunately my knowledge of such matters is limited. but i suspect a hardware issue. something goes wrong after a cold boot ONLY.. could be a fault in atx powersupply or ram, as they warm up to working temperatures. that could be checked by trying another powersupply and/or booting with minimal ram installed, and trying different banks for that. have you tried to put the machine on stand-by when you leave? instead of switching off? does that make a difference? regards, nodnar
I never leave my pc on if I go away for any reasons. I figure if it's not doing anything then it doesn't need to take any kind of power at all. I am definitely going with hardware related issues but all of my test come back good so I am not finding the source of the problem. I was/am hoping that sysem crash info will lead me to that answer because I am out of ideas and don't spare parts to really test the theories out.
Yep it worked before for a long time then out of no where this problem appeared some where last year and been around ever since. I will try that link out.
That does sound close to what I got have. After a while of the lock ups and especially a system crash it will work. Such an annoyance but I will give that idea try out too. Might as well try everything.