New
#21
Registrar Registry Manager and PowerISO were installed after BSOD was occurring, but I will uninstall them.
Attached are the dump files u requested. I used the SFtools to just Grab All again.
Registrar Registry Manager and PowerISO were installed after BSOD was occurring, but I will uninstall them.
Attached are the dump files u requested. I used the SFtools to just Grab All again.
Tom,
As I wrote to Dave, I tried to uninstall Net framework 4 and ensure Net framework 3.5.1 was in place (mainly since SFC was telling me the missing/corrupt files seemed to Net framework files) . That's when I had trouble uninstalling the updates via control panel>Add/Remove>Uninstall Updates. I was also having issues uninstalling SP1/KB976932 as well by that method. I think I finally uninstalled SP1 thru cmd. I then tried to reinstall SP1 using the standalone download (windows6.1-KB976932-X86), which was also having trouble. It seem to resolve itself somehow, because Windows Update kicked in and windows update gave me the option to download and install SP1/KB976932, which I did. It appears as if SP1 was installed successfully, but maybe not?
Here's the log u requested:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>dir C:\Windows\servicing\Packages\Package_for_KB976933~31bf3
856ad364e35~x86~~6.1.7601.17514.*
Volume in drive C is Win7
Volume Serial Number is 1E1A-5243
Directory of C:\Windows\servicing\Packages
11/20/2010 10:18 AM 7,716 Package_for_KB976933~31bf3856ad364e35~x86
~~6.1.7601.17514.cat
11/20/2010 10:06 AM 9,904 Package_for_KB976933~31bf3856ad364e35~x86
~~6.1.7601.17514.mum
2 File(s) 17,620 bytes
0 Dir(s) 89,755,484,160 bytes free
C:\Windows\system32>
Hi NeoJediX,
You're right to question it as your system is a right mess at the moment! The command prompt header shows that you don't have SP1 installed:
Code:Microsoft Windows [Version 6.1.7600]
Windows 7 RTM = 6.1.7600
Windows 7 SP1 = 6.1.7601
But looking at the package name, we can see it's an SP1 package:
Package_for_KB976933~31bf3856ad364e35~x86~~6.1.7601.17514.cat
When updates get partially installed it leaves one hell of a mess to tidy up, so I would highly recommend you cut your losses and do a repair install :)
Repair Install
Tom
Tom,
Well, I'll give it a whirl. Question: Windows 7 Starter came pre-installed on this here Asus EeePC 1001p. There is no disc or download from the list that has Win 7 Starter as an option. Which or what shall I use?
Also, I'm not sure if u had a chance to read the earlier post, but I tried a fresh install of Windows 7 Thin PC on a new partition. And guess what? As soon as I install the Intel graphics driver...BSOD.
Anyway, I'm willing to try Repair Install if u suggest which one to try...
Thanks so much.
I think you should try this one as a test ..... ASUS - Eee- Eee PC 1015CX
Attachment 273395
If it behaves the same, better you ask for a warranty replacement. Coz this is onboard graphics adapter, and your windows license should be OEM.
That driver wouldn't even install: your windows doesn't have the required resources...
I even tried installing it manually (have disc), but when u reboot, system rejects it (yellow exclamation point).
Dave and Tom,
So here we go: I did a clean install of Windows 7 Starter. As soon as I install the Intel graphics driver: BSOD. So we can eliminate the SP1 or messy systems files. What are we left with? Dave, u originally stated that monitor.sys is calling for brightness +32 and getting conflicting zero value or something to that effect. So, if we are able to narrow down to that, is there a way to week the monitor.sys not to expect brightness +32? What a wacky BSOD. Expecially when Win7 OS is the only one that does. Not giving up!
Hi,
Please post up a new SF log so we can confirm the state of your machine.
Yes it is indeed a strange BSOD, can you confirm if you have the latest chipset drivers installed?
Version: 9.1.2.1008 is the latest I can find:
Atom NM10 Chipset drivers
Cheers
Dave
Here's the SF logs before I try the chipset. Will report after I try the chipset. Just wanted to say chipset as many times as possible.
Tried the chipset...no resolve. Still stumped.