BSOD while doing various things error d1

[thrashmagazine]

Hey all, figured I would see if anyone could help out on this one. Basically at random times with random things going on (gaming, nothing, browsing web, desktop) my computer will blue screen (2-5 times a week). I built the computer in November, parts list is below:

OS: Windows 7 x64 Ultimate (Windows Completely Up to Date)
Case: Lian Li PC-9F (Mid-Tower)
Mobo: ASRock Z68 Extreme4 Gen3
CPU: Intel i7 2600k Sandy Bridge
GPU: EVGA SuperClocked 015-P3-1582-AR GeForce GTX 580 (Fermi) 1536MB 384-bit GDDR5 PCI Express 2.0 x16
RAM: 16GB Ripjaw X Series DDR3 1866
PSU: SeaSonic X Series X-850
HD1 (Windows): 128GB Crucial M4 SSD SATA III
HD2 (Installs): 500GB Seagate Barracuda 7200RPM SATA II
HD3 (Files): 2TB WD Cavier Black 7200RPM SATA II

Nothing is overclocked, although as a test for the BSOD, I have increased my VTT Voltage to 1.129 (it was defaulted to 1.05). My RAM is set to Auto in BIOS (but verified all timings were match to the RAM spec). I am using my RAM's profile of 1866 (however got a BSOD when I was testing it at 1333).

Things I have done to test what could be going on:

Ran memtest86+ (came back 100% after 7 hours (5 passes I think))
Under clocked my 1866 RAM down to 1333 (EVGA recommended as a test), still BSOD so reverted back
Ran memtestG (came back 100% ok after re-seating my graphic card)
Re-installed nVidia drivers (used Driver Sweeper in Safe Mode to clear out first)
Ran various graphic card benchmarks (no issues) (OCScanner, FurMark)
Ran Intel Burn Test on Max for 10 iterations with no failure (couple hours)
Ran HDTuner on my SSD, no issues

I guess I am not really sure how to read my minidump properly to be able to debug it, hoping someone on here could point me in a direction. I am assuming this is something driver related, I am just not sure unfortunately.


