Blue Screen of Death

[roosterdiesel]

:omg:

Flashing Chip....

Followed instructions installing burner drivers and everything looked fine.

THen blues screen with an error in the Slabser.sys I had to ok a
driver with that in it if I remember correctly. Did it twice on different USB ports.

Checked for BIOS update with no luck. Said I may need to turn off bios shadowing or cacheing.

BTW...its a 4 year old Dell Inspiron 9100 with XP. Any ideas?


Thanks!

[Power Hungry]

Uh oh... That's not good. In 4 years, I can't recall anyone ever getting the BSOD with those drivers.

At this point are you able to plug the unit in without the computer crashing, or does it crash as soon as the USB is plugged in? We might need to completely remove the drivers and reinstall them.

This is probably best handled by phone so let me know when would be a good time.

FWIW - I've used Dells exclusively for the last 5 years with both XP and now Vista and I have never had any problems so I doubt the issue is with the computer itself. It's probably something small and should be easy to fix.

[Jackpine]

Kind of reminds me of when I got a BSOD updating the firmware and version on what was then my Edge (now a Gryphon). Interestingly, my PC is also a Dell - an XPS 410 running XP.

I simply started over, after rebooting, and everything was fine. But, I had my "heart in my mouth", worrying if I had "toasted" the Edge.

BSODs are so rare now, we've almost forgotten what they look like.

- Jack

[Power Hungry]

Honestly, can't remember the last time I saw one either. In fact, how's this for cool?

Server Statistics for \*********
Statistics since 10/5/2008 7:45 PM


That was the last time I rebooted the server, and that was only because I moved it.

[roosterdiesel]

OK.....I can plug in the burner to the computer and energize it, flashes lights properly then it BSOD'd when I was moving the mouse to click the program button. Did it twice on different USB ports. This was a couple days ago.


Last night I tried again after Updating windows, was working fine, erased the chip and got the 1st position programed then BSOD.


I'll call again next week when I have a chance and Bill's not busy.

[secondarychaos]

Originally Posted by Groovy Chick

Antonio,

Are you using a 9-pin serial mouse or a USB mouse?

Sorry for the Hijack, but,
I gotta say, Man I love computers
Using a different type of mouse can interfere with program drivers?
Thank you Mr. Gates

[roosterdiesel]

Just wanting to come on thank Bill and Corey for the great customer service! Oh....and it's not the mouse....it's kinda flattened though since it's touchpad.


We were able to reinstall drivers but to no avail....I'm typing this recovering from BSOD.



Bill should have me operational this weekend! Does he ever sleep?



Antonio

[Jackpine]

I don't think he sleeps at all, Antonio.

But, it HAS to be some conflict with one or more files (I'd bet on .dlls) on your PC. I think Bill codes a lot in Visual Basic. I wonder if you two have the same link libraries, or, if your PC is using a .dll in a shared directory that doesn't match the one needed by the device.

On a similar note, I have had two laptop CD drives that BSODed on me now and then when I tried to install something from a CD. One of them got so bad that I finally resorted to copying the files from it to a USB drive and then I'd install the program via USB. Interestingly, the second laptop's CD/DVD drive completely gave up the ghost a while back, so now I'm totally down to USB drive installs on it. I gave the other laptop to my Sister, and she rarely installs anything, so it's fine for her.

- Jack

[Power Hungry]

Jack,

From what I gathered from Antonio, it appears that there is some conflict between the USB Drivers themselves and the mousepad. I may be wrong about the mousepad being involved in the conflict, but it's definitely related the the Silicon Labs USB drivers as that's what comes up on the BSOD.

What I am going to try to do is add a static COM port parameter to the command line so I can bypass the COM port polling procedure. I have a feeling this will resolve the issue.

What's funny is his laptop is a Dell Inspiron and so is on of mine. Of course, I have no problems.

We'll get it nailed down. It's always something, eh?

[Jackpine]

Originally Posted by Power Hungry

Jack,

From what I gathered from Antonio, it appears that there is some conflict between the USB Drivers themselves and the mousepad. I may be wrong about the mousepad being involved in the conflict, but it's definitely related the the Silicon Labs USB drivers as that's what comes up on the BSOD.

What I am going to try to do is add a static COM port parameter to the command line so I can bypass the COM port polling procedure. I have a feeling this will resolve the issue.

What's funny is his laptop is a Dell Inspiron and so is on of mine. Of course, I have no problems.

We'll get it nailed down. It's always something, eh?

OK - I bet you're right and the first laptop I was telling you about was also a Dell Inspiron (the second one is an Averatec). I didn't recall at all what was stated in the BSODs, but since the CD reader is a peripheral device, I'd be voting for the same kind of conflict. On the Inspiron, I was able to disable the touchpad and use a portable USB mouse (which had different drivers, of course). I did this for a while until I got used to the touchpad. I wonder if this could be an easy fix for the problem Antonio's having if your COM port idea doesn't work out?

- Jack