New
#11
Ok, I am running the minitool partition wizard home edition.
I see partion disk 1. NTFS status acvtive type primary. No sign of any additional partition
Ok, I am running the minitool partition wizard home edition.
I see partion disk 1. NTFS status acvtive type primary. No sign of any additional partition
In that case I suggest you go with the Startup Repair that Greg suggested in post #4. Maybe it can fix it.
Some progress. After starting the Startup Repair that Greg suggested. I am able to boot normally....however there are still some issues.
1. There is a small black box that doesn't seem to go away once I turned on my computer. Stays on my browser. Here is a screen shot.
http://i270.photobucket.com/albums/j...lacksquare.png
2. When I went to reboot my pc after an extended shut down process maybe 2-3 minutes. I was greeted by a blue screen. I had someone talking to me so I didn't see everything that is said but did notice a disc failure. I currently still only have 1 drive (c:) connected.
1) As you say its a browser problem, does it happen with IE?
2) Upload the bluescreen bugcheck file using this tool, zip it up and post in Crashes forum here for expert analysis: https://www.sevenforums.com/crashes-d...tructions.html
Definitely not a browser problem. Strangely enough the black square turned grey after an error message. The got the blue screen hard drive power error. Now the square is gone.
But the blue screen keeps coming up before the BSOD app is finished running.
Some kind of hard drive power state error. Trying to finish running the app in safe mode.
Damn blacksquare is back
Last edited by polorsport; 16 Feb 2011 at 22:53.
Still have that damn black square. The attachment was only able to complete in safe mode. Not sure if it makes a difference.
I can't believe all these problems. Just 24 hours ago everything was working fine. Still trying to get performance monitor to finish. But, my pc keeps crashing.
Don't know if the attachment showed up in my last post.
The BSOD was caused by ACPI on the system; for anyone who doesn't know, that's a power management feature. Check out this thread I worked this very morning: Driver Power State Failure BSOD - Tech Support Forum
While I haven't actually solved that thread yet, I suspected it's a BIOS issue, before reading this thread. How convenient that this issue should arise after a known BIOS issue.
As far as BSOD analysis goes, my job is done. I hate to say, but there is nothing more we are going to get out of analyzing the BSODs, as we already know it's a BIOS issue.
To solve the problem, I suggest that you try flashing the BIOS again; for the sake of efficiency, we might as well try the earlier BIOS.
Create a Linux Live CD, such as Ubuntu (instructions in link), and then run the 1204 version.
Download | UbuntuCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Documents and Settings\JK\Desktop\Windows_NT6_BSOD_jcgriff2\Windows_NT6_BSOD_jcgriff2\021611-32370-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730? Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`0303fe50 Debug session time: Wed Feb 16 19:56:09.347 2011 (GMT-5) System Uptime: 0 days 0:23:10.188 Loading Kernel Symbols ............................................................... ................................................................ .................................. Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa80073e97e0, fffff80000ba2748, fffffa8007950800} Probably caused by : ACPI.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 time Arg2: fffffa80073e97e0, Physical Device Object of the stack Arg3: fffff80000ba2748, Functional Device Object of the stack Arg4: fffffa8007950800, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa8007950800 DEVICE_OBJECT: fffffa80073e97e0 DRIVER_OBJECT: fffffa80069bcc30 IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc106 MODULE_NAME: ACPI FAULTING_MODULE: fffff88000ec4000 ACPI CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: aaCenter.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002ee1273 to fffff80002e72740 STACK_TEXT: fffff800`00ba26f8 fffff800`02ee1273 : 00000000`0000009f 00000000`00000003 fffffa80`073e97e0 fffff800`00ba2748 : nt!KeBugCheckEx fffff800`00ba2700 fffff800`02e7e29e : fffff800`00ba2830 fffff800`00ba2830 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0 fffff800`00ba27a0 fffff800`02e7ddd6 : fffff800`03022700 00000000`00015c1a 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00ba2810 fffff800`02e7e4be : 00000003`3c9dfbf4 fffff800`00ba2e88 00000000`00015c1a fffff800`02fef5c8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00ba2e60 fffff800`02e7dcb7 : fffff800`02fecec1 fffffa80`00015c1a fffffa80`083aaa28 00000000`0000001a : nt!KiTimerExpiration+0x1be fffff800`00ba2f00 fffff800`02e78865 : 00000000`00000000 fffffa80`09a64b60 00000000`00000000 fffff880`0fe89684 : nt!KiRetireDpcList+0x277 fffff800`00ba2fb0 fffff800`02e7867c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 fffff880`080f72a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_ACPI.sys BUCKET_ID: X64_0x9F_IMAGE_ACPI.sys Followup: MachineOwner --------- 0: kd> !sysinfo machineid Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=1911] BiosVendor = Phoenix Technologies, LTD BiosVersion = ASUS P5N-D ACPI BIOS Revision 1401 BiosReleaseDate = 06/21/2010 SystemManufacturer = System manufacturer SystemProductName = System Product Name SystemFamily = SystemVersion = System Version SystemSKU = BaseBoardManufacturer = ASUSTeK Computer INC. BaseBoardProduct = P5N-D BaseBoardVersion = 1.XX
Ok, I seem to have everything working now. I did a series of system restores, and re flashed my bios. No blue screens from these actions. And I was able to do a perfmon/report.
Now my last remaining issue is the overclocking. Following various youtube videos / tomshardware guide I can't seen to change anything in my bios without getting a frozen blank screen. I was following guides with virtually the same exact setup as I have.
I see you're running the same version as you updated to; that means that the first update simply got corrupted.