I have been having freezes and BSOD's very often for about a month. I've tried what I know and now am here for all of your help. Attached will be the logs that you need and below will be my computer specs,thanks.
Windows 7 Enterprise x64 , Original OS , Retail Version of Windows 7,Estimate age of system is over a year but not 2 years old , and I have reinstalled the OS before due to the same problems.
Remove Avast for diagnostic purposes
Enable Driver Verifier then upload the new dumps which are created
Driver Verifier - Enable and Disable
Code:aswFsBlk.SYS fffff880`043f7000 fffff880`04400000 0x00009000 0x4dc928a8 10/05/2011 15:59:36 aswMonFlt.sys fffff880`016a3000 fffff880`016dd000 0x0003a000 0x4dc928b3 10/05/2011 15:59:47 aswRdr.SYS fffff880`02cd9000 fffff880`02ce3000 0x0000a000 0x4dc928be 10/05/2011 15:59:58 aswSnx.SYS fffff880`02cef000 fffff880`02d87000 0x00098000 0x4dc929b6 10/05/2011 16:04:06 aswSP.SYS fffff880`04361000 fffff880`043ae000 0x0004d000 0x4dc929b6 10/05/2011 16:04:06 aswTdi.SYS fffff880`02c40000 fffff880`02c50000 0x00010000 0x4dc92960 10/05/2011 16:02:40Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8003d02b60, The thread currently holding on to the Pnp lock. Arg4: fffff80003c6e510 Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: fffffa8003d02b60 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LOCK_ADDRESS: fffff80002acdb60 -- (!locks fffff80002acdb60) Resource @ nt!PiEngineLock (0xfffff80002acdb60) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0xfffff80002acdb60 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff800028d6f92 to fffff800028d44da STACK_TEXT: fffff880`031c3f10 fffff800`028d6f92 : fffffa80`03d02b60 fffffa80`03d02b60 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a fffff880`031c4050 fffff800`028d97af : 00000000`000000fe fffff880`035ea390 fffff880`00000000 fffff880`02f63180 : nt!KiCommitThreadWait+0x1d2 fffff880`031c40e0 fffff880`010f8dd1 : fffffa80`03ef9100 00000000`00000000 fffff880`031c4400 fffffa80`03ef9100 : nt!KeWaitForSingleObject+0x19f fffff880`031c4180 fffff880`010fa961 : fffff880`031c4620 fffff880`031c4400 00000000`03060001 fffff880`031c41f8 : storport!RaSendIrpSynchronous+0x71 fffff880`031c41e0 fffff880`010fabde : fffff880`031c4620 00000000`00000101 00000000`00000000 fffff880`031c4620 : storport!RaidBusEnumeratorIssueSynchronousRequest+0x91 fffff880`031c42f0 fffff880`0110457d : 00000000`00000101 fffff880`00000101 00000000`00000101 00000000`00000001 : storport!RaidBusEnumeratorGenericInquiry+0x9e fffff880`031c4360 fffff880`0110462e : 00000000`00000101 fffff880`00000101 00000000`00000001 fffff880`031c44c0 : storport!RaidBusEnumeratorProbeLunZero+0x5d fffff880`031c4400 fffff880`01104764 : 00000000`00fe0001 fffffa80`00000101 00000000`00000000 00000000`00000001 : storport!RaidBusEnumeratorGetLunList+0x6e fffff880`031c4490 fffff880`01104856 : fffffa80`03db01b0 00000000`00000001 fffffa80`00004000 fffffa80`03db01b0 : storport!RaidAdapterEnumerateBus+0x94 fffff880`031c4600 fffff880`011427f2 : fffffa80`03e25c58 fffff880`010eba01 fffffa80`03d120a8 00000000`000000ca : storport!RaidAdapterRescanBus+0x76 fffff880`031c4710 fffff880`01142a00 : fffffa80`0715a560 00000000`00000000 fffffa80`03db01b0 fffffa80`0715a560 : storport!RaidAdapterQueryDeviceRelationsIrp+0xa2 fffff880`031c4750 fffff880`01142b94 : fffffa80`0715a560 fffff880`01108110 fffffa80`03db0060 fffff880`031c4880 : storport!RaidAdapterPnpIrp+0x150 fffff880`031c47b0 fffff800`02c87f5e : fffffa80`0715a560 fffffa80`05079390 fffffa80`03db0060 fffff880`02f63180 : storport!RaDriverPnpIrp+0x94 fffff880`031c47f0 fffff800`02c882ca : 00000000`00000000 fffffa80`05079390 fffff800`029c8fe0 00000000`00000000 : nt!PnpAsynchronousCall+0xce fffff880`031c4830 fffff800`02c8a617 : fffff800`02acd920 fffffa80`03d82b10 00000000`00000002 00000000`000003f8 : nt!PnpQueryDeviceRelations+0xfa fffff880`031c48f0 fffff800`02cbabfc : fffffa80`03d82b10 fffffa80`03d8003c fffffa80`03d82b10 00000000`00000002 : nt!PipEnumerateDevice+0x117 fffff880`031c4950 fffff800`02cbb208 : fffff800`02acb4e0 00000000`00000000 00000000`00000001 fffff800`02b3c248 : nt!PipProcessDevNodeTree+0x21c fffff880`031c4bc0 fffff800`029cb927 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98 fffff880`031c4c10 fffff800`028dc021 : fffff800`029cb600 fffff800`02bc8001 fffffa80`03d02b00 fffffa80`03d02b60 : nt!PnpDeviceActionWorker+0x327 fffff880`031c4cb0 fffff800`02b6e32e : 00000000`00000000 fffffa80`03d02b60 00000000`00000080 fffffa80`03cd4040 : nt!ExpWorkerThread+0x111 fffff880`031c4d40 fffff800`028c3666 : fffff880`02f63180 fffffa80`03d02b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031c4d80 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`031c42d0 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: .thread 0xfffffa8003d02b60 ; kb FOLLOWUP_IP: storport!RaSendIrpSynchronous+71 fffff880`010f8dd1 8bc3 mov eax,ebx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: storport!RaSendIrpSynchronous+71 FOLLOWUP_NAME: MachineOwner MODULE_NAME: storport IMAGE_NAME: storport.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a456 FAILURE_BUCKET_ID: X64_0x9F_storport!RaSendIrpSynchronous+71 BUCKET_ID: X64_0x9F_storport!RaSendIrpSynchronous+71 Followup: MachineOwner ---------
I've uninstalled avast and enabled driver verifier, do I need to wait till I get another blue screen or see if it is fine for 24 hours like it says in the how to? If I have to wait 24 hours I hate going without an antivirus. Your answers are appreciated,thanks.
well I guess forget that last message, not soon after i posted that i had another bsod, below are the new logs.
Your nVidia Storage Driver (nForce chipset driver) is the cause, update it
Drivers - Download NVIDIA Drivers
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {2a0, 2, 1, fffff88001087efa} Unable to load image \SystemRoot\system32\DRIVERS\nvstor64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvstor64.sys *** ERROR: Module load completed but symbols could not be loaded for nvstor64.sys Probably caused by : nvstor64.sys ( nvstor64+21efa ) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 00000000000002a0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff88001087efa, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002acd100 00000000000002a0 CURRENT_IRQL: 2 FAULTING_IP: nvstor64+21efa fffff880`01087efa 4a83a4c0a002000000 and qword ptr [rax+r8*8+2A0h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff880009b0b90 -- (.trap 0xfffff880009b0b90) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004cc70e0 rdx=0000000080000011 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88001087efa rsp=fffff880009b0d20 rbp=fffffa8004cc7000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=000000008fb65050 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nvstor64+0x21efa: fffff880`01087efa 4a83a4c0a002000000 and qword ptr [rax+r8*8+2A0h],0 ds:8ff3:00000000`000002a0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000289d2a9 to fffff8000289dd00 STACK_TEXT: fffff880`009b0a48 fffff800`0289d2a9 : 00000000`0000000a 00000000`000002a0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`009b0a50 fffff800`0289bf20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`04cc70e0 : nt!KiBugCheckDispatch+0x69 fffff880`009b0b90 fffff880`01087efa : fffffa80`06a8d901 00000000`00000000 fffffa80`058fc100 fffff880`01086f0e : nt!KiPageFault+0x260 fffff880`009b0d20 fffffa80`06a8d901 : 00000000`00000000 fffffa80`058fc100 fffff880`01086f0e fffffa80`04cc7000 : nvstor64+0x21efa fffff880`009b0d28 00000000`00000000 : fffffa80`058fc100 fffff880`01086f0e fffffa80`04cc7000 fffffa80`04cc7000 : 0xfffffa80`06a8d901 STACK_COMMAND: kb FOLLOWUP_IP: nvstor64+21efa fffff880`01087efa 4a83a4c0a002000000 and qword ptr [rax+r8*8+2A0h],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvstor64+21efa FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvstor64 IMAGE_NAME: nvstor64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a78d2cb FAILURE_BUCKET_ID: X64_0xD1_VRF_nvstor64+21efa BUCKET_ID: X64_0xD1_VRF_nvstor64+21efa Followup: MachineOwner ---------
still getting the nvstor64.sys blue screen after I updated the storage drivers, I did put Avast back on, could Avast really be the problem for something like this? I have just had a lot more luck with Avast than AVG on free antiviruses, but if I am forced to change I guess i will have to for this computer.
Run a scan of Malwarebytes and upload the newer dumps :)
Malwarebytes scan came back clean and here are the new logs. Thanks.
Nothing is been mentioned in your logs, I strongly recommend a Repair Install
well I did a repair install and no problems popped up till last night. last night I could move the mouse but couldn't like click on the start menu button. I could right click in the toolbar but couldn't click to get into task manager or any other option in the menu. Today I come home, I hit a button it comes awake but I could do nothing with keyboard or mouse, I couldn't get the numlock on or anything. There hasn't been any blue screens though yet? Any ideas?
Quote