Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

System bugchecks on break instruction (0x80000003)

Dejan_MaksimovicDejan_Maksimovic Member - All Emails Posts: 224

This happens quite often, almost always... WinDBG is connected to a VMWare Windows 7 machine, that is set up with VirtualKD.
If either my code has a DbgBreakPoint() or I get a debug break from another driver, I cannot continue execution after that point. F5/g, Step Into/Over/Out, Run to Cursor - all cause a bugcheck noting that 0x8000003 (debug break) exception was thrown.

Any ideas what could be wrong?

Comments

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,123

    I use VKD and Windows 7 and haven't seen this...Is it a recent update of Win7? Which versions of VMware and VKD are you using?

    -scott
    OSR

  • Dejan_MaksimovicDejan_Maksimovic Member - All Emails Posts: 224

    I did not get this message in my e-mail, therefore apologies for a late reply.
    This is VMKS 9-12 (all had this issue). I cannot test any newer at the moment.
    VKD is 3.0, latest publicly available release.

    This happens on more than one Win7, but I think they were last updated about a year ago (it's a VirtualKD VM, for driver testing only, it has to be ready :))

  • Dejan_MaksimovicDejan_Maksimovic Member - All Emails Posts: 224

    Update: also happens on a Win10 VM, but less often. This is the latest VMWKS that will run on my Nehalen laptop, so I cannot test VKS14. (ergonomics first :))

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,123

    Weird. I recently upgraded from VMWKS 12 to 15 and use the latest VKD. Never have this problem across multiple workstations (and targets of XP all the way through 19H1). You're cursed...

    -scott
    OSR

  • Dejan_MaksimovicDejan_Maksimovic Member - All Emails Posts: 224
    via Email
    I either figured a workaround, or was stupid all this time...

    F5 (g) causes the bugcheck, but gh (handle exception) does not. I
    would not have figured ir with any logic, considering the SAME
    assertion/break/etc. sometimes goes on, sometimes bugchecks after F5
    (and also bugchecks on one OS, but not on another).

    On 4/18/19, Scott_Noone_(OSR)
    wrote:
    > OSR https://community.osr.com/
    > Scott_Noone_(OSR) commented on System bugchecks on break instruction
    > (0x80000003)
    >
    > Weird. I recently upgraded from VMWKS 12 to 15 and use the latest VKD. Never
    > have this problem across multiple workstations (and targets of XP all the
    > way through 19H1). You're cursed...
    >
    > --
    > Reply to this email directly or follow the link below to check it out:
    > https://community.osr.com/discussion/comment/293523#Comment_293523
    >
    > Check it out:
    > https://community.osr.com/discussion/comment/293523#Comment_293523
    >
  • Dejan_MaksimovicDejan_Maksimovic Member - All Emails Posts: 224

    Hmm, spoke too soon :( This works in case I want to "gh" the breakpoint, however, if I want to step into the code, it still bugchecks :(
    How do I tell the OS the exception is handled, so I can step into the code, i.e. a "step into, with exception handled", like "gh" does for "Continue with exception handled"?

    Again, this does not happen always, but way more than I can afford to "retry agian".

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA