All aktivitet

148 382

28 464

Skal du dra til Drømmeland nå?

Nå hører vi to på: Bad To Me - The Beatles.♥️♥️♥️♥️

Banner SprengeMobil for vi Digger Kings Of Leon.

Løkringer

Vi har akkurat spist frokost.😋😋

8125

28 465

148 381

Vi ønsker dere alle sammen her i tråden, en fin og god torsdagsmorgen.♥️♥️

Vi ønsker dere alle sammen en Godtorsdagsmorgen.👨‍🦰👩‍🦰

148 380

28 466

Ja, det vil jeg nok tro at han ikke har. 😏😌

Haha, CC har ikke alle hestene hjemme.

8124

Søskenbandet The Corrs.

Drøvel

F48E

148 379

28 467

Banner Ciaran og Ciara for å få meg til å tenke på Kings of Leon, som har denne råbra sangen her!

Postgirobygget - Sløv uten dop

Her er fra Claude, jeg gikk tom for daglige meldinger, så det er det jeg fikk til så langt: .evtx is a Windows Event Log binary format. I'll parse it with Python. Ran 15 commands Ran 15 commands Here's a full breakdown of what the event log reveals. This system (DESKTOP-P7D1IU4, Gigabyte Z690 GAMING X DDR4) has several serious problems: 🔴 Critical: Multiple BSODs (Blue Screens of Death) Stop 0x00000101 — CLOCK_WATCHDOG_TIMEOUT CPU core #19 stopped responding to clock interrupts. This typically means an overclocking instability, failing CPU, or a bad BIOS/firmware setting. Parameters confirm core timeout: (0xa, 0x0, 0xffffcc80137c2180, 0x13) A minidump was saved: C:\WINDOWS\Minidump\012726-10968-01.dmp Stop 0x00000044 — MULTIPLE_IRP_COMPLETE_REQUESTS A disk/storage driver tried to complete the same I/O request twice, pointing to a faulty or buggy storage driver affecting \Device\HarddiskVolume3 (your C: system drive). Stop 0x00000052 (related to NTFS/filesystem) Also involving \Device\HarddiskVolume3. 🔴 Critical: NTFS Filesystem Corruption NTFS corruption events appeared across three drives: G: drive — by far the worst, with ~168 events including a confirmed Bad FRS (File Record Segment) — the Master File Table has a corrupted file record at reference 0x1000000000000. The system logged: "The Master File Table contains a corrupted file record. The name of the file is unable to determine." F: drive — 5 events H: drive — 2 events This is real, on-disk corruption. Files on G: may already be lost or unreadable. 🟠 Serious: 150 HAL (Hardware Abstraction Layer) Events An unusually high 150 firmware-level hardware events were logged. These are linked to: BIOS firmware F24 (most events) and F33 (newer, after a BIOS update) Status tagged as "Under Observation - More Data Needed" — Windows detected hardware behavior anomalies but couldn't conclusively categorize them yet 10 WHEABootErrorCount entries (hardware errors detected at boot) 4 WHEA (Windows Hardware Error Architecture) events — these are actual CPU/chipset/PCIe hardware fault reports 🟡 Audio Controller Failures 156 occurrences of "Audio Controller initialization failed." from the PaeDSPUSB provider — a USB audio device is repeatedly failing to initialize. Likely a faulty USB audio adapter or driver conflict. What to Do Immediately: Back up G: drive right now — it has active MFT corruption Run chkdsk G: /f /r (and F:, H:) from an elevated command prompt or recovery mode For the BSODs: 3. If you're overclocking (XMP/EXPO RAM profile, CPU OC), disable it — the 0x101 CLOCK_WATCHDOG is a classic overclock instability sign 4. Update to the latest BIOS (looks like you went from F24 → F33, which is good — stay current) 5. Run Windows Memory Diagnostic or MemTest86 — bad RAM can cause all of these symptoms simultaneously For the storage driver crash: 6. Check for storage controller driver updates (Intel RST or AMD SATA drivers) 7. Run CrystalDiskInfo to check S.M.A.R.T. health on all drives