Help with BSOD Fix please

[zocheyado]

I cannot figure out this bsod issue, I have been trying forever I cannot figure it out and it is the most frustrating thing on the planet. I have replaced the HDD's at one point, the motherboard, the ram, the psu, the GPU, and the network card, So at one point I probably had more then one problem, The current BSOD's are only the ones since my most recent replacement which is my graphics card, I switched to a 6950 from a gtx 460 and these are the bsod's since then, before that It was bsoding on the gtx 460 most of the time. I re installed windows right when I got the card. I have a few other threads on different forums and so far, I have tried uninstalling and using drive sweeper and then re-installing different versions of the graphics driver, I have adjusted the voltages on my ram to meet specs, and rolling back the driver, etc. If you can help me fix it 50$ pay pal coming your way, because as I said I have replaced so many parts in this computer Its cheaper for me to just figure out what is wrong.

 

[zocheyado]

Almost Forgot!

 

[MvdB]

Hello Zocheyado, welcome to SF! Sorry we took some time, very busy here at C&D!

You have a couple of possible problems though I have not had the time to go through all your dumps, just too many of them

First go to Devices and check these, make sure they either work correctly with new drivers or de-install:

Android Phone    USB\VID_0BB4&PID_0CAD&MI_01\6&1ACC5438&0&0001    The drivers for this device are not installed.
Unibrain 1394 PC    UB1394\UNIBRAIN&1394_PC\0013EA47001C6F65    The drivers for this device are not installed.

You have MANY instances of mscorsvw.exe failing. That is a process that should normally finish quickly, see here for more info: What is mscorsvw.exe and why is it eating up my CPU? What is this new CLR Optimization Service? - David Notario's WebLog - Site Home - MSDN Blogs
Or here for MS info: Mscorsvw.exe using 50 % of my CPU - Windows 7 Home SP1 - 64 bit - Microsoft Answers

But, for now, I think your biggest problem is mixed up Graphics drivers.
Your latest dump has a problem with your ATI drivers. Please get the latest for your card:
http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671

 

[zocheyado]

Well see I had another thread going on in a different forum in which everyone thought It was the graphics driver, I have always always had the most up to date drivers directly from AMD, through out this process I have uninstalled and reinstalled a dozen times in a dozen ways with different versions, So I really do not think it is the graphics driver. And not sure if I said it above but before I had the AMD card I have a nvidia Card and the same thing was happening.

 

[MvdB]

Well, there is no such thing as being a 100% sure... But I am sure that your graphics driver crashed. That is for sure. The question is.... Why. Possible reasons in order of likeliness:
1 the driver itself, in relation to the rest of the files of the graphicscard. Problem in your case could be your many retries.... A known problem is that these drivers are not removed correctly by their normal deinstall software. Some part rmains and is not replaced by the new. Could well be the case here. That why we have additional tools to remove stuff and others to clean registry.
2. Graphics card hardware is malfunctioning or gets too hot
3. RAM malfunctions
4. Mobo graphics card slot / bios settings.
5. IRQ settings

But if you are sure this is not it... I'll be happy to help you through tests to see whats up...

 

[zocheyado]

Well, there is no such thing as being a 100% sure... But I am sure that your graphics driver crashed. That is for sure. The question is.... Why. Possible reasons in order of likeliness:
1 the driver itself, in relation to the rest of the files of the graphicscard. Problem in your case could be your many retries.... A known problem is that these drivers are not removed correctly by their normal deinstall software. Some part rmains and is not replaced by the new. Could well be the case here. That why we have additional tools to remove stuff and others to clean registry.
2. Graphics card hardware is malfunctioning or gets too hot
3. RAM malfunctions
4. Mobo graphics card slot / bios settings.
5. IRQ settings

But if you are sure this is not it... I'll be happy to help you through tests to see whats up...

