Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while doing various things error d1

15 Dec 2011   #11

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by thrashmagazine View Post
Quote   Quote: Originally Posted by zigzag3143 View Post

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.

My System SpecsSystem Spec
.

15 Dec 2011   #12

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by thrashmagazine View Post
Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by thrashmagazine View Post

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

Quote:
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/Windows 7 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.
Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users.
My System SpecsSystem Spec
15 Dec 2011   #13

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by thrashmagazine View Post
Quote   Quote: Originally Posted by zigzag3143 View Post

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

Quote:
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/Windows 7 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.
Driver Verifier - Enable and Disable


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
My System SpecsSystem Spec
.


16 Dec 2011   #14

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by thrashmagazine View Post
Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by thrashmagazine View Post

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

Quote:
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/Windows 7 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.
Driver Verifier - Enable and Disable


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
My System SpecsSystem Spec
16 Dec 2011   #15

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by thrashmagazine View Post
Quote   Quote: Originally Posted by zigzag3143 View Post

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



Driver verifier

Driver Verifier - Enable and Disable


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
My System SpecsSystem Spec
17 Dec 2011   #16

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post

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...
My System SpecsSystem Spec
19 Dec 2011   #17

Microsoft Windows 7 Ultimate SP1 64-bit
 
 

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.
My System SpecsSystem Spec
21 Dec 2011   #18

Microsoft Windows 7 Ultimate SP1 64-bit
 
 
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 Windows 7 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?
My System SpecsSystem Spec
Reply

 BSOD while doing various things error d1




Thread Tools



Similar help and support threads for2: BSOD while doing various things error d1
Thread Forum
BSOD when i have certain things open, error 0x0000003d BSOD Help and Support
Tried many things, still error 800736B3 Windows Updates & Activation
Solved What things i should keep in mind when buying 2nd hand things??? Hardware & Devices
Solved BSOD while trying to do many things BSOD Help and Support
Different BSOD while doing various things. BSOD Help and Support
BSOD while doing certain things.. BSOD Help and Support
Class not registered error when clicking on things like device manager General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:06 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33