New Posts  All Forums:Forum Nav:

Need Help!!! - Page 4

post #31 of 71
Thread Starter 
http://www.mediafire.com/?62gvav2wdp08cvx

There you go smile.gif
post #32 of 71
The MEMORY.DMP you've attached is not verifier enabled, so not much to go on other than the bugcheck. The bugcheck is 9F: A device driver is in an invalid or inconsistent power state from either shutdown or going into or returning from hibernate or standby modes.

With this being said, it's likely a third party driver, but we don't because we need the verifier enabled dump. If during the time verifier was enabled you BSOD'd, it would have generated a verifier enabled dump which should be under C:/Windows/Minidump with the LATEST time & date. If it wasn't, that's why I suggested it may be MEMORY.DMP, but it's not.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\SymCache*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.17803.amd64fre.win7sp1_gdr.120330-1504
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03448670
Debug session time: Tue May 15 02:12:25.927 2012 (UTC - 4:00)
System Uptime: 0 days 7:00:47.801
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006792e30, fffff80000b9c3d8, fffff98066178dc0}

Probably caused by : ntkrnlmp.exe

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006792e30, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffff98066178dc0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa80083a76d0

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: 0000000000000000 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c388 fffff800`032ed702 : 00000000`0000009f 00000000`00000003 fffffa80`06792e30 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`0328de4c : fffff800`00b9c4f0 fffff800`00b9c4f0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
fffff800`00b9c430 fffff800`0328dce6 : fffffa80`0be19ac0 fffffa80`0be19ac0 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`0328dbce : 0000003a`c8dcd920 fffff800`00b9cb18 00000000`0018b206 fffff800`033f8348 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`0328d9b7 : 00000013`796f2fc5 00000013`0018b206 00000013`796f2fb0 00000000`00000006 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`0327aeca : fffff800`033f5e80 fffff800`03403cc0 00000000`00000000 fffff880`051b1480 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_VRF_3_IMAGE_ntkrnlmp.exe

BUCKET_ID:  X64_0x9F_VRF_3_IMAGE_ntkrnlmp.exe

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

post #33 of 71
Thread Starter 
ok dude want me to run verifier again for 24 hours ... and see if that would work ?
post #34 of 71
Yes, and to make this easier, delete all of your previous crash dump files. That way, when you do crash with verifier enabled, you should only have one crash dump, and that should be the verifier enabled one smile.gif
post #35 of 71
Thread Starter 
Ok i enabled it again ... i hope it works this time frown.gif
post #36 of 71
Keep me updated.
post #37 of 71
Thread Starter 
Of course smile.gif
post #38 of 71
Thread Starter 
Ok i left my pc on till now and it didnt crash so i dont have any dumb files ... is it now time to check the hardware frown.gif
post #39 of 71
Yes, now it's time for hardware diagnostics.

Before we begin, double check that NO hardware is overclocked. Also realize that hardware changes everyday. Just because something was stable and worked yesterday doesn't mean it will today or tomorrow.

First, we'll run a Memtest. Don't settle for anything less than 7-8 passes, this will take MULTIPLE hours. Run Memtest before bed or before work, whichever you prefer when you're NOT at the computer.

After Memtest, let me know what the results were so we can move on.
post #40 of 71
Thread Starter 
Ok so before i go to sleep i left the test on and when i woke up it was on pass 6 and it had 0 errors and it said it was up running for 7 hours. So then i went to school and when i came back the test was done and 2nd test had start and it was on pass 5 basically the same test restarted its self and the other one was done and it said no errors so i guess my ram is fine smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows