cluberti

The 0x7B stop error is "INACCESSIBLE_BOOT_DEVICE". Not familiar with that Pavilion brand - does the HDD attach via SATA, perhaps? If so, you're gonna need to integrate chipset drivers before you can install. Note HP tells you how to do this (link previous) on the site for support for that laptop.

Each core is more efficient, yes - but with 2 and 4 cores on a die, you still need more juice overall.

Your tinfoil hat, sir:

Could you actually post the contents of the error message? The WHEA errors are usually corrected hardware check failures, so the logs would be useful. You may be correct, but more data would be nice to verify.

It's just a graph - set it to whatever # will allow you to see the counters. Also note though, those counter numbers are available in the boxes under the graph when one of the values are highlighted.

That's an odd error code: # as an HRESULT: Severity: FAILURE (1), FACILITY_PLA (0x30), Code 0x1 # for hex 0x1 / decimal 1 ERROR_INVALID_FUNCTION winerror.h # Incorrect function. # 1 matches found for "0x80300001"

True - svchost.exe is just a generic host process that can run almost any binary as a service if it's written to do so. That's why these are almost always malware/viruses - great place for non-Microsoft code to hide, inside a Microsoft binary and running all the time as a service.

Working on it - should be ready soon.

What you ask is so much deeper and far-reaching than I think you understand. Pick up the book "Windows Internals, 4th Edition" and read chapters 2, 4, 7, and 11 (well, read the whole book, of course, but these are the "memory" chapters). That's 262 pages of nothing but memory management and structures . Basically, use process explorer and performance monitor, not task manager. What you see is not entirely accurate, and does not mean what you think it means. If you really want to get deep, even though it's not entirely an accurate measurement, see this thread I posted awhile back.

# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x3701 # for hex 0x3701 / decimal 14081 ERROR_SXS_ASSEMBLY_MISSING winerror.h # The referenced assembly could not be found. # 1 matches found for "0x80073701" Sounds like something's missing in WinSXS that Windows or an app expects to be there. What exactly did you do to your install?

Unfortunately this is not a kernel or complete memory dump, so the IRP structure that would show the driver path is missing. However, most mountmgr crashes are either (as crahak pointed out) a faulty hard disk, or, more commonly in this case, a faulty chipset or disk driver. I would update whatever chipset drivers you have installed, or any RAID controller drivers (if that's what's in use). Also, in some occasions, I have seen Symantec Antivirus' symtdi.sys driver cause this bugcheck as well (again, if I had the IRP stack, I would be able to gather more info than just a minidump), so if you have Symantec Antivirus or Norton Antivirus installed, removal as a test would also be a good thing to try. kd> !thread GetPointerFromAddress: unable to read from 8055f534 THREAD 82bc58b8 Cid 0004.0018 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0 IRP List: Unable to read nt!_IRP @ 823453b8 Not impersonating GetUlongFromAddress: unable to read from 8055f544 Owning Process 82bc87c0 Image: System Attached Process N/A Image: N/A ffdf0000: Unable to get shared data Wait Start TickCount 22479709 Context Switch Count 338060 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Start Address nt!ExpWorkerThread (0x804e4729) Stack Init f7c09000 Current f7c08990 Base f7c09000 Limit f7c06000 Call 0 Priority 13 BasePriority 13 PriorityDecrement 0 DecrementCount 16 ChildEBP RetAddr Args to Child f7c08860 80522325 0000007a c03de008 c000000e nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo]) f7c08888 804fae18 8149f010 c03de008 f7802000 nt!MiWaitForInPageComplete+0x1c5 (FPO: [Non-Fpo]) f7c08900 804ec48a 2dd56860 f7802000 c03de008 nt!MiDispatchFault+0x2a3 (FPO: [Non-Fpo]) f7c08950 804e1ff1 00000000 f7802000 00000000 nt!MmAccessFault+0x5bc (FPO: [Non-Fpo]) f7c08950 f7801fff 00000000 f7802000 00000000 nt!KiTrap0E+0xcc (FPO: [0,0] TrapFrame @ f7c08968) f7c089dc f7805de7 82b52f40 823453b8 00000103 MountMgr!MountMgrQueryDosVolumePath+0x3 (FPO: [Non-Fpo]) f7c089fc 804e3d77 82345428 82b52f5c 00000200 MountMgr!MountMgrDeviceControl+0xb7 (FPO: [Non-Fpo]) f7c08a0c 8052e753 000000c8 81ee7430 e2cd05e8 nt!IopfCallDriver+0x31 (FPO: [0,0,0]) f7c08c5c 805e7940 82b77e30 e2cd05e8 6e446f49 nt!IoVolumeDeviceToDosName+0x155 (FPO: [Non-Fpo]) f7c08cc0 80615429 81ee7430 00000001 00000001 nt!IopQueryNameInternal+0x92 (FPO: [Non-Fpo]) f7c08cf0 80519af7 81ee7430 f7c08d28 80556d10 nt!IoQueryFileDosDeviceName+0x2e (FPO: [Non-Fpo]) f7c08d2c 804e54ad 82bc81f0 80561b40 82bc58b8 nt!CcWriteBehind+0x12e (FPO: [Non-Fpo]) f7c08d74 804e47fe 82bc81f0 00000000 82bc58b8 nt!CcWorkerThread+0x126 (FPO: [Non-Fpo]) f7c08dac 8057dfed 82bc81f0 00000000 00000000 nt!ExpWorkerThread+0x100 (FPO: [Non-Fpo]) f7c08ddc 804fa477 804e4729 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo]) 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

http://support.microsoft.com/kb/297684

The desktop UI will have the same type of layout (desktop, toolbar, etc), but will no longer have a sidebar (gadgets float free), glass (Aero) will have more transparency and configurability, and the toolbar will be *vastly* different (dubbed the "superbar"), and it's really quite a good UI.

Too late, you did. If you want to police almost 1 million posts for questionable activity, and also wade through the legal waters (in multiple countries) on whether something does, or does not, violate a EULA held by some entity in all countries involved, then be my guest.MSFN does not promote illegal activity or warez, but we have to be cognizant that a lot of activity can be illegal or legal, depending on the country, the product, the vendor, and even the desired intent. We only delete things that are obviously not legal and would be specifically prohibited, while taking a case-by-case view of everything else. To that end, getting a computer from an OEM (any OEM) that does not contain either a hologram disc with a COA, or at least a recovery partition and a COA and PID stating such, is indeed illegal in ALL countries where Microsoft software is distributed. Which is why I responded as such. Also, you are the same person who posted the OEM-only Fiji version of Media Center, then complained about being reported. Consider yourself banned as per forum rules. While your opinion is your opinion, I can speak for all the mods when I say we do not appreciate being told how to run these forums in this manner. This isn't retaliation, and this goes for everyone - we're the mods, but we can't police everything. If you think something on these forums should be reported, please report it. This isn't our full-time job, please respect that. Thread closed.

See if this KB helps you.

This information IS available, but only if you have access to it. For example, I have access to MSOpen and the OCE, most people don't. Which is why when I talk about things like OfficeReady, people can't find information about it. Its the same idea. Its out there but sometimes you need an account to see it. No, I mean, I have access to an Open Business agreement EULA and PUM. However, it doesn't touch on server OSes in either way, just client licenses. Seems like the question would have been answered had it not been omitted. I guess it's fair to assume that if it doesn't say specifically that you need an OEM or retail license for Server, that you do not, but making assumptions with a EULA or PUM can be dangerous (probably why the question got asked in the first place).

AdjustTokenPrivileges From MSDN:

This almost reminds me of what the Win9x control panels were like - I must say, I don't dislike the Vista/Win7 control panel, and I do find it easy to use, but some people do not. A return to the Win9x-style control panel might be useful.

Then that would be a change from the last documentation I saw (admittedly in the 2003 timeframe, but still). Why is this stuff not more readily public? I guess I'll have to answer that one on my own.

That article is so vague I don't really know what they're doing to compare performance between a pre-beta, debug-build (unoptimized) OS code versus retail-build (optimized, unchecked) code. Basically they say it's the same because the process and thread count is similar, and skype crashes? That's the article? Come on, better journalism please. I expect no less from dailytech, but it's still mostly trash.

Right - some group changes do not, but security access changes (RDP isn't a security acl, it's a right) do.

How did you think MSFN tracked your user/pass? Magic? What is happening is that the cookie used to store my user/pass is expiring (as seen in a network trace), thus I need to log on again so MSFN can write a new cookie with my user/pass to my temporary internet files.Yes, clearing your cache of cookies will cause the issue as well, but that is *expected*.

If you have a VL agreement, it requires the machine underneath have an OEM or retail license before you can "upgrade" it to a VL install. This is true for Server and Client OSes. If you got a "bare" server with no OS, you need to either purchase an OEM license or a retail license copy of Server 2008 for that hardware before you can install the VL licensed copy on that machine. This is true for ALL volume license agreements.

We shall see - Server 2008 R2 (i.e. the "Server" branch of Win7) is slated x64 only, so again, we shall see.

OK, I spoke too soon. It's happening again at roughly 4 hour intervals. Very, very odd.