BleepingComputer.com: Vista Won't Load

Hi,

I have an HP Pavilion dv9429us. I got it in July 2007 and it worked flawlessly until I accidently dropped something on the keyboard in April, killing the HD. Got it replaced and all was well until June when I went to turn it on and got a blank screen. Turns out there was a known issue with the motherboards in certain models of HP laptops, including mine:



http://h10025.www1.hp.com/ewfrf/wc/documen...roduct=3446945#



So I sent it to HP and they fixed it for free and for some reason, replaced my screen, keyboard and touchpad as well. Again all was well until September when I went to turn it on and after the HP splash screen it went blank. Vista wouldn't load. Restarting brought up the "Windows failed to start" screen and asked if I wanted to run Startup Recovery or load normally. Choosing Startup Recovery brought up the "loading files" bar and then a blank screen again. The only thing that fixed it was turning it off, unplugging it, removing the battery and pressing the power button for 30 seconds. After plugging back in and turning on the Startup Recovery worked and Vista booted up fine, and all was fine until last week. Since then this boot issue has happened 5 times. Each time I was able to fix it with the procedure above but it is a real pain.



I get no error messages other than what I described above. Got one BSOD last week, it went too fast to read but I know a memory dump ocurred. Hasn't happened since. Windows says it repairs the issue with a System Restore each time. Memory and HD diagnostics all come back fine. Is my motherboard failing again? I can't figure out what it could be. Once Vista is up and running everything is fine until I turn my computer off.



I appreciate any and all help!

Startup Repair generates a log file at this location: %WINDIR%\System32\LogFiles\Srt\SrtTrail.txt
Copy and paste the text from it into your next post.

Here's a link for helping to analyze the BSOD info: http://www.bleepingcomputer.com/forums/topic176011.html

you should also go to your Event Viewer and post this here as well
Event Viewer is in your admin tools or simply right click my computer and goto Manage, this will open admin tools. Goto "Event Viewer", "windows logs", "system" and check for any error logs around the time you got BSOD and then post that here also.

usasma, on Nov 9 2008, 06:15 PM, said:

Here it is:

Startup Repair diagnosis and repair log
---------------------------
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 297 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 499 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 749 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 3260 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code = 0x0
Time taken = 1529 ms

Test Performed:
---------------------------
Name: Access control test
Result: Completed successfully. Error code = 0x0
Time taken = 18626 ms

Test Performed:
---------------------------
Name: File system test (chkdsk)
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Software installation log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Fallback diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Unspecified changes to system configuration might have caused the problem.

Repair action: System Restore
Result: Completed successfully. Error code = 0x0
Time taken = 80637 ms

---------------------------
---------------------------

juztrax, on Nov 10 2008, 01:04 AM, said:

Here's what I found. These are the only errors there. I'm far from computer illiterate but I am unsure what these errors mean-since two say they are caused by faulty hardware I will assume perhaps my motherboard is failing again. If so I will be really irritated. A laptop should last more than 16 months and a new motherboard more than 4! I don't abuse my computer in anyway. It stays on my desk on a cooling pad. I've never opened it up nor have I messed with any registry or bios settings or installed anything new in quite a while. I do regular scans with AVG, AdAware and HiJackThis and all is clean.

Windows (3032) Windows: A request to write to the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 222650368 (0x000000000d456000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (22033 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

The Collect Procedure for the "EmdCache" service in DLL "C:\Windows\system32\emdmgmt.dll" generated an exception or returned an invalid status. The performance data returned by the counter DLL will not be returned in the Perf Data Block. The first four bytes (DWORD) of the Data section contains the exception code or status code.

The Open Procedure for service "PNRPsvc" in DLL "C:\Windows\system32\pnrpperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.

Windows (2660) Windows: A request to read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 145956864 (0x0000000008b32000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (18525 seconds) to be serviced by the OS. In addition, 1 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 56786 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Did System Restore repair the problem? (that's what the logfile says)
Oops, didn't recall the first post!

I'd have to suggest locating the memory dump files and performing the analysis on them.

Beyond that, the first and last errors state that "This problem is likely due to faulty hardware."
The memory dump will give us more info about where this is occurring and will help to determine if it's likely to be hardware or software related.