Solved BSOD Error BCCode:3b

[axe0]

It seems you are missing an ASUS driver.
Driver Reference Table - AsUpIO.sys

*** WARNING: Unable to verify timestamp for AsUpIO.sys
*** ERROR: Module load completed but symbols could not be loaded for AsUpIO.sys
0: kd> lmvm AsUpIO
start             end                 module name
fffff880`03d1d000 fffff880`03d24000   AsUpIO   T (no symbols)           
    Loaded symbol image file: AsUpIO.sys
    Image path: AsUpIO.sys
    Image name: AsUpIO.sys
    Timestamp:        Tue Aug 03 04:47:59 2010 (4C57835F)
    CheckSum:         0000BD68
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please remove the overclocking while troubleshooting, it is not smart to overclock anything on an unstable system as it might cause more instability.

 

[fpvivia]

The reason that driver probably looks like it's missing is I uninstalled the ASUS suite and it most likely deleted this driver in the process. I don't believe I am currently set up in overclocking mode. Just got another BSOD. The error code is back to 3b so it looks like nothing's changed. Why is it so difficult with all these tools to pinpoint the exact cause of these recurring BSOD's? There has been a lot of time invested to solve this but it appears that we are not close to figuring it out. Any other ideas? Thanks.

 

[axe0]

Who says there is a single cause?
A BSOD could have so many causes, you wouldn't beleave.

 

[fpvivia]

Maybe, but all I know is the BSODs started occurring 2 weeks ago and after all the time I've spent trying to fix this it seems like I'm no closer to resolving this problem. Given the disruption these cause a user I would think Microsoft would provide some better tools for troubleshooting. It's going to take many more hours to rebuild this system on a new PC but I guess that's what I'm left with at this point unless you have any other ideas. Thanks.

 

[axe0]

Please run the Microsoft Uninstall Fix it to see if there is some leftover from ASUS AI Suite

 

[fpvivia]

Ran the tool and it didn't find any evidence of the ASUS Suite still installed. Any other ideas? Thanks.

 

[axe0]

This kind of a suggestion is one I do rarely.

Install ASUS AI Suite II again and remove it using Revo Uninstaller
Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems
There is a chance the removal process didn't remove AI Suite properly.

 

[fpvivia]

OK, I did this and got at least one more BSOD. Here is the updated collector file. Anything else I should try?

 

[axe0]

The dumps are again blaming the nvidia video driver.
But, because it might be possible that the data this driver gets is already corrupted before it executes the data my guess is that it starts with the memory. Usually memory corruption would come up in that case, but I think that what happens is that the driver gets data from multiple places from the memory, only 1 place is corrupted but it hasn't been noticed by the system and because of that memory corruption doesn't come up in the dumps.

I honestly don't know if it is true what I say, because I have no idea how it is going, but I simply think it is worth a short to test the memory.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

[fpvivia]

I replaced the RAM with new about 5 days ago. Before I did I tested it and there were no issues. I don't think it's the RAM. Do you think I should replace the video card? I was also thinking about booting from the Windows 7 install disk and running a repair of windows. On the other hand I haven't seen a BSOD for about 12 hours. Your thoughts?

 

[axe0]

Since the video drivers have been flagged a few times, I think it is time to test the GPU

Diagnostic test

 GPU TEST

Run Furmark to test your GPU. Furmark tutorial

   Note

Run Furmark for around 30 minutes

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high

 

[fpvivia]

I tried running it but the program says it requires an Open GL 2.0 compliant graphics card - Nvidia 6.0 or above. Mine is a 550 so it won't conduct the stress test. I'm going to replace the graphics card and see what happens.

 

[axe0]

That means Furmark isn't supporting the GPU, replacing the GPU would be a good decision and hopefully helps.

 

[fpvivia]

I replaced my GPU but after about 24 hours I started getting BSOD's again. I don't know what to do at this point. It appears that the only way to solve this is to reinstall windows on my computer. The DM Collector file is attached. Let me know if you have any other ideas. Thanks.

 

[axe0]

I'm by far an expert at hardware and thus not 100% certain, but I think it is worth it to suggest if not already been tried or possible?
Please try to put the GPU in another slot if possible.
It currently looks like a motherboard problem, but it is also possible that the new GPU is faulty.
View attachment 377155

 

[fpvivia]

I don't have the physical room in my system to change the slot in the motherboard being used for the GPU so that's not an option. I think it's highly unlikely that both a new and the old graphics card would be faulty. I'm pretty convinced at this point that my only course of action is to start over with this computer and reinstall windows. The BSOD's are still occurring regularly.

 

[axe0]

My thought is more that the slot the GPU is using is faulty then that the GPU is faulty.

 

[fpvivia]

Well, I have to move several things around in my case to move the GPU but I'll give it a try. I'll let you know. Thanks.

 

[fpvivia]

Well, I changed the GPU slot and about 15 minutes after the computer rebooted I got another BSOD. Any other ideas?
Thanks.

 

[axe0]

Diagnostics Test

 Clean boot

Please try the following:

• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Go to the tab startup
  • Disable everything
• Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
If the problem still persist, try booting in safe mode and see if the problem still persist