I’ve written a small driver, which should run on a physical computer.
The current version of it was installed on numerous and various computers (old and new, all kind of OSs, laptops, PCs and servers).
But today i’ve encountered a BSOD while installing the driver on a server.
The bugcheck i’ve received was 0x7E, with the exception of a status_breakpoint. needless to say there is no breakpoint anywhere in the code, nor a kernel debugger is attached.
Also, an important information is that its the first time it is running on a multi-processor hardware.
I know there isn’t much information about the error, i just want to know if the fact the it is a multi-processor computer might cause that kind of error (or any error for that matter).
Connect a debugger to the machine or get the memory dump and run the
“!analyze -v” command to see where the breakpoint is (whose code does it
belong to).
On 16 May 2016 at 23:46, wrote:
> Hey, > > I’ve written a small driver, which should run on a physical computer. > The current version of it was installed on numerous and various computers > (old and new, all kind of OSs, laptops, PCs and servers). > > But today i’ve encountered a BSOD while installing the driver on a server. > The bugcheck i’ve received was 0x7E, with the exception of a > status_breakpoint. needless to say there is no breakpoint anywhere in the > code, nor a kernel debugger is attached. > Also, an important information is that its the first time it is running on > a multi-processor hardware. > > I know there isn’t much information about the error, i just want to know > if the fact the it is a multi-processor computer might cause that kind of > error (or any error for that matter). > > Thanks. > > > — > NTDEV is sponsored by OSR > > Visit the list online at: < > http://www.osronline.com/showlists.cfm?list=ntdev> > > MONTHLY seminars on crash dump analysis, WDF, Windows internals and > software drivers! > Details at http: > > To unsubscribe, visit the List Server section of OSR Online at < > http://www.osronline.com/page.cfm?name=ListServer> ></http:>
You should be able to attach a debugger to a physical server. The only thing which would prevent you is if none of the physical ports support debugging. What you can use depends both on the target OS and the hardware.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-608507- xxxxx@lists.osr.com] On Behalf Of maorh11+xxxxx@gmail.com
Sent: 17 May 2016 08:10
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] BugCheck 0x7E with STATUS_BREAKPOINT
Thanks for your reply.
I can’t attach a debugger to the machine, since it is not a VM. it’s a
physical server.
NTDEV is sponsored by OSR
Visit the list online at: http: > > MONTHLY seminars on crash dump analysis, WDF, Windows internals and > software drivers! > Details at http: > > To unsubscribe, visit the List Server section of OSR Online at > http:</http:></http:></http:>
Given that you say you’ve run this on ‘numerous and various’ computers, I find it slightly difficult to believe that this has never been installed on a multi-processor machine before.
Please clarify exactly when the BSOD occurs: actually during the installation of the driver? If not, when? (e.g. before or after next reboot).
Also, it would help us if you stated exactly how you are installing the driver (e.g. are you using an MSI, a .inf, or some other installation program) and the version of Windows you are installing on.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-608472- xxxxx@lists.osr.com] On Behalf Of maorh11+xxxxx@gmail.com
Sent: 16 May 2016 21:46
To: Windows System Software Devs Interest List
Subject: [ntdev] BugCheck 0x7E with STATUS_BREAKPOINT
Hey,
I’ve written a small driver, which should run on a physical computer.
The current version of it was installed on numerous and various
computers (old and new, all kind of OSs, laptops, PCs and servers).
But today i’ve encountered a BSOD while installing the driver on a
server.
The bugcheck i’ve received was 0x7E, with the exception of a
status_breakpoint. needless to say there is no breakpoint anywhere in
the code, nor a kernel debugger is attached.
Also, an important information is that its the first time it is running
on a multi-processor hardware.
I know there isn’t much information about the error, i just want to
know if the fact the it is a multi-processor computer might cause that
kind of error (or any error for that matter).
Sorry for the late response, the server is not very reachable to me.
1 correction to what i’ve said: the driver did work on a multi-processor server before with no problem.
I got a mini dump now, and the call stack is:
nt!KeBugCheckEx
…
…
nt!KiBreakpointTrap+0xf4
Driver!__security_init_cookie+0x2e
Driver!DriverEntry+0x5
so it seems like the crash occurs before anything runs in the driver.
What else can i check in order to solve this issue?
This indicates you built the driver for a newer version of windows and you are running downlevel. Iirc, this happens when you target w8 or later as you get a new bigger over flow implementation that requires os support. What os did you target during build and what os are you loading on?
Sent from my Windows 10 phone
From: maorh11+xxxxx@gmail.commailto:maorh11 Sent: Thursday, May 26, 2016 7:33 AM To: Windows System Software Devs Interest Listmailto:xxxxx Subject: RE:[ntdev] BugCheck 0x7E with STATUS_BREAKPOINT
Hey,
Sorry for the late response, the server is not very reachable to me. 1 correction to what i’ve said: the driver did work on a multi-processor server before with no problem.
I got a mini dump now, and the call stack is: nt!KeBugCheckEx … … nt!KiBreakpointTrap+0xf4 Driver!__security_init_cookie+0x2e Driver!DriverEntry+0x5
so it seems like the crash occurs before anything runs in the driver.
What else can i check in order to solve this issue?
oh… that makes (some) sense.
i’m using WindowsKernelModeDriver8.1 toolset to build the driver and the problem occurs on Windows server 2008R2.
But i’ve also checked that driver on win7 (which 2008R2 matches to).
i’m using WindowsKernelModeDriver8.1 toolset to build the driver and the problem
occurs on Windows server 2008R2.
But i’ve also checked that driver on win7 (which 2008R2 matches to).
That does not answer Doron’s question correctly. You can use “WindowsKernelModeDriver8.1 toolset” to build the driver for Win 7 (Server 2008 R2), Win 8 (Server 2012) and Win 8.1 (Server 2012 R2). So, what did you build for and where are you trying to load the driver ?