BSOd ffom USB card reader

[KTac]

I have been running Windows 7 Enterprise 64-bit RTM happily for a few weeks now. All of a sudden my mmachine freaked out. I have an older USB flash memory card reader mounted in a 3.5" bay in the front of my computer. I have had no problems with it conected previously. The other day I needed to put some files on an SDHC card. The aforementioned reader isn't compatible with SDHC so I plugged in a second card reader, a newer external one that supports SDHC. As soon as I plugged it in, BANG! BSOD.

I was running Vista 32-bit prior to 7 with the exact same system configuration except that I added two more gigs of the exact same RAM when upgrading to 7. Both card readers worked fine under Vista no matter whether the were both connected at the same time or not.

Now if I try to start my computer with either one of the two card readers I get the same blue screen while Windows is loading. If I plug either of the card readers in While Windows is running it crashes with the same blue screen.

I am now stuck without the ability to read any flash cards. What really baffles me is that I could understand if Windows 7 didn't like the newer card reader for whatever reason but why won't things work with just the orginal card reader hooked up that I had in the first place when everything was fine before.

What could possibly be going wrong?

The stop message from the blue scren is:
IRQL_NOT_LESS_OR_EQUAL
STOP: 0x0000000a (0x0000000000000138, 0x000000000000000002, 0x0000000000000000, 0xFFFFF80002C27DCC)

 

[zigzag3143]

You might have corrupted a driver. check device manager to see if the USB hub and roots are all still working properly

Ken


edit: if you want zip the dump file (*.dmp) located in c:\windows\minidump and upload it for us to debug

 

[KTac]

Device manager shows all USB root hubs and controllers are working fine. Attached is the minidump file from the first crash when this whole mess started.

 

[rstrader]

The exact same thing is happening here. It started in Vista 64 and carried on into the upgrade to Windows 7 64. I've tried different card readers, both internal and external. I've tried different versions of the chipset driver X58.

I feel like it's the usb driver, but I haven't tracked it down yet. Every other usb device works fine... printers, keyboard, mouse, headset etc.

Stumped.

 

[Tews]

Hi rstrader and welcome to the forums!!

Please.. Dont hijack threads, it makes it too confusing when answering questions. Start a new thread specific to your problem ... and remember to fill out your system specs when you do..

 

[rstrader]

Not only did I not hijack the thread... I feel that two people having the exact problem with different specs will help to find a solution quicker. I could literally cut and paste the original problem into a new thread and it would be a perfect description of my problem.

If I remove the card reader the machine boots. If I hook it up BSD. If I hook it up with Windows running BSD. If I hook it up to a D-Link hub Windows recognizes (dings) but doesn't show any new device.

During boot while initializing the USB devices it shows the card reader as 4 mass storage devices.

Help!?

 

[Antman]

Not only did I not hijack the thread... I feel that two people having the exact problem with different specs will help to find a solution quicker. I could literally cut and paste the original problem into a new thread and it would be a perfect description of my problem.

If I remove the card reader the machine boots. If I hook it up BSD. If I hook it up with Windows running BSD. If I hook it up to a D-Link hub Windows recognizes (dings) but doesn't show any new device.

During boot while initializing the USB devices it shows the card reader as 4 mass storage devices.

Help!?

Attach a dump file. Then, we can get this moved to another thread with a valid starting point.

 

[rstrader]

For whatever reason I don't have a dump file. I have boot logging enabled and have that, but I know where it crashes, just not why. Is there a procedure involved in creating a *.dmp file?

 

[rstrader]

Success

After much mucking around I have found my problem.
I did a fresh install of Windows 7 Professional (available to people that have multiple licenses and software assurance). The card card reader worked fine. The problem is Acronis Backup and Recovery 10. When I installed my backup software the BSOD was back. Uninstall and the card reader returned. I'll post more when I try the solution from the Acronis forum.

 

[Antman]

