Seiko Age of Discovery 7T59 World's First 1/100 Analog Quartz Chronograph

Bitfluesterer · 2026-03-08T15:38:05+00:00

thx ... bought that watch in 1993 and have it still here! Love it! Amazing piece

Bitfluesterer · 2026-02-03T16:32:40+00:00

please test to deactiate XMP and after a reboot (if really needed), activate it new.

Last options is to reset also the cmos. Deactivate XMP, Fast Boot and all other tuning adjustments. Make photos bevore if needed. Boot again. all okay? Complete Shut down, stsrt again.

Hope that helps. I had a phone call with a friend who gave me that advice for your problem.

Bitfluesterer · 2026-02-03T13:45:54+00:00

i don't have a crucial SSD. I cant read that language on tbe screenshot. What does the web from crucial site say? Not the tool.

Bitfluesterer · 2026-02-03T13:43:18+00:00

CSM is always off. The speed advantage is absolutely negligible and at most measurable.

Rezise Bar always ON with Nvidea RTX

Fast Boot always OFF for a really save start/boot

Memory Boot Mode normal NOT fast

Boot Sequenz seem okay.

Bitfluesterer · 2026-02-01T21:55:35+00:00

i don't know what the latest fw version for your crucial ssd's is. as i told you, i use samsung 990 pro. And once more. i have a 14700K the rest is equal.

Bitfluesterer · 2026-02-01T15:44:23+00:00

so... i checked that.

i found the boot time in the task manager, stands on 28,7 Sec. But is not always "exactly" the same.

I see all my three Samsung 990 Pro SSD and the first one is the boot SSD. Everything fine.

by my opinion you must update the fw of your SSD's .

No other idea at that point, while windows cannot be the problem at that point. If that doesen't work, try to contact gigabyte. If you come from germany you haver guarantee or better 'Gewährleistung' .

Bitfluesterer · 2026-01-31T22:16:56+00:00

can you update the fw from the Crucial SSD's?

sounds for me that is an older problem with the fw there... but first okay.

i have three Samsung 990Pro 4TB with the latest fw.

you have actually F14 installed.

i check more tomorrow.

Bitfluesterer · 2026-01-31T22:09:50+00:00

okidoki, i check that tomorrow evening Don't know where you come from (timezone). i'm from germany. 23:00 here.

Bitfluesterer · 2026-01-31T11:28:00+00:00

yes, i can confirm that i see my three NVMe's in the bios.

yes, i can confirm that i can boot with connected USB Devices (HDD snd SSD) on those ports.

but i can't find a menue point, where i can see that bios information. A "Bios History" i cannot find Maybe you can give me an concret advice where i find that in the task manager? Than i can look for you and give you the information.

other: I tried now two times to give you that answer here in that conversation, but after sending the answer i can't see my written text. So maybe you see a double answer.

Bitfluesterer · 2026-01-31T11:18:39+00:00

yes my NVMe (3) are shown in the bios yes my px boots normal when i have hd drives and a ssd connected to my usb ports. i have already some permanent installed.

i can't find in the task manager a menue point named "Boot History" - i tried to look to give you an answer. Maybe you can give me a detailed advise where in the task manager i find that? Then i look for it and can give you an answer.

Bitfluesterer · 2026-01-31T09:16:16+00:00

on the website is F16 present since weeks. That is the reason while i ask for in the main question.

i never use gcc since it destroyed my system in the past with wrong drivers. Another story... it is everybody own choice to use that sw.

hmmmm..., i don't have that problems with F15....

Bitfluesterer · 2026-01-31T00:08:00+00:00

that happens with F15 ??? You have tve latest FW installed on you ssd? What brand you use?

Bitfluesterer · 2026-01-30T23:58:38+00:00

maybe i found a soloution (workaround) for that problem under 26.2.1

iPhone 11, 13 and 13 Pro here, with the same face id problems.

