New
#21
Wow, a lot of people have this problem. Well, I dont see any common factors in the system configs.
I really have no idea...
Wow, a lot of people have this problem. Well, I dont see any common factors in the system configs.
I really have no idea...
I have the same problem. I think it will be useful to know what is the different behaviour of the first boot of each calendar day with respect to the other boot in the same day
Make sure you BIOS is up to date. Also check to make sure your ram is getting the power it needs. (Refer to manufacturers specifications.) On fresh builds having this problem with no errors in the ram the problem usually is under-voltage of the ram.
This solution/tip applies to all of you who have posted.
The bios has been updated 2 days ago and the problem remained the same. I didn't check the power(I will try to do); the power supply is 750w.
The strange fact is that as soon as I switch off the computer and start again any time in the same day I have no errors
Here is a small explaining on it found in Wiki that would give a explanation between First boot (Can called as Hard Boot) other boot (Soft boot)
Hard reboot
A hard reboot (also known as a cold reboot, cold boot or cold start) is when power to a computer is cycled (turned off and then on) or a special reset signal to the processor is triggered. This restarts the computer without first performing any shut-down procedure. (With many operating systems, especially those using disk caches, after a hard reboot the filesystem may be in an "unclean" state, and an automatic scan of on-disk filesystem structures will be done before normal operation can begin.) It may be caused by power failure, be done by accident, or be done deliberately as a last resort to forcibly retrieve the system from instances of a system freeze, critical error or virus-inflicted DoS attack. It can also be used by intruders to access cryptographic keys from RAM, in which case it is called a cold boot attack. The attack relies on the data remanence property of DRAM and SRAM to retrieve memory contents which remain readable in the seconds to minutes after power has been removed.
Soft reboot
A soft reboot (also known as a warm reboot) is restarting a computer under software control, without removing power or (directly) triggering a reset line. It usually, though not always, refers to an orderly shutdown and restarting of the machine.
The Control-Alt-Delete key combination on the original IBM PC was designed to allow a soft reboot for a quicker and more convenient restart than powering the computer completely down then back up.
This kind of reboot will not usually reset the hard disks, so that they have time to update their write cache to permanent storage. Hard disks will also keep their configuration (like C/H/S adjustments, HPA, DCO, internal passwords...) over these reboots.
The Linux kernel has optional support for the kexec system call, which transfers execution to a new kernel and skips hardware or firmware reboot. The entire process is done independent of the system firmware. Note that the kernel being executed does not have to be a Linux kernel.
Hope this helps,
Captain
It seems your motherboards default is 4 x 1.5V DDR3.. DDR3 1333 voltages can range from 1.5v to 2.1v. So I would definitely look into what your RAM requires.
Agreed - the only similar thread that I have seen a solution to was when the problems at cold boot were fixed by upping the RAM voltage slightly.It seems your motherboards default is 4 x 1.5V DDR3.. DDR3 1333 voltages can range from 1.5v to 2.1v. So I would definitely look into what your RAM requires.
=================================
Hi Lastbuilders,
I have Blue Screen events with similar event information as the one you had posted above.
I would appreciate it if you could provide information on how the problem was solved on your PC.[/QUOTE]
=================================
Mar. 1st, 2011
The problem on my PC was solved after the two memory cards of the RAM, each one was DDR3 2GB from CEON, were replaced by memory cards from Kingston.
+++ Problem is solved +++
It was faulty GSKILL memory. I replaced the memory with 6GB of Corsair DDR3 and I no long have BSOD issues at startup. Even if your memtest comes up clean, this is likely to be the issue.
cheers and good luck!
=Glenn=