Windows 10 Blue Screens on First Boot Each Day
#1 
Bommelding
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 31 October 2013 - 01:10 PM
Hello people,
For a few weeks, every time I first boot my computer for that day, it shows a BSOD during booting or just after logging in. After that I just restart my computer and it'll work fine for the rest of the day.
I've tried system restore, but that doesn't work and just shows a BSOD too.
Next time it happens, i'll take a picture of the BSOD and post it here. I'm unable to do that now because today's BSOD has already happened and I already restarted my computer without making a picture.
I was wondering whether it could have something to do with my RAM.
I'm running Windows Vista on an Acer Aspire M1641:
PS: English is not my first language, so please forgive me for any mistakes 
-
Back to top
BC AdBot (Login to Remove)
-
- BleepingComputer.com
- Register to remove ads
#2
Anshad Edavana
-
- Members
- 2,805 posts
- OFFLINE
- Gender: Male
- Location: India
- Local time: 06:58 AM
Posted 31 October 2013 - 01:25 PM
Hi
Usually this kind of blue screen issues are caused by a memory module which is failing when it is cold and works fine when it is warm. If there is more than one module in the system, try a memory isolation test. That is remove either one of the module and check whether the issue happens. Then repeat the test with the other module. If one of them is faulty, you will find the faulty one in this way.
- Back to top
#3
Bommelding
- Topic Starter
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 31 October 2013 - 01:35 PM
I'm sorry, I don't fully understand which memory modules you mean. Do you mean the RAM strips?
Edited by Bommelding, 31 October 2013 - 01:35 PM.
- Back to top
#4
slgrieb
-
- Members
- 270 posts
- OFFLINE
- Gender: Male
- Location: Texas Panhandle
- Local time: 07:28 PM
Posted 31 October 2013 - 01:42 PM
I would suggest running Memtest 86+ to check your RAM. Memory should always be tested one module at a time, but I would use a diagnostic rather than swapping the modules out before startup to see if one gives you a BSOD. That's just a question of method, and I'm going to agree with Anshad on the cause of your problem; a very good call.
Edited by slgrieb, 31 October 2013 - 01:52 PM.
Yes, Mr. Death... I'll play you a game! But not CHESS !!! BAH... FOOEY! My game is...
WIFFLEBALL!
- Back to top
#5
Bommelding
- Topic Starter
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 31 October 2013 - 01:52 PM
Thank you
I can't find Administrative Tools in my control panel.. Maybe it's not available for Windows Vista Home Premium edition?
Do you maybe have a download link / tutorial about how to use Memtest 86+?
- Back to top
#6
Anshad Edavana
-
- Members
- 2,805 posts
- OFFLINE
- Gender: Male
- Location: India
- Local time: 06:58 AM
Posted 31 October 2013 - 01:54 PM
Yes, i mean the RAM modules in your system. This kind of errors are less likely to be detected in Memtest86+ and that is why i didn't recommended it in the first place. You will find an excellent tutorial from the below link.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
I
- Back to top
#7
slgrieb
-
- Members
- 270 posts
- OFFLINE
- Gender: Male
- Location: Texas Panhandle
- Local time: 07:28 PM
Posted 31 October 2013 - 01:57 PM
Thank you
I can't find Administrative Tools in my control panel.. Maybe it's not available for Windows Vista Home Premium edition?
Do you maybe have a download link / tutorial about how to use Memtest 86+?
I think you read my unedited post, and I feel that it was misleading, and I did you a disservice by over-complicating the issue. Anshad almost certainly got it right with his diagnosis of a failing RAM module.
Yes, Mr. Death... I'll play you a game! But not CHESS !!! BAH... FOOEY! My game is...
WIFFLEBALL!
- Back to top
#8
Bommelding
- Topic Starter
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 31 October 2013 - 02:07 PM
Indeed, I read your unedited post. I just read your edited post.
I'll try to run Memtest overnight and I'll post the results here. If it doesn't result in errors I'll try the method Anshad described in his first post.
I prefer doing the Memtest first to see if that is sufficient, because the other method will probably take several days 
Edited by Bommelding, 31 October 2013 - 02:07 PM.
- Back to top
#9
slgrieb
-
- Members
- 270 posts
- OFFLINE
- Gender: Male
- Location: Texas Panhandle
- Local time: 07:28 PM
Posted 31 October 2013 - 02:21 PM
Generally, running any memory diagnostic overnight is good enough. Of all diagnostic software, I think that memory diagnostics are the least reliable. I've had many modules that passed diagnostics (including some that I paid a lot of cash for) that still didn't run correctly in Windows. But, I would hope that a diagnostic test would point to a specific module that is failing. Most RAM vendors offer a lifetime warranty, and you might want to consider that option. Recently, memory prices have taken a high price hike, and so I think that makes a warranty replacement pretty attractive.
Yes, Mr. Death... I'll play you a game! But not CHESS !!! BAH... FOOEY! My game is...
WIFFLEBALL!
- Back to top
#10
Bommelding
- Topic Starter
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 31 October 2013 - 02:47 PM
That's why I try the Memtest first, because if it works, it'd save me a lot of time
If I remember correctly, I've got some 1GB DDR2 RAM strips laying around here somewhere. I guess I can just use that, can't I?
- Back to top
#11
Bommelding
- Topic Starter
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 02 November 2013 - 05:41 AM
Memtest resulted in 0 errors, so I removed one of my RAM strips.
After I removed one, my computer wouldn't boot anymore. So I opened it again and I guess I accidentally pulled my SATA-connector out while removing my RAM, because it wasn't plugged in anymore :s
After some struggle I managed to get my computer working again with just 1 of the RAM strips in it. I haven't had any BSOD since then. I'll keep the RAM out for a few more days, if I don't have any BSOD in those days I guess i'll buy a new strip.
- Back to top
#12
Anshad Edavana
-
- Members
- 2,805 posts
- OFFLINE
- Gender: Male
- Location: India
- Local time: 06:58 AM
Posted 02 November 2013 - 06:00 AM
Hi
Test the system for a few more days and if everything works fine, buy a new RAM kit compatible to your system. Let us know your findings 
.
Edited by Anshad Edavana, 02 November 2013 - 06:00 AM.
- Back to top
#13
Bommelding
- Topic Starter
-
- Members
- 75 posts
- OFFLINE
- Local time: 03:28 AM
Posted 10 November 2013 - 03:47 AM
I kept the RAM out for a week or so, and my computer never showed a BSOD during that time. However, it was very slow sometimes because of the lack of memory, of course.
So I decided to put the RAM in again, to give it 'a last chance' and to check whether it was the RAM slot or the RAM itself that was damaged. However, I've put it in yesterday morning and I haven't had any trouble since then 
Could it be the RAM was just not properly attached to the RAM slot before, therefore giving a BSOD sometimes?
- Back to top
#14
Anshad Edavana
-
- Members
- 2,805 posts
- OFFLINE
- Gender: Male
- Location: India
- Local time: 06:58 AM
Posted 10 November 2013 - 08:29 AM
Hi
Sometimes oxidation in the gold plated contacts of memory modules an cause rogue issues. At work, what i do is to use a rubber to clean the contacts (gently rub all the pins). This will clean dust and oxidation. Even though the RAM appears to wok now, i would recommend cleaning it.
Caution :Touch your fingers in an unpainted metal part of something big to discharge static electricity before touching any components inside a computer.
If the issue reappears, you should replace the module.
Edited by Anshad Edavana, 10 November 2013 - 08:29 AM.
- Back to top
Source: https://www.bleepingcomputer.com/forums/t/512497/bsod-every-day-on-first-boot/
0 Response to "Windows 10 Blue Screens on First Boot Each Day"
Post a Comment