The partition table does not have a valid system partition. Pt2

[polorsport]

Hi guys. I'm back breaking my pc again. Ok, so it looks like I'm running into a similar problem to what I had back in November.

However this came about in a different way. This time I was attempting a bios update via asus update utility tool. The reason for the update was that I was looking to overclock my cps (Q6600) as I just ordered an evga gtx 560 ti was suggested that I overclock to upwards of 3.4 ghz. Although the asus update tool said it was successful. I ended up with a strange small black square in the middle of my screen.

Now ever time I reboot my pc I get prompted to enter a boot dvd or repair disc.

I tried the steps given to me on the second page of this thread. "Windows 7 DVD Repair console, accept any offered repair, if it doesn't start Windows 7 then boot back in, click through to Recovery tools list to run Startup Repair up to 3 separate times".

I have disconnected all my hard drives, except for the c: aka disc 1

Disk 1 which I believe is my c: was listed as "Primary" under type in Partition 1

When I entered detail partition 1

Type: 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576

* Volume 3 C New Volume NTFS Partition 931 GB Health

 

[whs]

Post a snip of your disk management and we shall see.

 

[polorsport]

I can't take screen shots because my pc won't boot properly

 

[gregrocker]

Make sure Win7 or it's 100mb System Reserved partition (preferred) is marked Active to try Startup Repair from booted DVD/Repair CD up to 3 separate times to see if it will start: http://www.sevenforums.com/tutorials/71432-partition-mark-active.html
http://www.sevenforums.com/tutorials/105541-startup-repair-run-3-separate-times.html

You can use free Partition Wizard bootable CD to Modify>Set to Active Win7 partition or the 100mb, then from Disk tab Rebuild MBR to see if that alone will start it. Free Download Magic Partition Manager Software - Partition Wizard Online Post back a camera snap if you need to.

If your BIOS flash wasn't successful, then download it again and reflash. It is always safest and more stable to flash BIOS from Windows, so I would first repair or even reinstall if necessary to use Win7 as a platform. In the case where your BIOS flash corrupted, I would use Asus Tech Support to supervise as this may be required to qualify to RMA mobo if under warranty.

 

[whs]

OK, here is what I suspect: You may have the 100MB partition which has to be active because it contains the bootmgr. Instead, your C partition is active which is a mistake.

The way you can check that without the system is to download the bootable CD of this program. Then boot from that CD and check whether there is a 100MB partition. If yes, make that active and make C inactive. The control is in the Partition tab > Modify.

Hmm, Greg types faster than me - LOL

 

[polorsport]

Thanks for the replies guys. Sorry for not replying sooner. I'm a little under the weather, and well the medicine kicked in.

Anyway. This is going to sound really dumb, but I'm not sure which drive is my c: at the moment. Judging from my earlier posts I connected just what I thought was my c: to begin the " Partition - Mark as Active
Startup Repair" but can't get past this screen. I took a picture with my phone.

I also burned the "bootable CD of this program" tried running it but again could not get past the above screen.

 

[whs]

Getting this error from the HDD is one thing, but getting it from the CD suggests you did not change the BIOS boot sequence to boot from CD.

 

[polorsport]

How should I go about doing that. I'm at my bios screen

 

[gregrocker]

How to Boot your Computer from a Bootable CD or DVD

Or use the BIOS one-time Boot Menu which every computer has.

 

[whs]

one-time Boot Menu which every computer has

Except Sony Vaio - LOL.

 

[polorsport]

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

 

[whs]

In that case I suggest you go with the Startup Repair that Greg suggested in post #4. Maybe it can fix it.

 

[polorsport]

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/jj88/polorsport/blacksquare.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.

 

[gregrocker]

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: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[polorsport]

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

 

[polorsport]

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.

 

[polorsport]

Don't know if the attachment showed up in my last post.

 

[Jonathan_King]

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 | Ubuntu

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

 

[polorsport]

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.

 

[Jonathan_King]

I see you're running the same version as you updated to; that means that the first update simply got corrupted.