Thanks for the big reply! well as for the graphics driver, I did not just use the default un installer, I used drive sweeper and since then I have reinstalled windows entirely as I have a few times before in an attempt to fix it and it Still crashes with brand new drivers on a brand new install So I doubt it is drivers, I usually have a gpu temp gadget so I don't think that is the issue, especially since most of the crashes occur during starcraft 2, even though crysis 2 makes my gpu alot hotter and it crashes alot less. As for ram, I have ran memtest86+ for a few hours on my new ram, I had other ram that I had for about a year that I thought must be the problem and replaced only to find that nothing changed and got another blue screen. So im going to hesitantly remove the top 3 as possible issues, now Is there any way to test my graphics card slot? is there a way to clean it if it has dirty connections or something? also you said /bios settings, is there a way I can download a profile of my bios so you guys can check it out? I recently RMA'ed my mother board guessing that something was wrong, and they told me that my bios settings were incorrect and they at that point updated my bios to the current version and set it to the default so Im assuming that is correct, and any more info on IRQ settings / what you ment by that? Again im not opposed to buying new hardware. just cant tell what is wrong. Thanks!

 

[zocheyado]

Also I forgot to mention this before but! 2 times now since I have resintalled it has blue screened, but 2 other times it has just crashed...so it would freeze and the sound would repeate just like when it blue screens but no minidump is made to examine =/ here is the system run profile thing since resintall and all that.

 

[MvdB]

Ok, I'll have a look. Meanwhile, could you update us on progress on the other issues I identified?

You have MANY instances of mscorsvw.exe failing. That is a process that should normally finish quickly, see here for more info: What is mscorsvw.exe and why is it eating up my CPU? What is this new CLR Optimization Service? - David Notario's WebLog - Site Home - MSDN Blogs
Or here for MS info: Mscorsvw.exe using 50 % of my CPU - Windows 7 Home SP1 - 64 bit - Microsoft Answers

Just as an example the mscorsvw one.. but any of those issues could cause your problems....

 

[MvdB]

