Share via

BSOD error - KMODE EXception not handled

Anonymous
2022-09-12T09:29:25+00:00

I'm close to tears - help needed.

I've been able to update most of my computers to Win 11 - but not this one, an ASUS PN-51. I've tried close to 20 times but it goes down every time artound 48 pct. I've rund sfc/scannow, dism restorehealth, chkdsk, all drivers update according to devicemanager and driver booster. I've been able to get to the different logfiles but can't decipher them as to where the problem is located,. I have an idea it might be cionnected to this

MOUPG A previous StudyID was [not restored]

2022-09-12 10:04:50, Info MOUPG SetupManager: Reporting Data - DataId = [22], Value = [0]

2022-09-12 10:04:50, Info MOUPG SetupManager: User Rollback Mode Detected

2022-09-12 10:04:50, Warning MOUPG SetupManager: Error retrieving setup platform result: [0x80070002]

2022-09-12 10:04:50, Info MOUPG SetupHost: Reporting post reboot event -> [0xC1900101, 0x30018]

2022-09-12 10:04:50, Warning MOUPG SetupNotify::ReportEvent - Report ID or Event Reporter not available.

2022-09-12 10:04:50, Info MOUPG SetupHost: Tracing post reboot failure event

2022-09-12 10:04:50, Info MOUPG CSetupDiagnostics: Tracing Data [CUSTOM] -> [WindowsUpdateFailure] -> [Win10UA:VNL:URL::<1.4.19041.1703>:<1>:{DF96E1FE-46A8-4D59-8F62-52BEC5086F5A}:[10.0.19044]:[2]][4e2c66f5-9f45-4e18-aff3-4e322b567a1f][62dc356d-49b9-43d2-a16f-9c6ed39018b7][][0x1]

2022-09-12 10:04:50, Info MOUPG **************** SetupHost Logging End ****************

2022-09-12 10:04:50, Info SP ExecuteCommandFromValue: Command line returned result: 0x00000000

2022-09-12 10:04:50, Info SP Attempting to stop the telemetry

but I'm not able to see what this means.

As I'm not so technically minded that I can use the debuggers I hope I can get help from here -I want to use only one Windows platform from now on - Win 11.

I keep my fingers crossed that I soon can be solely on Win 11.

erik_dk - writing from denmark

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

11 answers

Sort by: Most helpful
  1. Anonymous
    2022-09-12T12:02:02+00:00

    I'll try to repeat the procedure.

    yours erik marcussen

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-09-12T11:56:00+00:00

    Hi again

    I think I have tried to set up the system as to produce minidump-files as far as I have read instructions on the net. But I try to alter some settings again to produce a new memorydump

    Was this answer helpful?

    0 comments No comments
  3. DYARI BARHAM 34,936 Reputation points Independent Advisor
    2022-09-12T11:28:32+00:00

    Hi erik_dk,

    Thanks for sharing the files.

    The only minidump file did not name any driver only indicates ntkrnlmp.exe which is a Windows component that means something else drove the system to a fault or it could be a memory corruption that usually happens due to driver incompatibility.

    Kindly check C:\Windows and search for MEMORY.dmp file which is a huge file.

    If it is not available, please wait until your computer crashes and produces other minidump files.

    Regards,

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-09-12T10:55:07+00:00

    Hi Dyari

    Thank You for coming back to me. I've uploaded all the relevant information I've been able to locate and have uploaded it to my OneDrive at ******@live.dk

    Link should be one of these.

    https://1drv.ms/f/s!AsNi1asEI0damnmfmEP2Px75peZQ

    https://1drv.ms/u/s!AsNi1asEI0damnmfmEP2Px75peZQ?e=jdllg6

    There was no Minidump in the minidump-folder.

    I'll be happy to supply with further information if needed.

    yours erik marcussen

    Was this answer helpful?

    0 comments No comments
  5. DYARI BARHAM 34,936 Reputation points Independent Advisor
    2022-09-12T10:10:42+00:00

    Hi erik_dk,

    I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

    Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

    Regards,

    Was this answer helpful?

    0 comments No comments