Booting twice

[erndog105]

I have W7 Home and at start up first time each day (only) the boot screen appears, followed quickly by a blue screen that is too fast to read and a second boot screen comes up. this is followed by an error screen that says Windows failed to start, a recent h/w or s/w problem may have cause the problem. I get two options, try and fix or start normally.
After that, each new start up during the day is normal. Next day, it all starts over again.
Any ideas?

 

[richc46]

What are you doing different between the first boot in the morning and those during the day?

 

[TGSoldier]

Right click on my computer.. go to properties.. the advanced tap.. statup and recovery,.. uncheck the automatically restart tab at the bottom them.

Next time it BSOD's, upload the .dmp file so we can take a look at it and pinpoint your problem.

 

[zigzag3143]

I have W7 Home and at start up first time each day (only) the boot screen appears, followed quickly by a blue screen that is too fast to read and a second boot screen comes up. this is followed by an error screen that says Windows failed to start, a recent h/w or s/w problem may have cause the problem. I get two options, try and fix or start normally.
After that, each new start up during the day is normal. Next day, it all starts over again.
Any ideas?

since it appears you are getting an actual BSOD can you use these instructions to find and upload the created dmp file? http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html


Thanks

Ken J+

 

[chev65]

Cold start issues usually point to the power supply.

 

[erndog105]

zigZag, I will try and get the dump. Right now I am trying to learn how to use the cmd command.

 

[erndog105]

I need additional help. I have located the mini dump in question and have winzip. But when I try and get to the dump, it says I do not have permission to open this file and I need to be owner or admin for permission. I am the admin. on this computer. Minidump folder is locked.

 

[riggs614]

I have W7 Home and at start up first time each day (only) the boot screen appears, followed quickly by a blue screen that is too fast to read and a second boot screen comes up. this is followed by an error screen that says Windows failed to start, a recent h/w or s/w problem may have cause the problem. I get two options, try and fix or start normally.
After that, each new start up during the day is normal. Next day, it all starts over again.
Any ideas?

I ran into similar issues, check out the thread to see if any of these suggestions may help:

http://www.sevenforums.com/crashes-debugging/45354-bsod-startup.html

 

[erndog105]

Need help with dump file

Not sure I know what I am doing but I went to the mini dump file and am attaching the latest dump. This problem happens every morning at first time start up. If this is not done correctly please let me know. Attached is the dump. I tried to load the actual file but could only load the zip of it.

 

[chev65]

I've seen this same exact problem on a bunch of systems and it always ended up being a PSU issue. What happens is that on cold starts the power drops below a level that is acceptable for the motherboard so it crashes and shuts down to protect itself. After that starting is normal again because the parts aren't so cold and do not draw as much power. Certain boards are dependent on exact power requirements and will not run unless they get the correct voltage.

It's not that the PSU isn't high enough output, it's that on cold starts the MOBO will automatically shut down if power drops below an acceptable level for even a second. You can keep beating around with the dmp's but when you get tired of it I highly suggest trying a different power supply and see if anything changes with your cold start problem.

The .dmp's point to a system file.
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe

And a component of your Nvidia driver showed up, which is fairly inconslusive for a cold start problem.
SYMBOL_NAME: nvlddmkm+13286e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387
FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+13286e
BUCKET_ID: X64_0x50_nvlddmkm+13286e
Followup: MachineOwner

 

[riggs614]

chev,

While I don't doubt your assessment, I had an issue that sounds almost exactly like what erndog105 is having, and it was a driver issue, related to the TDP problem with graphics stuff in Vista and 7.

You can see my previous post about it. Once I removed some Windows Updates and reverted to the drivers that came with my MoBo, this problem didn't occur anymore.

 

[chev65]

I read about your issue riggs and it didn't look to be the same to me. You didn't have an issue until after you were messing around with an HDMI connection. Quote:I didn't have this issue until I tried to setup my HDTV on the HDMI. You also said this,.. It set up fine, but upon reboot, I had distorted graphics, right from post, and Windows 7 only got as far the loading Windows screen logo. BSOD with atikmdag.sys error.

If you don't mind I'd like to stick to solving the Op's issue.

I see no mention there of a cold boot issue at all.

No offence but your problem is completely different.

 

[riggs614]

I read about your issue riggs and it didn't look to be the same to me. You didn't have an issue until after you were messing around with an HDMI connection. And you didn't have a cold boot problem everyday like the Op seems to be having. Your problem is completely different.

Even with the HDMI removed, the problem continued. This problem occurred each time I tried to restart my computer, regardless of it it was from cold boot, or just a simple restart.

I assumed the issue was related to the HDMI connection, but after removing the Windows updates and reverting drivers, I can restart with HDMI/without HDMI and it starts fine. My BSOD also pointed to the driver associated with my graphics card. Since that was teh only change I thought I made at that time, I blamed it on the HDMI. However, after digging through updates, I realized some other things occurred around that time.

It might not have been that clear though my thread, but reading about his issue, it was how my computer worked for 5-6 days until I fixed it.

 

[chev65]

I read about your issue riggs and it didn't look to be the same to me. You didn't have an issue until after you were messing around with an HDMI connection. And you didn't have a cold boot problem everyday like the Op seems to be having. Your problem is completely different.

Even with the HDMI removed, the problem continued. This problem occurred each time I tried to restart my computer, regardless of it it was from cold boot, or just a simple restart.

I assumed the issue was related to the HDMI connection, but after removing the Windows updates and reverting drivers, I can restart with HDMI/without HDMI and it starts fine. My BSOD also pointed to the driver associated with my graphics card. Since that was teh only change I thought I made at that time, I blamed it on the HDMI. However, after digging through updates, I realized some other things occurred around that time.

It might not have been that clear though my thread, but reading about his issue, it was how my computer worked for 5-6 days until I fixed it.

You just helped prove my point..again, you didn't have a cold boot issue at all, your problems were occuring on every boot. The Op also never mentioned any problem at all with Windows update or messing with an HDMI connection. There is a big difference between a cold boot only problem and a simple crashing problem like you had.

Please stick to your own posts and I will stick to mine. I didn't derail your post even though I knew it was not the same problem, and I would appreciate if you show me the same respect.

Now, If you don't mind I would like to keep this thread about solving the Op's problems.

 

[erndog105]

Chev65, thanks so much. At least it gives me a place to start. This computer is 2 years old, built by Pugent Systems and has been nothing but hard ware hell since day one. Would you believe when it was delivered, it power cord did not even work. Too many other issues to recap but a failing Power unit would not be a surprise, Ill start there and let you know. Thanks.

 

[erndog105]

Problem fixed, so far. I went to Nvidia and found a x64 driver for the video card, down loaded it and to date, problem has not returned. Puget suggested I also check some other stuff with two probrams. First, Google Prime95. Then CoreTemp. I will do this but I think my problem is now fixed. thanks all.