I noticed I have a "Warning" on an unknown device but I have no idea how to tell what it is (I do know its USB related but not sure what set installed it and the HArdware ids and so forth give me nothing. Also, it says in the Perfmon I have no Anti-Virus, I have AVAST running.

 

[thrashmagazine]

Assuming it has nothing to do with the USB unknown device, I figured out what it is, now I just cant get the driver to install through windows Its my AFT PRO-35U (Card Reader). I assumed it was fine since USB on it works fine, but my cards do nothing. That being said, it explains the unknown device in the PerfMon, any help on the BSOD appreciated.

 

[thrashmagazine]

hoping someone might have some idea what could be happening.

Today I ran chkdsk on all my attached hard drives (no issues found).

Driver Verifier is next up, will report back on this, any ideas would be appreciated beyond this though.

 

[thrashmagazine]

I was so excited to receive a different BSOD while running Driver Verifier (although once it rebooted it came back up ok so I can't get it to keep happening)...

Any thoughts on this one guys?

 

[thrashmagazine]

I plan to test a memtest86+ for each stick of RAM I have, it will unfortunately be a long test but hoping I can figure something out. Anyone have any ideas?

 

[zigzag3143]

I was so excited to receive a different BSOD while running Driver Verifier (although once it rebooted it came back up ok so I can't get it to keep happening)...

Any thoughts on this one guys?

Driver verified and Related to MBfilt64.sys Audio Driver from Creative Technology Ltd.

I would remove to test and if you have to re-install it I would find the newest version to re-install.

 

[thrashmagazine]

I was so excited to receive a different BSOD while running Driver Verifier (although once it rebooted it came back up ok so I can't get it to keep happening)...

Any thoughts on this one guys?

Driver verified and Related to MBfilt64.sys Audio Driver from Creative Technology Ltd.

I would remove to test and if you have to re-install it I would find the newest version to re-install.

Thank you for the reply, I am not really sure what you are saying though. I don't have any creative technology drivers that I know of (Realtek, Nvidia graphics card audio and finally corsair hs1 gaming headset are all I got.

Sorry for sounding dumb, could you explain a little more?

 

[zigzag3143]

I was so excited to receive a different BSOD while running Driver Verifier (although once it rebooted it came back up ok so I can't get it to keep happening)...

Any thoughts on this one guys?

Driver verified and Related to MBfilt64.sys Audio Driver from Creative Technology Ltd.

I would remove to test and if you have to re-install it I would find the newest version to re-install.

Thank you for the reply, I am not really sure what you are saying though. I don't have any creative technology drivers that I know of (Realtek, Nvidia graphics card audio and finally corsair hs1 gaming headset are all I got.

Sorry for sounding dumb, could you explain a little more?

Not dumb at all. Often a particular driver is used by more than one company.

In your case the driver MBflt64.sys is present, loaded, and causing the crash. If you search for it you will find it. When you do right click>properties and see who the mfr is.

You can prevent it from loading by changing it from MBfilt64.sys to MBflt64.bak. It may disable your sound but at least you could tell the mfr etc.

 

[thrashmagazine]

Driver verified and Related to MBfilt64.sys Audio Driver from Creative Technology Ltd.

I would remove to test and if you have to re-install it I would find the newest version to re-install.

Thank you for the reply, I am not really sure what you are saying though. I don't have any creative technology drivers that I know of (Realtek, Nvidia graphics card audio and finally corsair hs1 gaming headset are all I got.

Sorry for sounding dumb, could you explain a little more?

Not dumb at all. Often a particular driver is used by more than one company.

In your case the driver MBflt64.sys is present, loaded, and causing the crash. If you search for it you will find it. When you do right click>properties and see who the mfr is.

You can prevent it from loading by changing it from MBfilt64.sys to MBflt64.bak. It may disable your sound but at least you could tell the mfr etc.

Thanks, I will give it a look over. Just out of curiosity, what tools did you use to tell its causing a crash, blue screen viewer wasn't much help to me.

 

[zigzag3143]

Thank you for the reply, I am not really sure what you are saying though. I don't have any creative technology drivers that I know of (Realtek, Nvidia graphics card audio and finally corsair hs1 gaming headset are all I got.

Sorry for sounding dumb, could you explain a little more?

Not dumb at all. Often a particular driver is used by more than one company.

In your case the driver MBflt64.sys is present, loaded, and causing the crash. If you search for it you will find it. When you do right click>properties and see who the mfr is.

You can prevent it from loading by changing it from MBfilt64.sys to MBflt64.bak. It may disable your sound but at least you could tell the mfr etc.

Thanks, I will give it a look over. Just out of curiosity, what tools did you use to tell its causing a crash, blue screen viewer wasn't much help to me.

BSV and who crashed are sort of ok for a quick view but the gold standard is WinDeBugger.

It has a steep learning curve but is well worth it. Its not rocket science.

The one con for WinDbg is to work you need to download symbols for each OS (abt a gig each)

 

[thrashmagazine]

Not dumb at all. Often a particular driver is used by more than one company.

In your case the driver MBflt64.sys is present, loaded, and causing the crash. If you search for it you will find it. When you do right click>properties and see who the mfr is.

You can prevent it from loading by changing it from MBfilt64.sys to MBflt64.bak. It may disable your sound but at least you could tell the mfr etc.

Thanks, I will give it a look over. Just out of curiosity, what tools did you use to tell its causing a crash, blue screen viewer wasn't much help to me.

BSV and who crashed are sort of ok for a quick view but the gold standard is WinDeBugger.

It has a steep learning curve but is well worth it. Its not rocket science.

The one con for WinDbg is to work you need to download symbols for each OS (abt a gig each)

Another quick one, sorry to keep bothering you, did you see this in each blue screen or just the latest one? Wondering if Driver Verfier actually helped out or if it was in each one anyways.

 

[zigzag3143]

Thanks, I will give it a look over. Just out of curiosity, what tools did you use to tell its causing a crash, blue screen viewer wasn't much help to me.

BSV and who crashed are sort of ok for a quick view but the gold standard is WinDeBugger.

It has a steep learning curve but is well worth it. Its not rocket science.

The one con for WinDbg is to work you need to download symbols for each OS (abt a gig each)

Another quick one, sorry to keep bothering you, did you see this in each blue screen or just the latest one? Wondering if Driver Verfier actually helped out or if it was in each one anyways.

None of these were driver verified and all point to netio.sys



Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users.

 

[thrashmagazine]

BSV and who crashed are sort of ok for a quick view but the gold standard is WinDeBugger.

It has a steep learning curve but is well worth it. Its not rocket science.

The one con for WinDbg is to work you need to download symbols for each OS (abt a gig each)

Another quick one, sorry to keep bothering you, did you see this in each blue screen or just the latest one? Wondering if Driver Verfier actually helped out or if it was in each one anyways.

None of these were driver verified and all point to netio.sys



Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users[/B]

unfortunately that driver didnt have a mfr, so i just deleted all my drivers for audio and let windows install them this time as oppose to my motherboard ones. Maybe that will do the trick...im doubtful though since things like this never work this easy for me haha

 

[zigzag3143]

Another quick one, sorry to keep bothering you, did you see this in each blue screen or just the latest one? Wondering if Driver Verfier actually helped out or if it was in each one anyways.

None of these were driver verified and all point to netio.sys



Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users[/B]

unfortunately that driver didnt have a mfr, so i just deleted all my drivers for audio and let windows install them this time as oppose to my motherboard ones. Maybe that will do the trick...im doubtful though since things like this never work this easy for me haha

Good luck and let us know if you need help

Ken

 

[thrashmagazine]

None of these were driver verified and all point to netio.sys



Driver verifier

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users[/B]

unfortunately that driver didnt have a mfr, so i just deleted all my drivers for audio and let windows install them this time as oppose to my motherboard ones. Maybe that will do the trick...im doubtful though since things like this never work this easy for me haha

Good luck and let us know if you need help

Ken

Will do and I will report back within the week if i BSOD again

 

[thrashmagazine]

Good luck and let us know if you need help

Ken

I crashed again, this time back to the original crash message "0x000000d1."

It was also harder to get back into Windows this time, it took me about 5 boot ups before it wouldn't just crash back to the bios screen. Running out of ideas now...

 

[thrashmagazine]

I opted to format my computer over the weekend, so as of Sunday night, my computer is up and running and will not be rebooted for a week or two to see if I can get it to crash, will update if I have an issue still.

Still used Windows 7 x64.

 

[thrashmagazine]

Possible Reason Found

I formatted my computer on Saturday and have had no crashes as of yet (crossing my fingers). However, I might have stumbled upon the reason on a friends computer today.

Keep the differences in mind though:
I used AVAST when BSOD
I am currently using MSE without BSOD yet

He is using MSE however:

The minute I installed uTorrent for him on his machine, with uTorrent open for anywhere from 5 minutes to 2 hours it BSODs, same error. Both of us using Win7 x64.

That said, my obvious thought was, google it. I was able to find similar issues but only with Mcafee, so my questions are now:

1. Obviously uTorrent/Virus scanning causing the issue, wondering why
2. Why did it fail with AVAST for me but not MSE
3. Why is it failing with MSE for my friend

My thoughts are it has something to do with memory/core amounts, but that is just a shot in the dark. Where my machine has 4 cores (8 hyperthread), 16GB of RAM, his was only a 2 Core/4GB RAM machine. In other word,s its my only thought as to why my machine can run uTorrent for days without an issue, but his can not. Any ideas?