For future ref I'll copy some of the dump analysis here:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000018569a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002aea809, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  00000000018569a0 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeGetCurrentProcessorNumberEx+19
fffff800`02aea809 668911          mov     word ptr [rcx],dx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  uTorrent.exe
--------------------------------------------------------------------
SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  tcpip!IppPacketizeDatagrams+b3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4db4de6a

FAILURE_BUCKET_ID:  X64_0xA_tcpip!IppPacketizeDatagrams+b3

BUCKET_ID:  X64_0xA_tcpip!IppPacketizeDatagrams+b3

Followup: MachineOwner

In this dump it is again another type of code and driver. It is starting to look like there is something wrong at a deeper level. Also, in this dump, it had a problem again with basic W7 drivers, this time part of the security system...

Om the other hand, the dump before that from 7th of August, again points to graphics drivers:

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0000001, {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+4d761 )

Followup: MachineOwner
---------

Assuming all went well in your previous steps and you did really delete old drivers and install correct new ones.. That you even checked the exact versions of these drivers that are loaded in your system. Also that all other points advised above have been done/fixed.

Again ONLY if all the above has been tried and tested... then I'd start looking at HW.. This kind of diversity of problems can, in your case of a new build, be caused by something as simple (but difficult to research) as PSU / powersetting problem.

We recently had a thread here where there were all sorts of crash codes, memtest worked fine for 7 passes etc all sort of tests... fine... but still crashes. UNtil someone thought to push up the voltage of a ram module a bit. That fixed it.

Anyway, not saying that specific example it the case here but.. IF you build your own, as you have apparently done, you need to have researched and tried out all the detail of voltages / amps on a rail etc for your specific system....

 

[MvdB]

PS.... you really need to be complete in following earlier steps before looking into hardware.
Your USB problem still remains. It is as good a reason for this as any other:

Universal Serial Bus (USB) Controller PCI\VEN_1033&DEV_0194&SUBSYS_50071458&REV_03\4&A1CFEE5&0&0048 The drivers for this device are not installed.

On the 9th part of the problem could have been a memory leakage in CamtasiaStudio, according to logs. That has not caused a dump though...

 

[zocheyado]

Yeah I know i need to install those USB's its USB3.0 and Microsoft doesn't have a auto driver for it. Yes I am sure that I did the drivers correctly, So! what types of hardware would you suspect? The only thing I know for sure is that my RAM is running at its rated voltage of 1.65v, but that's all I know for sure. could it be motherboard? what are your thoughts on HW?

 

[zocheyado]

Oh and another thing I forgot to mention gah keep forgetting, is that I doubt it is voltages, because when I first made this build it worked fine for about 8 months no issues at all, ever, then one day it started and never stopped.

 

[zocheyado]

Crashed again. sigh

 

[MvdB]

Please un-install that usb. it could have caused all of this.
Also, please update us on the .NET 4.0 compiler that crashed all the time. Have you done anything there? That's the mscorsvw problem that I did not yet get an answer on.

I'm pressed for time right now but will try to look at the new dump in the morning...

 

[zocheyado]

Un install? you mean install? maybe. and are you saying I should get net 4.0? i dont remember saying anything about it. and any advice on how to fix the mscorsvw problem? thanks a ton btw.

 

[MvdB]

Sorry, with uninstall I mean de-install...

The mscor problem=the .NET compiling prob.
I'll see if I can get some extra info to solve it for you in the morning... Am on an ipad now....wont work

 

[zocheyado]

extra info.....windows update had a .net framework update....*megusta* lol, but also my friend mentioned trying another graphics card to see if it was the card or the slot or whatever, and since my parents have a 9600gt I figured it would be a good test since it would be nvidia and not amd so if it crashes with nvidia driver we would know somethings up! but ...when I first plugged in the graphics card and turned on the system, it didn't post and I sat there for a second..and was like oh! forgot to plug in 6pin power, so i turned it off and plugged it in, tried it again, waited...no post....so I unplugged that 6 pin and used a different one...and it started...so im wondering....maybe one of my 6pin pci power cables is bad? perhaps, because my 6950 uses both, so it might be starting like normal but being massively under-powered. again totaly pulling this out of my *** but w/e lol. will return with results!

 

[zocheyado]

So since my last post, I tried putting that other card in, and started bopping around on starcraft and watching that 70s show trying to induce a crash, and about halfway through, instead of crashing I started getting alllll these dots on my screen, I have a screenshot here http://img811.imageshack.us/img811/6520/unledhptg.png and a video of it here VIDEO0070 - YouTube , so Just wondering if that makes your job any easier. and then I plugged in my other 2 6 pin power cables the 2 that work for sure, and started it back up with the other graphics card, and again boom crash... sigh. but this one didn't have a blue screen just froze.

 

[MvdB]

Yes, though I'm not a graphical card expert, I'd say these dots prove there is a power/HW failure. However, again, I'm not an expert on Graphical cards and what you did in swapping ATI - Nvidia is not easy...
They have conflicting drivers and the driver set MUST be removed completely before installing the other. If you did no do what is advised in the quote below, I would go and de-install ALL (both ati and nvidia) drivers, reboot (you'll have a Safe mode -like screen) and only then install the latest correct version for your current card. NEVER just swap.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Driver Sweeper

Driver Sweeper is a fast tool to remove driver leftovers from your system. It's very important to remove your drivers on a proper way, because driver leftovers can cause problems like stability and startup problems. You can use it if you want to update/remove drivers from your system.

How to use ?

There are two methods to use Driver Sweeper.
Both methods achieve the same results. This method is always able to clean all files.

This method will delete remaining files upon reboot (if deleting failed). You can clean your drivers this way:

- Use the official uninstaller(s) of the driver(s) you want to uninstall.
- Reboot your PC in Safe Mode.
- Run Driver Sweeper and select what to clean.
- Analyse lists all the entries possible to remove, cleaning removes the entries selected.
- More drivers can be selected for the same cleaning process.

What can it be used for ?
The current supported drivers are NVIDIA (Display and Chipset), ATI (Display), Creative (Sound) Realtek (Sound), Ageia (PhysX) and Microsoft (Mouse).

Phyxion.net - Driver Sweeper
When it is removed then download and install the fresh copy, from the manufacturers' site if possible.

 

[zocheyado]

I have never had both cards installed at the same time, but im having issues still, it has since blue screened once but it froze before it could make the minidump, and besides that my computer has been just freezing alot instead of bluescreening, just freezing making me restart. any more ideas you guys ?