Home > Bsod On > BSOD On Only Cold Boots

BSOD On Only Cold Boots

It also doesn't matter what speed, 1600 or 1333. Please help The test I have adopted for stability is agentGOD's Intel Burn Test. PotoLOL View Public Profile Find all posts by PotoLOL #9 09-26-2010, 04:21 AM alpaugh78 Registered User alpaugh78's PC Specs alpaugh78's PC Specs MotherboardGigabyte P55A-UD4P ProcessorIntel i7 860 Memorycmx4gx3m2a1600c9 Video same exact problem, two different mobo's/system styles. Bonuses

Computer Type: PC/Desktop System Manufacturer/Model Number: self build OS: windows 10 Pro Quote topgundcp View Profile View Forum Posts Private Message VIP Member Posts : 2,023 Ubuntu14.04x64 MintMate17x64 Win10Prox64 New Generated Wed, 22 Mar 2017 08:36:20 GMT by s_bd41 (squid/3.5.23) CNET Reviews Best Products Appliances Audio Cameras Cars Networking Desktops Drones Headphones Laptops Phones Printers Software Smart Home Tablets TVs Virtual After that I can restart and run Memtest again without a single error. Computer Type: PC/Desktop System Manufacturer/Model Number: *Custom Built* OS: Windows 10 Home 64-bit CPU: Intel i5 2500k @ 4.7GHz (OC disabled for debugging) Motherboard: Gigabyte Z77X-UD3H Memory: 2 x [CMZ8GX3M1A1600C10 Corsair

The computer ran fine with Windows 7, and also ran fine for about one month with Windows 10. It's a Gateway 5040 running XP Media Center SP3 with 4G of RAM. Step 3: I would suggest updating the drivers for your motherboard/hardware and making sure they are installed properly. Yesterday I experienced a red boot screen after restoring to a windwos restore point installing a new GeForce driver, that is probably related to this issue.

Track this discussion and email me when there are updates If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and Set up an RMA on my memory and was wondering how long my RMA number is good for. Sep 29, 2005 BSOD on cold boots since HW upgrade Jan 8, 2012 BSOD only on cold boot Mar 9, 2009 Bsod on cold start, only after a date change?? This screen should give you a hint of what's wrong.

Thanks! It would just really be a great ego booster if I could find out what is wrong and fix it. You'll find discussions about fixing problems with computer hardware, computer software, Windows, viruses, security, as well as networks and the Internet.Real-Time ActivityMy Tracked DiscussionsFAQsPoliciesModerators General discussion BSOD on Cold Startup Only Personally I'm exhausted from this issue right now, and just want to find the solution.

This post has been flagged and will be reviewed by our staff. Over time, it has increased to 6 or 7 boot attempts before it goes into Windows. You may also... When this is done, my machine is perfect upon "waking".

Now, I could just uninstall it and revert back to the WHQL driver... "Working on it..." Message for over 18 hours in Installation and Upgrade I am trying to upgrade through https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-on-cold-startup-but-ok-on-restart-or/3ed9116d-20f8-44f9-8f9d-f377963f725a I added a missing feature - image creation, which would be welcomed by Virtual PC users. Only recently I started getting BSOD's pointing to ntoskrnl+142770. It runs perfectly otherwise.

It does this no matter how I set my memory up in bios whether it's XMP or manually. browse this site Does this mean the RAM is bad? I just updated bios today with the hope that it takes care of the problem. Nov 13, 2008 #6 (You must log in or sign up to reply here.) Show Ignored Content Topic Status: Not open for further replies.

If it does or if it doesn't, repeat the process until you have tested each stick of ram in this way. I don't really understand much else. Have you scheduled Checkdisk or tried system repair? read this article In windows10 as far as i know secure boot option is enabled by default.

Thanks for you help! Will putting all new memory in stop this? I reinstalled my GPU drivers...

One of the Blue Screen errors I've received before pointed to a problem with the ACPI.SYS driver, which I have already replaced once.

Then I would try to boot the computer up again, and it would boot into Windows, without a problem. I have a custom built computer that is running Windows XP, SP3. Forum New Posts FAQ Tutorial Index Tutorials Join Us Forum Windows 10 Forums BSOD Crashes and Debugging Windows 10: BSOD on most "cold" boots (or first boot after several hours) Page To create a CD with ISO Recorder right-click on a file with .iso extension and select "open with then click ISO Recorder" Step 2: I would suggest: If you have more

STOP: c000021a 3). I can also provide my last kernal dump file if you think that would be helpful. I have downloaded and run as many diagnostic tools as I could find on the Internet (registry cleaners, old driver removers, temporary file removers, spyware/malware removers, etc.) and nothing has helped. click here now I'm still learning my ways around a pc so I use forums alot for help.

Unfortunately I lack the experience to understand most of it. Not sure why it would suddenly come loose after being in place for years, but I WILL check. After a couple tries the pc will then boot into Windows. Join the community here.

I didn't change or do ANYTHING yesterday. This could explain your cold boot problems. It showed no errors. Robyn Flag Permalink This was helpful (0) Collapse - This Morning...

I am at my wits end here. TechSpot is a registered trademark. They are mostly MEMORY_MANAGEMENT. When I was using my faulty module I've often had CRC errors with compressed files.

Once it gets going my pc runs great. Computer typically blue screens, sometimes it freezes at the bios splash screen where they Windows 10... Let you know tonight. First, Download memtest from www.memtest.org and let it run for a minimum of 7 passes.

Well, this morning it loaded perfectly. After a couple tries the pc will then boot into Windows. I removed one RAM chip and booted the computer up with the other. Been a frustrating last 2 weeks with this and this should make the problem clear.

It then goes on to indicate NTFS_FILE_SYSTEM and tells you what steps to follow if it is the first time you saw the message. It is also a good idea to boot to the Recovery Console and run Chkdsk /f /r to detect and resolve any file system structural corruption. I've googled every number here, and nothing fits or makes sense to me.