Does Atmel look at crash dumps?

Go To Last Post
6 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Or could it be that Windows doesn't crash in Norway? ;)

I got another blue screen today. Atmel Studio was running, or rather it was just sitting there. I wasn't using it. My JTAGICE2 wasn't plugged in either. In fact I wasn't using anything. I left home for 5 hours. When I got back there was a blue screen.

Probably caused by Pool_Corruption
PROCESS_NAME: atmelstudio.ex

This doesn't prove it was the fault of atmel studio, but it seems every blue screen is associated with atmelstudio or the jtagice2 driver.

.

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have a JTAG-ICE MKII and JTAG-ICE3 plugged in at work all the time (as do most of us) and haven't seen anything similar. What version of Windows?

It might be worth uninstalling the Jungo USB drivers and reinstalling them just in case something there is a bit wonky.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
I have a JTAG-ICE MKII and JTAG-ICE3 plugged in at work all the time (as do most of us) and haven't seen anything similar. What version of Windows?

Same here usually Studio 6 is running with the tools attached from Monday to Friday without reboot. Since you describe a bluescreen I assume that you are running WinXP aswell?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm running Win7 SP1 with all the updates. I've had 3 blue screens. Two on this Win7 install and one on another Win7 install. They all happened when Studio 6 was running.

The one on the other Win7 install was the same as this one I reported in my first post.

The other one on this machine was in a Microsoft driver called usbser.sys.

Quote:
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8009aa0c00, Physical Device Object of the stack
Arg3: fffff800046b93d8, Functional Device Object of the stack
Arg4: fffffa8013e4db80, The blocked IRP

Debugging Details:
------------------

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa8013e4db80

DEVICE_OBJECT: fffffa8009aeb8f0

DRIVER_OBJECT: fffffa8009ae4970

IMAGE_NAME: usbser.sys

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

USBSER.SYS is the Microsoft provided kernel driver module that implements CDC-ACM (USB to Serial). If that's breaking there must be something else unstable in the system that's causing it, since that's completely unmodified by Atmel Studio 6.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yeah, thanks for reminding me. I plugged a USB to RS232 dongle into the back of the computer several weeks ago. It didn't work very well and I haven't used it since. I forgot it was still plugged in. It's not plugged in anymore.