I managed to check "Hide all MS-services" in msconfig, but upon restart into "regular" safe mode(no command prompt), I got the bad_pool_header 0x19 stop. Before this I had replaced the iaStor.sys file(none of the other files that followed the package from intel(iaAHCI etc.).
He has not replied to my sms yet. Will try sfc /scannow and then try the DVD to repair.
You may upload a couple of the latest dumps, alongwith the msinfo32 file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
There is another way to disable intel iaStor.sys, from Device Manager > IDE ATA/ATAPI controllers. Try that method, too.
Exoanding ATA|ATAPI controllers, you will get intel device there. Right click and disable it.
Update: he does not need RAID-stuff on his laptop. He only has a program(think it is "RAIDar" that I saw was installed) to check how the NAS is doing.
I am right now running "startup repair" from a Windows 7-disc I burned for him. This should guaranteed have non-corrupt files.
I also want to add 2 things. When I started msconfig again the checkbox for "Hide all MS-services" or how they put it on the "Service"-tab was unchecked again. Also if I am quick to check it(so as not to BSOD), I cannot click "apply"(greyed out). Not sure why. Also, regarding win32k.sys... You wrote that "sfc /scannow" would fix that problem. Problem is that "sfc /scannow" told me there were some files damaged that it could not repare(no details). I have the log though. Not sure if that log differs from the one I sent earlier.
Startup repair said it cannot repair the computer automatically. It writes 3 things as "root causes". Unknown troubleshooting: Troubleshooting 3b. An aborted system restore. Also that the integrity control and reparation of systemfiles failed(error code 0x490)
btw, some person in the beginning asked if I could use the onboard graphics card instead. I have not found an option in BIOS to do that so I have not been able to try it.
Arc, I cannot do any of that since I cannot use the graphical interface...
Reading everything, I can say that a clean install will be the best in this situation.
If you want to back some important files up, do it following Copy & Paste - in Windows Recovery Console
Then go through the steps of Clean Reinstall - Factory OEM Windows 7.
I have that as the last ditch effortTrying to do a system restore now. I thought he didn't have any such points stored almost so I haven't tried it earlier. He had had a critical update on the 5th I saw. or 2 even. I am recovering to the last one right now and will see how it goes.
I am avoiding a clean install since he has forgotten to make a recovery media of this computer. but I will if all else fails. Either tonight or tomorrow.
Thanks for the help though.
Noone want to help me try to replace the win32k.sys before attempting new install of win 7?
Recovery media is not used to Clean Reinstall - Factory OEM Windows 7. If you'd read the tutorial you'd know the installer for his licensed version is provided in the first step.
What Recovery run from disks or its partition on the HD provides is the opposite of a Clean Reinstall, with all of the corrupting factory bloatware and duplicate utilities which have better versions built into Win7, and which throttle the OS from its native state.
In this present issue under discussion, win32k.sys is not a problem, it was never, and it cannot be.
And trustedinstaller will not allow to replace you to win32k.sys. Why? Because there is enough reason to prevent you from doing it.
If win32k.sys is corrupted, SFC scannow should fix it. If SFC failed, that means there are errors beyond recovery in normal course; and the wise decision is to go for a repair install.
In your situation, the real problem is the storage controller driver. That is failing, that is unstable. But the crash dump initially failing to determine it as the failing module, so it blaming win32k.sys wrongly. I suggested you all the possible ways to stop the storage controller driver; but it is so vulnerable that it is not letting you to go upto that place too, failing even before that.
In such a situation, it is the best for you to go for a clean reinstall. Saying again, win32k.sys is not the problem, and it never was.
Here is the link to the stop 0x3B hotfix: "0x0000003B" Stop error when you run certain applications in Windows 7 or in Windows Server 2008 R2
There is a description that what files it contains. There is no win32k.sys. Verify it. And, this fix will be a part of the service pack 2. That means, win32k.sys is not anything that reported bad or failing till now.
Then why you are getting this result on the Blue Screen? It is a misunderstanding from the Crash Dump's part. We interpret it, we can come to know that it is iaStor.sys that is behind the prima facie win32k.sys.
I hope you can understand now, why nobody is helping you replace win32k.sys?
gregrocker, I HAD read the win 7-guide you had provided and misunderstood me completely. I was just thinking for his sake, should he ever want to have it as it was when he bought it. I think you too did indeed recommend making recovery disks first. I have an HP and I know they have a lot of junk in the installations that come with the comp.. but it's always nice to be able to have it as it was.
OK then Arc, I will have to trust your judgement on that. Yeah, I cannot be stable in graphic mode and most everything useful is done there save for registry-fix basically(well, apart from sfc, chkdsk etc. too).
I had found another 3b-fault(with the hotfix KB2359223) that closely matched my behaviour and included there WERE indeed win32k.sys... but, yeah, I have reached the end of the line here and also feel that a clean install indeed seems the best at this point. I have tried every recovery point I could find. did not make it better and couldn't go far enough back. Yes, I do understand.
I think maybe in trying to solve this, it has also become changed so it's not possible to restore easily, even despite being better after I came there, at least to some extent(he couldn't see labels before).
Well, hopefully a clean install shall not cause so much trouble... One of the worst cases I've ever come across.
well, well, well... I managed to extract win32k.sys from the original DVD and replace the one in his system32-folder, following the guide you have here: Extract Files from Windows 7 Installation DVD
and, voila! Computer runs "as normal", even though IE 32-bit won't start(64-bit does though). Told you guys that file seemed corrupt. Will leave to return his comp. soon. Although it works thus far(since 50 mins), I still think he may have issues, but the major problem is corrected at least.
Huge relief!
May uninstall Avast and Zone alarm that he uses and replace with MSE, but that's up to him.
Quote