BSOD crash

So... this is a brand new computer last month...Clean install of a Retail Windows 7 Ultimate x64 on an Intel SSD.
A couple of times now, I leave the computer (and it's not really doing anything computing-wise)... and when I return an hour or more later - it's sitting on the BSOD..
This is the first time it's created a dump file.
I downloaded and installed the Windows Driver Kit Version 7.1.0... to get the debugger... and it seems to be pointing at Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )

Can anyone help?

Majic31 said:

So... this is a brand new computer last month...Clean install of a Retail Windows 7 Ultimate x64 on an Intel SSD.
A couple of times now, I leave the computer (and it's not really doing anything computing-wise)... and when I return an hour or more later - it's sitting on the BSOD..
This is the first time it's created a dump file.
I downloaded and installed the Windows Driver Kit Version 7.1.0... to get the debugger... and it seems to be pointing at Ntfs.sys ( Ntfs!NtfsDeleteScb+108 )

Can anyone help?

It is extremely difficult to analyze just one crash as there is no trend to follow and that it the case with yours.

It is a memory exception caused by as as yet un-named driver. I would suspect the Atheros Bluetooth drivers as there are far too many of them.

ALSO Please remove sptd.sys
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller http://www.duplexsecure.com/en/downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place. http://www.magiciso.com/


I would run driver verifier to find which driver is the true cause

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Majic31 said:

Firstly - Thank You for the quick response. I appreciate it.
I am sorry for the lack of info (only 1 dmp file)...but as I said - although it crashed a couple of times - it only created the one file.

This morning I received the e-mail notification from SevenForums and began following your instructions.

I created my restore point and system repair disc.

I followed the directions and activated the verifier.exe program as directed.

Thru 3 attempts - it never got farther than the "starting windows" screen.

I went into Safe mode and restored.

Then I came onto the forum and noticed some additional instructions which weren't contained in the e-mail - namely about the Daemon Tools and removing the sptd.sys driver.

I uninstalled Daemon Tools, used the uninstall for the sptd.sys and even installed the MagicIso (thank you very much for that link)

Then I created another restore point and activated the verifier.exe program.

This time it booted into Windows and windows ran - but extremely slowly. The only consolation was it didn't run long before it BSOD'd on me - several times.
I wanted to include the dmp files, but apparently when I did the system repair - it deleted them.

I will have to repeat the process so I can generate more dmp files to analyze. I hope it doesn't crash before I can copy them to another location - and hopefully save them.

EDIT - I have now included the original dump file and 6 new ones created while running verifier.exe...
(btw - Did I mention how S-L-O-W the machine runs while verifier is running??? Firefox usually takes a couple of seconds from the time I click on it, until I'm online on my home page. It took 86 seconds for the program to start and over another minute for the webpage to open...)

Good news bad news.


All of the verified DMP's point to mcdbus.sys which is I am afraid the driver for MagicISO. For some unknown reason your system hates it. I would remove it


After removing magicISO let verifer run to see if we can catch the original culprit

Ken

OK - I have uninstalled both Magic Disc (the freebie) and Magic Iso (the one I paid for - not much chance getting a refund when they've sent me a serial # and registered me.... oh well - but I do still need an ISO manager/emulation - any other suggestions)...

I have created another restore point (after uninstalling MagicIso)... and am now running verifier.exe...

It's already running much longer than any of the other "verifier" times

I'll let you know if/when it crashes...

Again - I can't thank you enough for the assist...

Well, after running for 48hrs with only one crash (dmp file blamed my Acronis non-stop backup - which I uninstalled after restoring my system)...it would appear my problems lay with the Daemon Tools driver...

Other than running painfully slow - everything ran beautifully without crashing.

I am now looking to see what drive emulation software I can get that is compatible with Win 7 64bit....

Again, zigzag3143 thank you very much for your assistance.

Majic31 said:

Well, after running for 48hrs with only one crash (dmp file blamed my Acronis non-stop backup - which I uninstalled after restoring my system)...it would appear my problems lay with the Daemon Tools driver...

Other than running painfully slow - everything ran beautifully without crashing.

I am now looking to see what drive emulation software I can get that is compatible with Win 7 64bit....

Again, zigzag3143 thank you very much for your assistance.

My pleasure and glad to see you are working.


Ken

Majic31 said:

I am now looking to see what drive emulation software I can get that is compatible with Win 7 64bit....

If you're looking for a simple, lightweight, virtual drive replacement for Daemon Tools, You could try the Free DVDFab.

And you're not alone. MagicISO gave me my one and only unintentional BSOD in the two plus years I've been running Windows 7.