http://tinypic.com/view.php?pic=2lm6jpf&s=7 Hi, I'm getting the bsod of the image above. I'm getting it as I'm running tests with the kernel (file) transaction manager, i.e. with TxF/Transactional NTFS. Due to the problem, it doesn't manage to write anything such as a debug dump to disk. The error codes are fairly specific and unlike the average BSOD, they aren't googleable. Help appreciated.

Hello, Bug check code 0x3B: http://msdn.microsoft.com/en-my/library/ff558949(v=vs.85).aspx please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps like c:\windows\minidumps) and post a link here. If you want to read dump files without my help, use Windbg and refer to this Microsoft article: http://support.microsoft.com/kb/315263 Else, you can try to update your graphic card driver and check again. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

Hi, Thanks for the link. As I wrote, it doesn't write a debug dump due to the nature of the error (I assume). I have crash dumps turned on in system settings. I am the programmer causing the problem by using p/invoke to talk to the kernel transaction manager, although I have no idea where I am sending bad data. Is there a way to know when one is sending bad data to the kernel? Here is what I am sending with: https://github.com/haf/Castle.Services.Transaction/blob/develop/src/Castle.Services.Transaction/Internal/NativeMethods.cs Any ideas?