format PE native
entry main

section '.text' executable readable
main:
    nop
    

Tyler, that code actually produces a native executable, not a native driver.

Take a look at this: http://board.flatassembler.net/topic.php?p=29031#29031

2.4.2 Portable Executable



To select the Portable Executable output format, use format PE directive, it
can be followed by additional format settings: first the target subsystem
setting, which can be console or GUI for Windows applications, native
for Windows drivers, EFI, EFIboot or EFIruntime for the UEFI. DLL
keyword following the subsystem setting marks the output file as a dynamic link
library. Then can follow the at operator and the numerical expression
specifying the base of PE image and then optionally on operator followed by
the quoted string containing file name selects custom MZ stub for PE program
(when specified file is not a MZ executable, it is treated as a flat binary
executable file and converted into MZ format). The default code setting for
this format is 32-bit. The example of fully featured PE format declaration:

format PE GUI 4.0 DLL at 7000000h on 'stub.exe'



To create PE file for the x86-64 architecture, use PE64 keyword instead of
PE in the format declaration, in such case the long mode code is generated
by default.


section directive defines a new section, it should be followed by quoted
string defining the name of section, then one or more section flags can
follow. Available flags are: code, data, readable, writeable,
executable, shareable, discardable, notpageable.
The origin of section is aligned to page (4096 bytes). Example declaration of PE section:

section '.text' code readable executable



Among with flags also one of the special PE data identifiers can be specified to mark the whole
section as a special data, possible identifiers are export, import,
resource and fixups. If the section is marked to contain fixups, they are
generated automatically and no more data needs to be defined in this section.
Also resource data can be generated automatically from the resource file, it
can be achieved by writing the from operator and quoted file name after the
resource identifier. Below are the examples of sections containing some special PE data:

section '.reloc' data discardable fixups
section '.rsrc' data readable resource from 'my.res'



entry directive sets the entry point for Portable Executable, the value of
entry point should follow.


stack directive sets up the size of stack for Portable Executable, value
of stack reserve size should follow, optionally value of stack commit
separated with comma can follow. When stack is not defined, it's set by
default to size of 4096 bytes.


heap directive chooses the size of heap for Portable Executable, value of
heap reserve size should follow, optionally value of heap commit separated
with comma can follow. When no heap is defined, it is set by default to size
of 65536 bytes, when size of heap commit is unspecified, it is by default set
to zero.


data directive begins the definition of special PE data, it should be
followed by one of the data identifiers (export, import, resource or
fixups) or by the number of data entry in PE header. The data should be
defined in next lines, ended with end data directive. When fixups data
definition is chosen, they are generated automatically and no more data needs
to be defined there. The same applies to the resource data when the resource
identifier is followed by from operator and quoted file name - in such case
data is taken from the given resource file.


The rva operator can be used inside the numerical expressions to obtain
the RVA of the item addressed by the value it is applied to.