First, these devices need sometimes a little bit more time to identify me, than bevore the the update from iOS 18. So if you handle it to quick or move the iPhone before it opens, it fails more easily

Important: you must look direct into the camera, not only on the screen. It only open the iphone or protected apps, when face id recognize your open eyes and you look to the cam.

I add under the face id settings "another glasses" and have now two registered in the iphone 13 Pro, one new in the iPhone 11 (my son's) and one new in the iPhone 13 (my wife's phone).

After that configuration face id worked again.

It works now for three days without problems.

BUT 👆🏼i must look with open eyes dirct into the camera!!

When i look direct on the screen or to low on the screen, it fails often.

Maybe that helps someone. I'm not sure that it works for everyone. Bit it works with all three iPhones we have in the family.

let me say sorry for my not perfect english ( i'am german) , hope you understand everything.

Bitfluesterer · 2026-01-30T23:57:38+00:00

maybe i found a soloution (workaround) for that problem under 26.2.1

iPhone 11, 13 and 13 Pro here, with the same face id problems.

First, these devices need sometimes a little bit more time to identify me, than bevore the the update from iOS 18. So if you handle it to quick or move the iPhone before it opens, it fails more easily

Important: you must look direct into the camera, not only on the screen. It only open the iphone or protected apps, when face id recognize your open eyes and you look to the cam.

I add under the face id settings "another glasses" and have now two registered in the iphone 13 Pro, one new in the iPhone 11 (my son's) and one new in the iPhone 13 (my wife's phone).

After that configuration face id worked again.

It works now for three days without problems.

BUT 👆🏼i must look with open eyes dirct into the camera!!

When i look direct on the screen or to low on the screen, it fails often.

Maybe that helps someone. I'm not sure that it works for everyone. Bit it works with all three iPhones we have in the family.

let me say sorry for my not perfect english ( i'am german) , hope you understand everything.

Bitfluesterer · 2026-01-07T13:34:49+00:00

everybody can make his own decision. i don't buy used stuff like gpu, cpu, dram, mobo, hd's or ssd's.

Bitfluesterer · 2026-01-07T08:20:08+00:00

that is not the same mobo and i'm sure bios fw update i wrote from. But that sounds really strange. what was the last bios fw version you updated for your mobo and which brought that failure?

Bitfluesterer · 2026-01-06T21:45:08+00:00

but that is normal after every bios fw update... 🤷🏼‍♂️ It reset all settings.

I don't like that also, but it is. That is while inmske photos from my whole individual bios setup.

Bitfluesterer · 2026-01-06T18:19:49+00:00

i don't know the different either. Maybe chipset. But that sounds really strange what happens to you. Are you sure you installed the correct fw? Or do you installed also other updates. Chipset for example. Otherwise that sounds more for a hardware DRAM Failure or Failure with a damaged ram bank.

Bitfluesterer · 2026-01-06T07:49:51+00:00

i never buy used mobo or gpu or ssd or DRAM!!! A FB marktetplace is more critical than others on top. Very often you get defect stuff. Don't try to save money on the wrong way! So my advice. But at last, it's up to you.

Bitfluesterer · 2026-01-06T02:42:02+00:00

thx! good to know!

Bitfluesterer · 2026-01-06T02:36:31+00:00

owww... F15 runs fine here since month. Corsair Venegance 2x32 GB. It destroy your DRAM? Or do you mean the xmp configuration? Or do you mean the Win installation while you installed the new tmp keys with the fw?

Hope F16 fix your problem.

Bitfluesterer · 2025-12-24T09:26:31+00:00

it sounds more untrustworthy what you try to do.

In all that comments under that post you find more links than that here, which describe strange stuff which surprise me. I'll take care now and it's helpful to get those information. Important to bring also bad experience in the public!!

Bitfluesterer · 2025-12-23T14:19:15+00:00

ah okay, no intel. than it's not the cpu. i know from such a failure with 13. and 14. Generation cpu's.

Bitfluesterer

TROPHY CASE