Random freezes, tried alot but won't help

Hi Everyone,

I really need some help here. I consider myself a relatively advanced user (fix most of my problems myself, build my own PC's), but I just can't seem to figure this one out.
My PC keeps freezing on me randomly, while watching vids, browsing the internet, being idle...surprisingly enough mostly not while gaming though.

I've tried several things:
-Updated bios.
-Thought it was my sound card or drivers. Removed my sound card, formatted system disk, reinstalled windows 7 ultimate with newest drivers for everything.
-Thought it was my hard disk, bought a new one (was planning to anyways), reinstalled everything newest drivers, no dice.
-Thought it might be my memory, scanned it using the microsoft memory checker and memtest86+, no errors found. (Now removing 1 stick at a time, seeing if it still crashes)
-I also tried stress testing my memory using Prime95, did this twice, and both times this caused blue screens with different error messages (one about memory, one about windows drivers?). I still have the dump files if u guys think they'll be useful.
-I was also checking the event logs, seems Multimedia Class Scheduler, Application Experience and Windows Update services tend to be started (or sometimes stopped) often right before the crashes, the Windows Modules Installer tends to be stopped and changed to start on request or start automatically alot as well. . I also noticed alot of svchost.exe's are running all the time... Don't know what all this might mean though.

Also, my power settings are on high performance with no sleeping or deactivating.
My system info is in my profile, I'll add a dxdiag to the post (in dutch, sadly).

I know there's a lot of things this can be, but i hope the things I've done will help you guys help me figure it out.

Thanks in advance,
fatalefout

ps. I crashed a few times and swapped out my memory sticks meanwhile, with the one it tends to freeze more often, and with the other no crashes yet. Could this be the problem then, even though the tests said there were no errors? Or could it be that i placed my memory in a different slot?
EDIT: Froze using the other stick of RAM as well...

EDIT 2: been reading other random freeze topics, I've looked at the processes that are running and their I/O read + other values, but none were higher than 45.379. Only thing notable was that svchost.exe was running 7 times... (right now, svchost.exe is using 4.295.935.618 in I/O others, multiple others are running, just crashed again)

Please let us see the memory dump files:

Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service (not RapidShare as the analysts usually can't download from it) - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

Memory dump files here. I tried stress testing my proc, it froze every(like 10) time except 1. Not after a set amount of time though(1-30 mins), and it freezes after a while without stress testing too...

I guess it could also be a voltage problem, my vCore's set to 1.33 automatically according to CPUID...whereas it should be 1.35? I never overclocked this setup by the way...

I tried a clean boot, still freezing even though i didnt have anything non-windows booting up.

ps. It even froze during the windows welcome screen twice
ps. 2: It's started freezing more often since i use only 1 memory stick (either one will do)
EDIT:
I also tried upping my vCore to 1.36 and setting the mem voltage to 1.66(1.65 is default), still crashes. ..I just checked with a memory stick from another computer that works fine, and i still have crashes. So that means it's not the RAM i guess?

OP also receiving assistance here: Random freezes, tried alot but won't help - Tech Support Forum

Here's my last post from there:

Here's an extract of the stack text from the STOP 0x1A error:

Code:

nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'+0x4a83
nt!MiDeleteVirtualAddresses+0x4cc
nt!NtFreeVirtualMemory+0x5ca
nt!KiSystemServiceCopyEnd+0x13
0x778d009a

Stacks are read from the bottom up.
So, the first thing (0x778d009a) is a memory address from (presumably) a user level process (as only the kernel level stuff is captured in a minidump.
Next is the ending of System Service function.
Then there's an attempt to free virtual memory and delete the virtual address'
At which point Windows starts to get really confused, and finally it issues the KeBugCheckEx (the blue screen crash).

The whole point of this is that it appears to me that it's a 3rd party software/function that appears to be causing this (the System Service stuff).

Interestingly, the next 2 errors are STOP 0x3B - SYSTEM_SERVICE_EXCEPTION - which reminds me of the nt!KiSystemServiceCopyEnd from the STOP 0x1A stack text above.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2008 or earlier:

Code:

Alpham164.sys Mon Jul 23 03:57:03 2007 - Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham164.sys
Alpham264.sys Tue Mar 20 05:51:03 2007 - Ideazon ZBoard - http://www.carrona.org/dvrref.html#Alpham264.sys
copperhd.sys Tue May 23 23:51:13 2006 - Razer Diamondback - http://www.carrona.org/dvrref.html#copperhd.sys
WMP300Nv2.sys Tue Jul 31 01:13:59 2007 - Atheros AR5008 Wireless Network Adapter for your Linksys Wireless-N PCI Adapter WMP300Nv2 - http://www.carrona.org/dvrref.html#WMP300Nv2.sys

I have seen a lot of issues recently with the ZBoard and Razer devices. But, if updating them doesn't fix things, please try running Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 16:51:56.943 2010 (GMT-4)
System Uptime: 0 days 1:02:50.644
BugCheck 3B, {c0000005, fffff80002d75870, fffff8800a6ce470, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpCreateHandle+300 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  prime95.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jun  7 15:48:15.948 2010 (GMT-4)
System Uptime: 0 days 1:21:33.259
BugCheck 1A, {41284, 39d1d001, 10d70, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )
BUGCHECK_STR:  0x1a_41284
PROCESS_NAME:  prime95.exe

I'd pick one and stick with it. It'll save me (and others) a lot of time posting to both threads.
FYI - there's a very small community of people who help with BSOD issues - and these 2 forums are the primary places that they hang out.

Here's my response to the last post:

If you're experiencing hangs/freezes and BSOD's - they're usually related.

Actually, when using Driver Verifier you're waiting for a DRIVER_VERIFIER_ENABLED_MINIDUMP. But, since you're not doing the dump analysis, the BSOD is easier for you to recognize. The memory dump is generated when your system crashes, but it's not finalized until you reboot.

Once we figure out the BSOD issues then we can work on any freezing/hanging that may remain.

I could not find any drivers for v2 either. Did you click on the "find the model number" link and double check? FYI - this model (the v1) is NOT compatible with 64 bit Vista systems ( Re: WMP300N Vs WMP600N - Cisco Home Community )

Due to the difficulties that you're experiencing, I'd suggest removing the software and the card from your system. If you must have internet connectivity while testing, either purchase a new card that's Win7 compatible - or temporarily run an Ethernet cord from the router to the system. This will help to rule out the card as being a problem.