Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Manfred
Novice
2,638 Views

Suche Donwloadmöglichkeit für BEH6110H.86A.0041 BIOS

Jump to solution

Ich suche für mein Mainboard die Downloadmöglichkeit des aktuellen BIOS BEH6110H.86A.0041 
Ich habe nur die Meldung gefunden, alle BIOS Downloads wurden entfernt.
Mein Board:  DH61CR

0 Kudos
68 Replies
VesperGremlin
New Contributor I
176 Views

The second DMP file i got from the last Blue screen of death crash is full of  'memory_corruption'-s 

i don't want to paste the whole thing but here's the last part of it :


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24260.amd64fre.win7sp1_ldr.180908-0600
Machine Name:
Kernel base = 0xfffff800`03812000 PsLoadedModuleList = 0xfffff800`03a4cc90
Debug session time: Mon Jan 18 20:14:08.576 2021 (UTC + 2:00)
System Uptime: 0 days 4:27:31.012
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd3018). Type ".hh dbgerr001" for details
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff8a00013f0d8, ffffffffc0000185, a6b7d860, fffff960002924d0}

Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff8a00013f0d8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000000a6b7d860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff960002924d0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------

Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c0000185

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88008517230 -- (.trap 0xfffff88008517230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=000000006001107b
rdx=000000000957dd00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002924d0 rsp=fffff880085173c8 rbp=fffff880085175b0
r8=000000000957dcf0 r9=0000000000000001 r10=fffff96000289e00
r11=fffff800038b39b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!NtGdiFastPolyPolyline:
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
Page a6b7d not present in the dump file. Type ".hh dbgerr004" for details
fffff960`002924d0 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000396e87e to fffff800038a59a0

STACK_TEXT:
fffff880`08516f68 fffff800`0396e87e : 00000000`0000007a fffff8a0`0013f0d8 ffffffff`c0000185 00000000`a6b7d860 : nt!KeBugCheckEx
fffff880`08516f70 fffff800`0397a9a8 : fffffa80`0383d390 fffff880`08517090 fffff880`0568bc00 ffffffff`ffffffff : nt!MiWaitForInPageComplete+0x63e
fffff880`08517040 fffff800`03981860 : ffffffff`ffffffff 00000000`00000008 00000000`c0033333 ffffffff`ffffffff : nt!MiIssueHardFault+0x4b8
fffff880`085170e0 fffff800`038b1a96 : 00000000`00000008 fffff960`002924d0 00000000`00000000 00000000`00000002 : nt!MmAccessFault+0x4820
fffff880`08517230 fffff960`002924d0 : fffff960`00289e4e ffffffff`ffffffff fffff800`03981f2e ffffffff`ffffffff : nt!KiPageFault+0x356
fffff880`085173c8 fffff960`00289e4e : ffffffff`ffffffff fffff800`03981f2e ffffffff`ffffffff fffff880`08517440 : win32k!NtGdiFastPolyPolyline
fffff880`085173d0 fffff800`038b39d3 : 00000000`6001107b 00000000`0957dd00 00000000`00000000 00000000`00000001 : win32k!NtGdiPolyPolyDraw+0x4e
fffff880`085174c0 000007fe`fecd7e1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0957dc98 fffff800`038a87b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fecd7e1a
fffff880`08517710 00000000`00000002 : fffff960`0014e54b fffff880`08506000 00000000`00000000 fffff900`c1ac3360 : nt!KiCallUserMode
fffff880`08517718 fffff960`0014e54b : fffff880`08506000 00000000`00000000 fffff900`c1ac3360 fffff880`08517c70 : 0x2
fffff880`08517720 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!ValidateHwnd+0x6b


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800038a8172 - nt!SwapContext_PatchXSave+2
[ 01:21 ]
fffff800038a82ff - nt!SwapContext_PatchXRstor+2 (+0x18d)
[ 09:29 ]
fffff800038a84c2 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1c3)
[ 01:21 ]
fffff800038a8651 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0x18f)
[ 09:29 ]
4 errors : !nt (fffff800038a8172-fffff800038a8651)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT_LARGE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------

2: kd> lmvm memory_corruption
start end module name

n_scott_pearson
Super User Retired Employee
165 Views

Obviously, with the other indications, the concern is with DMA transfers to and (especially) from the SATA drives. I see two possibilities for cause. The first is a failure in the PCH component and the SATA controller(s). The second is, well, bad memory. Either could explain what has been seen. The latter can be tested for with a tool like MemTest86 or MemTest86+ (but not the Windows memory test; it isn't sophisticated enough). Both of these tools are free, so take your pick. A third alternative is AIDA64.

...S

cypruscloud
Novice
150 Views
So we're you able to run that 16 series nvidia card of yours after the bios update.
Tags (1)
cypruscloud
Novice
145 Views
Hey@VesperGremlin were you able to run your 1650 super on Intel dh61ww motherboard after the bios update
n_scott_pearson
Super User Retired Employee
141 Views

In my DZ68ZV board, I have verified I can run both a MSI GeForce GTX 750 ti as well as a Gigabyte GeForce GT 1030. Unfortunately, I don't have a DH61WW board available to me.

Hope this helps,

...S

VesperGremlin
New Contributor I
130 Views

Hey cyprus cloud , sorry i completely forgot about this place

Oh yes i was , works perfectly OK , the GPU was not even displaying anything with BIOS 0016 or whatever it was , after i updated to 0117 it worked like a charm .

I am currently having other issues with the board itself , the main problem being that the computer suddenly becomes unresponsive and restarts on its own , with or without the 1650 Super installed .

I have been having this problem even before i updated the BIOS to install the new GPU. So it's the motherboard that's going bad . But otherwise if you have a motherboard like this one the card will work just fine after a successful BIOS update .

VesperGremlin
New Contributor I
126 Views

Hello again Scott

Funny i found that same board today , a used DZ68ZV .

And another used CPU , the i5-2500 .

It's still lockdown season here so i will only be able to buy those some time in february .

VesperGremlin
New Contributor I
135 Views

I found a DZ68ZV board , i will buy that one and try the same card on it .

The card works fine with the dh61ww , and i says again : the crashes that happen have nothing to do with card-motherboard incompatibility - and they are not occur very frequently either , so i had plenty of time to try the card and it works perfectly on that board .

I am glad i came back to answer yer question .

Salut .

VesperGremlin
New Contributor I
135 Views

Do not * occur frequently i mean

cypruscloud
Novice
123 Views
Hey VesperGremlin thanks for your reply and I am happy to know that it works cause I am having the same kind of problem with graphics card
VesperGremlin
New Contributor I
115 Views

What is the board's current BIOS version ?

I used the relatively weak I3-2100 processor on that board with 8gbs of RAM and the 1650 super - it easily ran every single game i threw at it .

No indigestion there heh )

cypruscloud
Novice
112 Views
Bios version: 0048
ME firmware: 8.0.13.1502
VesperGremlin
New Contributor I
116 Views

Yes it won't work with 0048 . perfectly normal .

Easy , all you need now are two more updates - it was a little more difficult for me as i started from 0016 .

From 0048 update to 0099 , then to 120 .

Follow Scott's instructions on page 1  -  He included all the versions you need to download too .

I have to say i had never done a BIOS update before and was a bit nervous , but if you follow the instructions it'll go just fine .

cypruscloud
Novice
113 Views
Well I started from the version 0020 and now I am at 0048. I stopped here because I saw some post where users were complaining about the 0099 update bricking there board so I wanted to do some research first.
VesperGremlin
New Contributor I
109 Views

Yes good you brought that up

0099 didn't install correctly with me

the computer didn't start after 0099 .

So after that i downloaded the recovery BIOS 0117 from another site , i'll find that site now - I used RUFUS to install 0117 and that is where i stopped . Everything worked fine after that and i didn't continue updating .

Maybe i should ask Scott about that before you update to 0099 .

 

VesperGremlin
New Contributor I
108 Views

I must have written about all the things i did to update in a reply on one of these pages somewhere .

Let me find that

VesperGremlin
New Contributor I
100 Views

Here :

'' Update went ok with F7 up until 35 , at which point i got stuck , i then - with the help of his holiness saint RUFUS - was able to update it all the way up to 99 .

The computer would not boot past the intel page again with 99 , and this time it made no difference whether i used integrated graphics or the 1650 super . Then i managed to update to 117 with a bios recovery file i had found somewhere and everything worked fine . ''

Yeah like you said , something wrong with version 99 . When that happened i thought i was the one who had made a mistake but now that you mention it i realize it must have been something everyone has experienced at one point .

Right after that happened i downloaded the 0117 recovery BIOS from here :

https://drivers.softpedia.com/get/BIOS/Intel/Intel-DH61WW-Desktop-Board-Recovery-BIOS-0117.shtml

That fixed it for me .

 

VesperGremlin
New Contributor I
99 Views

What is your graphics card ?

cypruscloud
Novice
94 Views
Thank you so much VesperGremlin. and I am using integrated graphics because my old graphics card is dead and planning to purchase a graphics card
VesperGremlin
New Contributor I
85 Views

I tried a GTX 1050-TI on the DH61WW back when the BIOS version was still 0016 and it worked fine ( 0016 is the oldest BIOS version )

So , if you are going to get a card from the GTX 10 series (or below) , try the GPU on the board first before you update the BIOS - It might work without any need for BIOS Updates .

Keep me updated Kypros Cloud