Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

BackyardEOS causing blue screen crash


NeilW

Question

Hi all,

I'm running BackyardEOS on a laptop under Windows 7 64bit with 8Gb RAM attached to a Canon 70D. The last three times I've run BYE I've had Windows crash out to a blue screen mid session, then reboot. The blue screen doesn't last long enough for me to get any useful information from it.

Has anyone else had this happen. and/or can anyone offer suggestions to locate the cause and fix it?

Thanks,

Neil Walter
Adelaide, South Australia
Link to comment
Share on other sites

  • Answers 8
  • Created
  • Last Reply

8 answers to this question

Recommended Posts

Actually, BSODs are mostly at the Driver-level than at the App-level, but are triggered as equally by Hardware or Software Issues (the Issue just needs to be serious enough that Microsoft decided the OS couldn't reliably continue without an immediate reboot).  The issue also needs to be related to the Laptop, so unless the DSLR is triggering an error in the USB Driver, it is unlikely the Culprit.

 

The easiest way to isolate the Issue is to try to swap-out components until the Issue disappears.  

This would mean to try:

different USB Cable

different USB Port

different Software - use Canon's EOS Utility to trigger a set of equivalent Bulb Exposures and to have them downloaded to the Laptop

different PC - use BYE to perform a set of equivalent Bulb Exposures (confirm with Guylain whether you can install this License of BYE onto a different PC for purposes of this Debugging Test)

 

Note: None of this Debugging need be done at Night, nor when attached to your Scope (unless you also use ASCOM or other software to manage the Mount while Imaging with BYE).  You might want to test with PHD running to a Camera Simulator - if PHD is part of your normal AP Imaging Setup.

Link to comment
Share on other sites

I ran the WhoCrashed program, and it returned the following from the crash during imaging last Friday:

 

On Fri 21/11/2014 12:16:24 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\112114-54475-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x19 (0x3, 0xFFFFF8A0020A23A0, 0x30002E00300036, 0xFFFFF8A0020A23A0)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Not sure if that tells you anything, but I'll monitor the situation and see if the problem continues.

 

Neil

 

I also sufferd the Blue Screen of Death earlier this year.  BYE was not the issue.  A corrupt file in the Windows 7 Professional operating system did it.  Seems that a recent Windows update was corrupt.  Restoring to an earlier update level retruned everything to normal.  Then carefully monitoring Windows updates, including a now clean copy of the corrupted update, got me back to the latest levels. 

Link to comment
Share on other sites

I ran the WhoCrashed program, and it returned the following from the crash during imaging last Friday:

 

On Fri 21/11/2014 12:16:24 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\112114-54475-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x19 (0x3, 0xFFFFF8A0020A23A0, 0x30002E00300036, 0xFFFFF8A0020A23A0)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Not sure if that tells you anything, but I'll monitor the situation and see if the problem continues.

 

Neil

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use