Using my ever faithful err.exe tool: 

http://www.microsoft.com/en-us/download/details.aspx?id=985

 


C:\Users\KeithGa>err 0xc0000359

# for hex 0xc0000359 / decimal -1073740967 :

  STATUS_INVALID_IMAGE_WIN_32                                   ntstatus.h

# The specified image file did not have the correct format,

# it appears to be a 32-bit Windows image.

# 1 matches found for "0xc0000359"

 

Whoops, did you load a x86 binary into a x64 image? (or vise versa).

 

Back in the day, Intel used the *same* *.inf file for the x86 and x64
versions of the AHCI driver, the only way to know for sure *which* driver
you were loading was to crack open the *.sys file and look inside. We added
some deep binary inspection to MDT to address it. 

 

If you perform any offline loading of driver packages into your image, you
might get this problem.

 

Yet another reason why I generally recommend creating images in a VM, and
injecting drivers at install time.

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of [email protected]
Sent: Tuesday, July 29, 2014 4:22 PM
To: [email protected]
Subject: RE: [MDT-OSD]

 

Do you have the mass storage drivers injected?

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Séguin, Mario
Sent: Tuesday, July 29, 2014 15:28
To: [email protected] <mailto:[email protected]> 
Subject: RE: [MDT-OSD]

 

Hi Guys,

 

When I image an HP 8560P with our windows 8.1 image i get a BOD right after
rebooting the first time after the image is dropped.

 

 

The operating system couldn’t be loaded because a critical system driver is
missing or contains errors.

 

File: \Windows\system32\Drivers\Jraid.sys

Error code: 0xc0000359

 

 

Anyone knows how to fix this?

 

thanks


Reply via email to