Internet causes BSOD

[back2thefuture]

Hi there I have just done the upgrade and all is good except for a major problem I can not fix everytime I click on the explorer to browse the net I get the blue screen of death and do not know what to do.
Everything else runs smooth and stable but as soon as I click the explorer it crashes out can anyone help.

 

[H2SO4]

Hello, and welcome to SF

Please follow this procedure to collect info which would be useful to us in helping to diagnose your crash:

http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

 

[back2thefuture]

Ok will do when I get home thanks for your help.

 

[back2thefuture]

Hi there this is the error reports




110609-32276-01.dmp 06/11/2009 00:18:36 KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e 0xc0000046 0x830428d8 0xa322f378 0x00000000 ntkrnlpa.exe ntkrnlpa.exe+408d8 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit C:\Windows\minidump\110609-32276-01.dmp

 

[back2thefuture]

Can any one help plz?

 

[back2thefuture]

Here is the full error if anyone can please help it is driving me mad ?

bsod error 0x0000008e (0xc0000046, 0x8308a8d8, 0x8defe378,0x00000000

 

[H2SO4]

Here is the full error if anyone can please help it is driving me mad ?

bsod error 0x0000008e (0xc0000046, 0x8308a8d8, 0x8defe378,0x00000000

Please follow the procedure I linked to in order to upload the minidump (file) itself. The numbers alone are usually insufficient.

 

[back2thefuture]

Does this help?

 

[H2SO4]

Does this help?

Yes. Now I've actually got something to examine

If you uninstall the utility to which this driver belongs, and thereby get rid of the driver, the crashes will stop:

Image path: \SystemRoot\system32\DRIVERS\oodivd.sys
Timestamp: Tue Jun 23 06:12:08 2009 (4A3FE598)

 

[back2thefuture]

does it say what program uses this driver at all?

 

[H2SO4]

does it say what program uses this driver at all?

No, sorry, memory dumps don't "speak" in that manner. As a suggestion, check in the registry whether HKLM\System\CCS\Services\Co_mon exists. If so, some of the subkeys and values may offer clues as to where it's from.

If you're having trouble finding any legit-looking references to that driver name, that's sometimes suggestive of malware.

 

[back2thefuture]

Found it and all is working fine you are a life saver thank you so much for your guidence.

 

[H2SO4]

Found it and all is working fine you are a life saver thank you so much for your guidence.

No problem. Glad to hear it's all working!


===============================
(I just noticed that I confused the name of the driver that was giving you grief [oodivd] with the one causing another poster's crashes [co_mon]. Sorry. When you look at a lot of minidumps the distinctions between them tend to go all blurry.)

 

[back2thefuture]

Found it and all is working fine you are a life saver thank you so much for your guidence.

No problem. Glad to hear it's all working!


===============================
(I just noticed that I confused the name of the driver that was giving you grief [oodivd] with the one causing another poster's crashes [co_mon]. Sorry. When you look at a lot of minidumps the distinctions between them tend to go all blurry.)

But is it oodivd that was my issues?

 

[H2SO4]

Found it and all is working fine you are a life saver thank you so much for your guidence.

No problem. Glad to hear it's all working!


===============================
(I just noticed that I confused the name of the driver that was giving you grief [oodivd] with the one causing another poster's crashes [co_mon]. Sorry. When you look at a lot of minidumps the distinctions between them tend to go all blurry.)

But is it oodivd that was my issues?

Hehe, are you purposefully aiming to confuse me now?

Yes, according to a random sampling of your 16 minidumps, all of the crashes were almost certainly caused by a driver called oodivd.sys, which is apparently something to do with "O&O DiskImage".