Why does my desktop PC fail to boot first try?

-

after having since installed windows 10 technical preview on 80gb hdd, single partition, main os (not dual boot).

whenever start desktop pc first time automatically turns off before able login windows 10 technical preview.
when turn on desktop pc second time windows 10 technical preview starts fine.

i tested few times in succession , every time shut down computer , turn on, loading windows 10 technical preview, loads preview successfully.  after leaving computer off period of @ least 30 minutes , turning on, first boot causes desktop pc automatically turn off before i'm able login.

i continue using windows 10 technical preview if i'm unable boot first time, every time, it's frustrating.


my desktop pc system specifications:

  • cpu: intel core i5-750 lynnfield quad-core
  • mb:   asus p7p55d - hybrid series
  • ram: corsair xms3 4gb ddr3 1600
  • hdd: seagate 80gb 7200 rpm
  • gpu: sapphire hd 7750 1gb gddr5
  • psu: antec cp-850

hi,

you might try turning off feature called fast startup...

this feature works when shutdown , boot.

it doesn't effect restart.

to turn off or on...

go control panel...power options, , select choose power buttons on left.

then select change settings unavailable near top center of screen...

lower down on window, uncheck fast startup.

if helps, source of problem driver not loading properly...



Windows 10 Insider Preview  >  Windows 10 Insider Preview General



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more