Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

bsod on normal bootup (win7) but can boot into safe mode


  • Please log in to reply
4 replies to this topic

#1 kentatsu

kentatsu

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:19 AM

Posted 26 February 2016 - 01:52 AM

Hello everyone,

 

Long story short, I upgraded to win 10 from win 7. Something happened to my win 10 so it reverted back to win 7 and now when it starts up it bsod. But at least i can boot into safe mode. chkdsk and mem check are all good. Although I cannot run the startup repair (it wont even show as an option after I hit F8). 

 

Is there a way I can fix and run the startup repair? (or better, any way to just directly fix booting back into my win 7 desktop normally?) Well anywho, when I run bcdedit /enum all it shows: 

 

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Berlin>bcdedit /enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {deca1280-d7ce-11df-beb5-8494439681a0}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {3c7e57c0-dc55-11e5-9140-d33306e6c483}
device                  ramdisk=[C:]\Recovery\deca1282-d7ce-11df-beb5-8494439681
a0\Winre.wim,{3c7e57c1-dc55-11e5-9140-d33306e6c483}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered)
locale
osdevice                ramdisk=[C:]\Recovery\deca1282-d7ce-11df-beb5-8494439681
a0\Winre.wim,{3c7e57c1-dc55-11e5-9140-d33306e6c483}
systemroot              \windows
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=C:
systemroot              \Windows
resumeobject            {deca1280-d7ce-11df-beb5-8494439681a0}
nx                      OptIn

Resume from Hibernate
---------------------
identifier              {deca1280-d7ce-11df-beb5-8494439681a0}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 Yes

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {3c7e57c1-dc55-11e5-9140-d33306e6c483}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\deca1282-d7ce-11df-beb5-8494439681a0\boot.sdi

 

Also in my recovery folder it shows the folder of deca1282-d7ce-11df-beb5-8494439681a0 with both boot.sdi and winre.wim. Also my winload.exe seems to be in the system32 folder as well.

Sorry I'm not as tech savvy (im quite noob lol) and just want to provide as much info as I can. Just really trying to get my PC to work again :(

 

If anyone can help I would appreciate it so much! Thank you all.

 

P.S.

 

Here is also the bsod info/BCCode if its necessary:

 

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1033

Additional information about the problem:
  BCCode:    1000007e
  BCP1:    FFFFFFFF80000003
  BCP2:    FFFFF880068FD02D
  BCP3:    FFFFF880009A9468
  BCP4:    FFFFF880009A8CD0
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\022516-27237-01.dmp
  C:\Users\Berlin\AppData\Local\Temp\WER-38859-0.sysdata.xml


Edited by kentatsu, 26 February 2016 - 01:53 AM.


BC AdBot (Login to Remove)

 


#2 CyberSec_ET

CyberSec_ET

  • Members
  • 151 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Forestville California
  • Local time:04:19 AM

Posted 26 February 2016 - 05:04 AM

Here is some information from Windows 7 Help Foums

about your issue your having >

 

http://www.sevenforums.com/bsod-help-support/42547-windows-7-bsod-but-ok-safe-mode.html

 

 

>> MODS Delete Post <<


Edited by CyberSec_ET, 26 February 2016 - 05:09 AM.


#3 kentatsu

kentatsu
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:19 AM

Posted 26 February 2016 - 04:36 PM

Thank you for the reply CyberSec_ET.
I tried that method and unfortunately it isn't working. After I reboot it does not run the disk check. It just bsod after the windows logo.

#4 RolandJS

RolandJS

  • Members
  • 4,525 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Austin TX metro area
  • Local time:06:19 AM

Posted 26 February 2016 - 04:55 PM

I'm wondering if the rollback failed to reinstall the graphic chipset/video display drivers; on another computer, you might have to download manufacturer's drivers, sneaker-net 'em to your broken computer and add them into your windows via Safe Mode with Networking.


Edited by RolandJS, 26 February 2016 - 04:55 PM.

"Take care of thy backups and thy restores shall take care of thee."  -- Ben Franklin revisited.

http://collegecafe.fr.yuku.com/forums/45/Computer-Technologies/

Backup, backup, backup! -- Lady Fitzgerald (w7forums)

Clone or Image often! Backup... -- RockE (WSL)


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:19 AM

Posted 27 February 2016 - 07:50 PM

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

 

If neither of these work in Safe Mode, then here's what we need:

 

Upload Dump Files:
NOTE:  If using a disk cleaning utility, please stop using it while we are troubleshooting your issues.
Please go to C:\Windows\Minidump and zip up the contents of the folder.  Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there.  If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP.  If you find it, zip it up and upload it to a free file hosting service.  Then post the link to it in your topic so that we can download it. 

Also, search your entire hard drive for files ending in .dmp, .mdmp, and .hdmp.  Zip up any that you find and upload them with your next post.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file):  http://www.carrona.org/setmini.html
More info on dump file options here: http://support.microsoft.com/kb/254649

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the TEST.NFO file.  If you have difficulties with making this work, please post back.  Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the syteminfo.txt file.  If you have difficulties with making this work, please post back.  Then zip up the .txt file and upload/attach the .zip file with your next post.




 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users