Community
cancel
Showing results for 
Search instead for 
Did you mean: 
kcran
Beginner
1,404 Views

Cannot enter BIOS, Asmedia SATA

HELP! Assume I am not a complete idiot please.

I have a system that I am using, or at least trying, to use for dual boot. Before I get the usual remove battery stuff and all that nonsense here is the problem.

Everything works great until I hook up a drive to the SATA 3 ports on the Asmedia controller. Once I do that, I can not enter BIOS....you know the problem ...when I hit F2 to enter BIOS screen goes black.......

Been through 3 iterations of this now.

I have tried everything and in different sequences, including: reseating all, wiping drives, MBR, full clean, making sure no ID's left on drives, etc.

If I disconnect drives and video card and hook up one at a time after Back to Basics or clean boot/BIOS, again everything works great until......I hook up the last drive and the ONLY drive on the SATA 3 ports.

----

Windows 7 Pro 64 bit, GE force GTX780, USB Mouse and keyboard. Boot set for UEFI and Legacy until I finish which I can't do until everything works properly then I will uefi, both SATA controllers enabled. No raid.

Processor: Core i7-4770K

Board: DZ87KLT75k

AA: AAG74721-305

BIOS: KL78711D.86A.0452.2014.0605.0927

Memory: 32GB of Corsair Vengance,

WD 500GB Velociraptor drives x4, all on sata 6

WD 1TB Drives x2, one on SATA 6 one on SATA 3

----

I want to leave one of the SATA 6 ports open for a possible hardware addition at a later time.

Again, I have tried everything, including wiping everything and starting over with one WD drive on SATA 6 port, memory and video card. Everything works great, OS loads up fine boots, recognizes everything, all is awesome until I connect the last drive in the system on the SATA 3 port and format it. Then I can not enter BIOS and the other Windows dual boot OS won't recognize USB mouse and keyboard. This has happened 3 times in a row now.

Irritating and frustrating. Been building PC's since Win 95. I don't want to lose advertised functionality to "fix this". I also do not want to have to take apart my PC every time I want to enter the BIOS or to dual properly.

 

Once I hook up that previously wiped then formatted drive on the SATA 3 controller, things go south.

0 Kudos
3 Replies
Kevin_M_Intel
Employee
218 Views

Hi ndglass1,

I am sorry you are having this problem but let me help you.

The behavior you are describing is very strange and I honestly have not heard about this problem before but I will take a look on this with the Demo I have next to me (same model).

There is some more information I would like to know just to make sure I have a clear picture:

  1. What are the Operating Systems you are trying to install?
  2. Do you have both HDDs connected to Intel® Sata? Is there any HDD connected to the Marvel?
  3. Have you tried different images or installation files?
  4. Is there a way to test different HDD?
  5. Can you attach your dxdiag report here?

How to get it?

Dxdiag Report: Type dxdiag in Start Menu> open> Save> Copy/Paste here.

Kevin M

kcran
Beginner
218 Views

Hey, always nice to meet another Kevin.

You will notice in the report some multiple-partitions; the issue starts before I partition any drive. It only starts once I hook up the last 1TB drive to the SATA 3 ports. All other drives hooked into SATA6 ports. No windows errors that I know of, no resource or hardware conflicts...at least that I can find.

Win7Pro and Win8.1 Pro. I have multiple Win7 images and have tried 2 of them with same results.

The drives I know work properly. I have tried different combinations on different ports, diskpart, Clean All, Chkdisk, etc. I can read to and write on all disks and seem to have no other issues.

Except.....when I hook up the 6th and final drive in the system on the SATA3 port. This is just with initial Win7 install no other programs, windows updates... nothing but Windows and hardware.

Maybe some issues with resources? IRQ? I don't know. Since I also lose video when I try to enter Set-up, it seems to me to maybe be some conflict or resource issue. Isn't there something about USB, PCI and SATA Controller sharing some resources on this board; think I read that somewhere.

Dxdiag Below:

------------------

 

System Information

 

------------------

 

Time of this report: 7/30/2014, 16:39:20

 

Machine name: PLASMA-PC

 

Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)

 

Language: English (Regional Setting: English)

 

System Manufacturer: INTEL_

 

System Model: DZ87KLT_

 

BIOS: Default System BIOS

 

Processor: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz

 

Memory: 32768MB RAM

 

Available OS Memory: 32726MB RAM

 

Page File: 3612MB used, 127292MB available

 

Windows Dir: C:\Windows

 

DirectX Version: DirectX 11

 

DX Setup Parameters: Not found

 

User DPI Setting: Using System DPI

 

System DPI Setting: 96 DPI (100 percent)

 

DWM DPI Scaling: Disabled

 

DxDiag Version: 6.01.7601.17514 32bit Unicode

------------

 

DxDiag Notes

 

------------

 

Display Tab 1: No problems found.

 

Sound Tab 1: No problems found.

 

Sound Tab 2: No problems found.

 

Sound Tab 3: No problems found.

 

Input Tab: No problems found.

--------------------

 

DirectX Debug Levels

 

--------------------

 

Direct3D: 0/4 (retail)

 

DirectDraw: 0/4 (retail)

 

DirectInput: 0/5 (retail)

 

DirectMusic: 0/5 (retail)

 

DirectPlay: 0/9 (retail)

 

DirectSound: 0/5 (retail)

 

DirectShow: 0/6 (retail)

---------------

 

Display Devices

 

---------------

 

Card name: NVIDIA GeForce GTX 780

 

Manufacturer: NVIDIA

 

Chip type: GeForce GTX 780

 

DAC type: Integrated RAMDAC

 

Device Key: Enum\PCI\VEN_10DE&DEV_1004&SUBSYS_07813842&REV_A1

 

Display Memory: 4095 MB

 

Dedicated Memory: 2994 MB

 

Shared Memory: 1101 MB

 

Current Mode: 1920 x 1080 (32 bit) (60Hz)

 

Monitor Name: Generic PnP Monitor

 

Monitor Model: E2241

 

Monitor Id: GSM5819

 

Native Mode: 1920 x 1080(p) (60.000Hz)

 

Output Type: DVI

 

Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

 

Driver File Version: 9.18.0013.3523 (English)

 

Driver Version: 9.18.13.3523

 

DDI Version: 11

 

Driver Model: WDDM 1.1

 

Driver Attributes: Final Retail

 

Driver Date/Size: 3/20/2014 23:02:50, 17755424 bytes

 

WHQL Logo'd: Yes

 

WHQL Date Stamp:

 

Device Identifier: {D7B71E3E-5344-11CF-3156-8C271CC2C435}

 

Vendor ID: 0x10DE

 

Device ID: 0x1004

 

SubSys ID: 0x07813842

 

Revision ID: 0x00A1

 

Driver Strong Name: oem37.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section093:9.18.13.3523:pci\ven_10de&dev_1004

 

Rank Of Driver: 00E02001

 

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C

 

Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

 

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

 

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

 

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

 

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

 

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

 

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

 

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

 

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

 

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

 

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

 

...
Kevin_M_Intel
Employee
218 Views

Thanks for the information. I am sorry but I have some more questions. You mentioned the issue appears when you connect a driver to the SATA 3 Asmedia controller but the motherboard does not have this but Intel® and Marvel controllers so, do you have any PCI card with Asmedia Controller connected to the system? Or maybe you are referring to the Blue SATA onboard ports (Intel®)?

I have tested the system with 2 HDDs 500GB each and 1 TB HDD. I also have an SSD and ODD connected all to the Blue SATA ports and I am able to access the BIOS without any problem. So I am not able to reproduce the issue so far.

Kevin M

Reply