Windows staring blue screen error
I have really bad problems to get my windows 7 to boot up. So this issue happens just before welcome screen, windows starting stops at black
screen and I have to restart many times to get windows to boot up. Sometimes it starts normally but not very often. I have tried to restore (any point), windows own fix tools like starting fix, scandisc, none of those have
helped.
What might cause this issue and what would be the best way to fix it? Here is the error report (it's Finnish so I had to translate).
Ongelman tunniste:
problem identification
Ongelmatapahtuman nimi: BlueScreen
Käyttöjärjestelmän versio: 6.1.7600.2.0.0.768.3
Aluekohtaisten asetusten tunnus: 1035
Lisätietoja ongelmasta:
more information about the problem
BCCode: 124
BCP1: 00000000
BCP2: 865EF22C
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Ongelman kuvausta helpottavat tiedostot:
Facilitate the description of the problem files:
C:\Windows\Minidump\062610-21808-01.dmp
C:\Users\Lucien\AppData\Local\Temp\WER-46971-0.sysdata.xml
June 28th, 2010 2:48pm
Firts question: did it work before? If so, has something changed that might cause the issue?
if not, please try the steps described in
http://windows.microsoft.com/en-US/windows-vista/What-to-do-if-Windows-wont-start-correctly and
http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7
The fact the sytem boots sometimes excludes things that do not change between reboots. Random crashes ofton are caused by issues with RAM (you can use
this tool or check this), overheated components (if the system worked well before check any fans and dustfilters). Also disk errros can be the cause (but you already did a chkdsk I read).
If none of these "easy fixes" adresses the issue, only thorough BSOD analysis can determine the cause. You can do this yourself using
Windbg. This however is not really easy and therefore recommended only for (very) experienced users and developers. However, Windows includes ways to submit your dmp files
to Microsoft for analysis.MCSA/MCTS/MCP
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2010 3:35pm
Hi,
I would like to suggest you update the BIOS and the hardware drivers for Windows 7 first.
If the issue persists, would you please upload the minidump files to the public folder of
SkyDrive and provide us the link for our further research?
Collect Minidump Files
=================
1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.
2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".
3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.
4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.
If the Blue Screen appears again, please refer to the following steps to collect memory dump files:
1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.
2. Go to your Desktop, right-click on it and create a new folder named "Dump".
3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.
4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".
5. Please send the ZIP file to us.
You may also analyze them with Debugging Tools by yourself. You can install it and it’s Symbol Packages from the following link:
http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx
WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article:
How to read the small memory dump files that Windows creates for debugging.
If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist
with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
June 29th, 2010 8:12am
You're getting bugcheck 0x124 - WHEA_UNCORRECTABLE_ERROR. "This bug check indicates that a fatal hardware error has occurred."
You've got probably got some faulty hardware, unfortunately, perhaps the processor and/or perhaps the motherboard. Additional things you can try, though, just to see... Ensure
that the system has adequate cooling and ventilation. Test RAM, reseat RAM and the processor if you can. If
the BIOS is the latest, consider reverting to a previous version and see if that helps. If not, install the latest version. Also double-check BIOS settings; perhaps, note current settings, reset the BIOS defaults, and then adjust those settings
you know are necessary to adjust. Double-check voltage, etc. and ensure/verify CPU compatibility with the motherboard. If you're overclocking, stop.
Can you upload the contents of c:\windows\minidump to your SkyDrive and
provide a link? The dumps may hold more details about the specific problem you're encountering.
For dealing with Blue Screens, general guidance follows (not that the below will necessarily be of much use to you given the type of problem you appear to be experiencing):
Consider running chkdsk on all partitions. Let chkdsk complete on each partition and see if that helps.
Also consider running SFC /SCANNOW.
Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS.
Consider testing memory with Windows Memory Diagnostic or memtest86. Note
that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the
other modules.
If you boot into safe mode, do you still experience bugchecks? What about if you do a clean
boot, or device
clean boot?
It can be helpful to use Driver Verifier. To enable Driver Verifier... start->verifier.exe->OK->Create standard settings- >Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish,
and OK your way out of the dialog.
Then, reboot and use the system as you normally would, and wait for a problem. In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the
changes.
Wait for a bugcheck to occur after enabling verifier as described, and then upload it to your SkyDrive,
and provide a link.
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2010 10:43pm