Hi, Can someone examine my minidump file and tell me what could be causing my bluescreens. This is getting very aggrevating. I thought win 7 was suppose to be better. I have never had this many BSODs before. I have uploaded the file to skydrive. http://cid-1db60350544eba43.skydrive.live.com/browse.aspx/.Public?uc=1

The problem u have is driver crash . u have the minudump file analyse: ******************************************************************************* * * * 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: fffffa800acc4050, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800cb02a10, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800cb02a10 DEVICE_OBJECT: fffffa800aac7790 DRIVER_OBJECT: fffffa8009489e70 IMAGE_NAME: disk.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d MODULE_NAME: disk FAULTING_MODULE: fffff88000dd5000 disk CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800030f7e23 to fffff80003088f00 STACK_TEXT: fffff800`00b9c4c8 fffff800`030f7e23 : 00000000`0000009f 00000000`00000003 fffffa80`0acc4050 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`03094fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`00b9c570 fffff800`03094326 : fffff800`03237700 00000000`003170d9 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`03094e7e : 00000075`b0310d11 fffff800`00b9cc58 00000000`003170d9 fffff800`03205da8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`03094697 : 00000021`ca28b4c1 00000021`003170d9 00000021`ca28b4f8 00000000`000000d9 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`030916fa : fffff800`03201e80 fffff800`0320fc40 00000000`00000000 fffff880`048044d0 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a I want to be a MVP! ______________________________ Computer Technician

Ok, thanks for the info. Is there any way to tell which driver?

Sometimes hardware faults can mask and make it look like its a software driver is at fault when its not. I would run memtest86+ and run it several times, not just once. http://www.memtest.org/Here's a more complete analysis of your minidumpMicrosoft (R) Windows Debugger Version 6.11.0001.404 X86Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [G:\020310-68999-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available WARNING: Whitespace at end of path elementSymbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`03254e50Debug session time: Wed Feb 3 07:33:10.703 2010 (GMT-6)System Uptime: 0 days 14:02:26.717Loading Kernel Symbols......................................................................................................................................................................Loading User SymbolsLoading unloaded module list............******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa800acc4050, fffff80000b9c518, fffffa800cb02a10} Probably caused by : disk.sys 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 timeArg2: fffffa800acc4050, Physical Device Object of the stackArg3: fffff80000b9c518, Functional Device Object of the stackArg4: fffffa800cb02a10, The blocked IRP Debugging Details:------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800cb02a10 DEVICE_OBJECT: fffffa800aac7790 DRIVER_OBJECT: fffffa8009489e70 IMAGE_NAME: disk.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d MODULE_NAME: disk FAULTING_MODULE: fffff88000dd5000 disk CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800030f7e23 to fffff80003088f00 STACK_TEXT: fffff800`00b9c4c8 fffff800`030f7e23 : 00000000`0000009f 00000000`00000003 fffffa80`0acc4050 fffff800`00b9c518 : nt!KeBugCheckExfffff800`00b9c4d0 fffff800`03094fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330fffff800`00b9c570 fffff800`03094326 : fffff800`03237700 00000000`003170d9 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66fffff800`00b9c5e0 fffff800`03094e7e : 00000075`b0310d11 fffff800`00b9cc58 00000000`003170d9 fffff800`03205da8 : nt!KiProcessExpiredTimerList+0xc6fffff800`00b9cc30 fffff800`03094697 : 00000021`ca28b4c1 00000021`003170d9 00000021`ca28b4f8 00000000`000000d9 : nt!KiTimerExpiration+0x1befffff800`00b9ccd0 fffff800`030916fa : fffff800`03201e80 fffff800`0320fc40 00000000`00000000 fffff880`048044d0 : nt!KiRetireDpcList+0x277fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_disk.sys BUCKET_ID: X64_0x9F_IMAGE_disk.sys Followup: MachineOwner--------- 0: kd> !drvobj fffffa8009489e70 ffffff80003237790: Unable to get value of ObpRootDirectoryObjectfffff80003237790: Unable to get value of ObpRootDirectoryObjectDriver object (fffffa8009489e70) is for: \Driver\DiskDriver Extension List: (id , addr) Device Object list:fffffa800b16b060: Could not read device object DriverEntry: fffff88000de706c disk!GsDriverEntryDriverStartIo: 00000000 DriverUnload: fffff880018a8c90 CLASSPNP!ClassUnloadAddDevice: 00000000 Dispatch routines:[00] IRP_MJ_CREATE fffff88001887700 CLASSPNP!ClassGlobalDispatch[01] IRP_MJ_CREATE_NAMED_PIPE fffff8000306f65c nt!IopInvalidDeviceRequest[02] IRP_MJ_CLOSE fffff88001887700 CLASSPNP!ClassGlobalDispatch[03] IRP_MJ_READ fffff88001887700 CLASSPNP!ClassGlobalDispatch[04] IRP_MJ_WRITE fffff88001887700 CLASSPNP!ClassGlobalDispatch[05] IRP_MJ_QUERY_INFORMATION fffff8000306f65c nt!IopInvalidDeviceRequest[06] IRP_MJ_SET_INFORMATION fffff8000306f65c nt!IopInvalidDeviceRequest[07] IRP_MJ_QUERY_EA fffff8000306f65c nt!IopInvalidDeviceRequest[08] IRP_MJ_SET_EA fffff8000306f65c nt!IopInvalidDeviceRequest[09] IRP_MJ_FLUSH_BUFFERS fffff88001887700 CLASSPNP!ClassGlobalDispatch[0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff8000306f65c nt!IopInvalidDeviceRequest[0b] IRP_MJ_SET_VOLUME_INFORMATION fffff8000306f65c nt!IopInvalidDeviceRequest[0c] IRP_MJ_DIRECTORY_CONTROL fffff8000306f65c nt!IopInvalidDeviceRequest[0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff8000306f65c nt!IopInvalidDeviceRequest[0e] IRP_MJ_DEVICE_CONTROL fffff88001887700 CLASSPNP!ClassGlobalDispatch[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff88001887700 CLASSPNP!ClassGlobalDispatch[10] IRP_MJ_SHUTDOWN fffff88001887700 CLASSPNP!ClassGlobalDispatch[11] IRP_MJ_LOCK_CONTROL fffff8000306f65c nt!IopInvalidDeviceRequest[12] IRP_MJ_CLEANUP fffff8000306f65c nt!IopInvalidDeviceRequest[13] IRP_MJ_CREATE_MAILSLOT fffff8000306f65c nt!IopInvalidDeviceRequest[14] IRP_MJ_QUERY_SECURITY fffff8000306f65c nt!IopInvalidDeviceRequest[15] IRP_MJ_SET_SECURITY fffff8000306f65c nt!IopInvalidDeviceRequest[16] IRP_MJ_POWER fffff88001887700 CLASSPNP!ClassGlobalDispatch[17] IRP_MJ_SYSTEM_CONTROL fffff88001887700 CLASSPNP!ClassGlobalDispatch[18] IRP_MJ_DEVICE_CHANGE fffff8000306f65c nt!IopInvalidDeviceRequest[19] IRP_MJ_QUERY_QUOTA fffff8000306f65c nt!IopInvalidDeviceRequest[1a] IRP_MJ_SET_QUOTA fffff8000306f65c nt!IopInvalidDeviceRequest[1b] IRP_MJ_PNP fffff88001887700 CLASSPNP!ClassGlobalDispatch 0: kd> !devobj fffffa800aac7790 ffffff80003237790: Unable to get value of ObpRootDirectoryObjectDevice object (fffffa800aac7790) is for: InfoMask field not found for _OBJECT_HEADER at fffffa800aac7760 \Driver\Disk DriverObject fffffa8009489e70Current Irp 00000000 RefCount 0 Type 00000007 Flags 01002050Vpb fffffa800aac76d0 DevExt fffffa800aac78e0 DevObjExt fffffa800aac7f88 AttachedDevice (Upper) fffffa800ab78b90 \Driver\partmgrDevice queue is not busy.0: kd> lmvm diskstart end module namefffff880`00dd5000 fffff880`00deb000 disk (pdb symbols) c:\symbols\disk.pdb\36B97AD42B4D4B96BDB7534FBA7CD76C2\disk.pdb Loaded symbol image file: disk.sys Mapped memory image file: c:\symbols\disk.sys\4A5BC11D16000\disk.sys Image path: disk.sys Image name: disk.sys Timestamp: Mon Jul 13 18:19:57 2009 (4A5BC11D) CheckSum: 0001FF1D ImageSize: 00016000 File version: 6.1.7600.16385 Product version: 6.1.7600.16385 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0000.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: disk.sys OriginalFilename: disk.sys ProductVersion: 6.1.7600.16385 FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255) FileDescription: PnP Disk Driver LegalCopyright: © Microsoft Corporation. All rights reserved.MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]

Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services). The system goes to BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are). To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: Microsoft - Help and Support If you are outside the US please see Microsoft Worldwide Home for regional support phone numbers. Meantime we can try some available steps as a general troubleshoot. 1. Please remove the antivirus and run the system with a period. If the issue does not occur, mainly focus on antivirus settings and compatibility. 2. Disable Automatic Restart and see detail information on the blue screen. 1).Click Start, in the Start Search box enter sysdm.cpl. 2).Click the tab Advanced. Under Startup and Recovery, click the Settings button. 3). Uncheck “Automatically restart”. 4). On the drop-down menu “Write debugging information”, choose “Small memory dump”. 5). Click OK. When Blue Screen displays, try to find which *.sys file is cause the blue screen. Usually it is listed in the bottom part.Arthur Xie - MSFT