After much mucking around I have found my problem.
I did a fresh install of Windows 7 Professional (available to people that have multiple licenses and software assurance). The card card reader worked fine. The problem is Acronis Backup and Recovery 10. When I installed my backup software the BSOD was back. Uninstall and the card reader returned. I'll post more when I try the solution from the Acronis forum.

Which brings us back to this...

Not only did I not hijack the thread... I feel that two people having the exact problem with different specs will help to find a solution quicker. I could literally cut and paste the original problem into a new thread and it would be a perfect description of my problem.

Deferring to your wisdom, please provide the OP with a link to your Acronis forum thread. Unless, of course, you were completely wrong and 100% out of line in your reponse to the professional guidance provided by Tews.

Perhaps you could literally cut and paste the Acronis solution.

 

[Lordbob75]

I looked at the dump for the OP, says it is probably caused by snapman.sys....
What the hell is that?

~Lordbob

 

[zigzag3143]

snapman.sys and acronis have a known BSOD history. there is an update that fixes its cause

ken

 

[Lordbob75]

snapman.sys and acronis have a known BSOD history. there is an update that fixes its cause

ken

But what is snapman.sys?

And good to know as well, thanks.

~Lordbob

 

[Antman]

"The SnapAPI module is in charge of all I/O operations on the hard disk of Acronis software working in Windows. It also allows to create backups under running Windows with an unlimited number of files open for reading and writing without the necessity to reboot the computer."

kb.acronis.com/content/1512

 

[Lordbob75]

"The SnapAPI module is in charge of all I/O operations on the hard disk of Acronis software working in Windows. It also allows to create backups under running Windows with an unlimited number of files open for reading and writing without the necessity to reboot the computer."

kb.acronis.com/content/1512

Interesting... So it is like a plug in for Acronis that causes this?
That seems... irresponsible.

~Lordbob

 

[Antman]

Interesting... So it is like a plug in for Acronis that causes this?
That seems... irresponsible.

No more so than any other compatibility issue. If Acronis never labeled it Windows 7 certified.

 

[Lordbob75]

Interesting... So it is like a plug in for Acronis that causes this?
That seems... irresponsible.

No more so than any other compatibility issue. If Acronis never labeled it Windows 7 certified.

Fair enough. I figured this occurred on Vista as well.

~Lordbob

 

[rstrader]

Not a problem. My card reader is back running perfectly. This fix obviously only applies to systems running the current version of Acronis Backup and Recovery.

Acronis Backup & Recovery 10 and BSOD Issue | Forums

Hello all,
We were able to get a workaround for common BSOD issue after the installation of the latest (11105) build of Acronis Backup & Recovery.
If you faced the same BSOD as we can see here, you can do the following to fix this issue:

• Boot into Safe Mode and remove contents of SnapAPI drivers according to this article
• Boot in Normal Mode and install the latest build of our program. You can download all the necessary files from update section in your account
• Do not reboot your PC after the Installation
• Install the new version of SnapAPI 468
• Reboot your PC

Thank you.
__________________ Alexander Nikolsky
Acronis Customer Central | Acronis Backup Software

 

[KTac]

A HA! I had just installed Acronis Backup & Recovery 10 a few days before I started having this problem. This very well may be the culprit. rstrader please provide the link to the thread on the Acronis forum. Thanks.

Oops, sorry, got too excited. I was replying to a post on the first page and didn't check the second.

 

[KTac]

Am I missing something here. Build 11105 is the latest bulid correct?

The istructions say if you have this problem after installing the latest build 11105 then follow the steps to remove the SnapAPI drivers, then it says to install latest build and then the latest SnapAPI v468.

I'm already running build 11105. Does that mean I should reinstall build 11105 after performing the steps to remove the SnapAPI drivers? Wouldn't that just put the old ones right back? Or is there a build newer than 11105 that I'm not seeing?

Or, since since I'm already running build 11105 which appears to be the latest, do I just follow the the steps to remove SnapAPI and then just install the newer v468?