System freezes

Agreed, although a description of the freezing and what you are/were doing helps. Also, what freezes -the whole system (mouse cursor included) or just apps or the shell, etc?

OK, so the mouse cursor works, which means at least the kernel is running (although if all of your windows freeze, that would indicate a lock somewhere causing a user-mode hang in the shell). If you have a PS/2 keyboard attached to the machine (or are on a laptop), you can do the following to create a memory dump of the system when it hangs:

1. Create or set the following registry value:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
Value: CrashOnCtrlScroll
Type: REG_DWORD
Data: 1

2. Open the Control Panel, and then open "System". Click the "Advanced system settings" link on the left-hand side, which will open the System Properties window to the "Advanced" tab. Under the "Performance" section, click the "Settings" button. Click the "Advanced" tab, and then click "Change" under "Virtual Memory". Uncheck the box "Automatically manage paging file size for all drives" at the top if it is checked, and then select the drive letter that you installed Windows to from the list (usually C: ). Select "Custom size" at the bottom, and enter installed RAM + 50MB in both the "Initial size" and "Maximum size" boxes in megabytes (MB). For example, if you have 4GB of RAM, the number you would enter would be 4146; 4096+50. Click the "OK" button to save the settings, then click "OK" again to return to the "System Properties" window.

3. Next, and also in the "System Properties" window, click the "Settings" button in the "Startup and Recovery" section at the bottom of the "Advanced" tab. Make sure "Complete Memory Dump" is selected (see 3a if this is not in the list) in the "Write debugging information:" drop-down list - not "Small" or "Kernel". Make sure that both the "Write an event to the system log" and "Automatically restart" options are checked, and then click the "OK" button to save settings, then click the "OK" button again to close the System Properties window.

3a. If the "Complete Memory Dump" option in step 3 is not available, you will need to manually configure this registry value:
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
Value: CrashDumpEnabled
Type: REG_DWORD
Value: 1

4. You will need to reboot for these changes to take effect.

5. The next time that the system hangs on you, hold down the *RIGHT* CTRL key and press the SCROLL LOCK key twice to cause the computer to bugcheck (it will be an E2 bugcheck code) and create a memory.dmp file in %SYSTEMROOT% (usually C:\Windows).

Once the system finishes writing the dump file and reboots, you can zip or rar the resulting memory.dmp file and upload it to a file sharing service for us to download and analyze for you.

OK I got it to create dumpfiles.. Thanks I can have some windows freeze up while others don't lol Here are the minidump reports.

No offense, but minidumps for a hang are useless - hence why my instructions directed for *complete* memory dumps.

OK, I see it - azureus is crashing, and werfault.exe has suspended the process and is supposed to be dumping it. However, the Azureus process has over 30 threads that are stuck writing to disk (the disk writes can't complete, because it's suspended by the debugger - this, however, is keeping the debugger from being able to write dump information to disk!. If it was just the two processes deadlocked on each other, that would not be enough to hang the system like this. However, because the process crashing is in the process of writing non-cacheable I/O to the disk and is stuck doing so, it causes any and all threads that come behind it that will write to disk to also wait - and the kernel process (SYSTEM) indeed has a thread attempting to flush a buffer to disk, and thus this is causing the kernel itself to be stuck in a wait until that finishes. Enough of those and yes, the system will hang - here's the thread in kernel that is the last thread to be in a wait state at the time of the dump:

Code:

// This thread is waiting on NTFS to return, which can't because Disk is blocked:
1: kd> !thread 86bf6350 
THREAD 86bf6350 Cid 0004.07c4 Teb: 00000000 Win32Thread: 00000000 WAIT: (Executive) KernelMode Non-Alertable
94b136a0 NotificationEvent
IRP List:
85ab2818: (0006,01fc) Flags: 00060043 Mdl: 86da29b8
Not impersonating
DeviceMap 89808b10
Owning Process 8483ab50 Image: System
Attached Process N/A Image: N/A
Wait Start TickCount 358410 Ticks: 5723 (0:00:01:29.279)
Context Switch Count 8799 IdealProcessor: 0 
UserTime 00:00:00.000
KernelTime 00:00:00.109
Win32 Start Address nt!ExpWorkerThread (0x82abbe2e)
Stack Init 94b13fd0 Current 94b133d0 Base 94b14000 Limit 94b11000 Call 0
Priority 16 BasePriority 13 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
ChildEBP RetAddr Args to Child 
94b133e8 82abcb25 86bf6350 00000000 807c8120 nt!KiSwapContext+0x26 (FPO: [Uses EBP] [0,0,4])
94b13420 82abb423 86bf6410 86bf6350 94b136a0 nt!KiSwapThread+0x266
94b13448 82ab52cf 86bf6350 86bf6410 00000000 nt!KiCommitThreadWait+0x1df
94b134c4 88a514e2 94b136a0 00000000 00000000 nt!KeWaitForSingleObject+0x393
94b134e4 88a500e3 94b13790 851d6000 00001000 Ntfs!NtfsWaitOnIo+0x1c (FPO: [Non-Fpo])
94b13604 88a4a8fb 94b13790 85ab2818 85a28500 Ntfs!NtfsNonCachedIo+0x456 (FPO: [Non-Fpo])
94b1366c 88a4efa9 94b13790 85ab2818 85a28500 Ntfs!NtfsNonCachedUsaWrite+0x145 (FPO: [Non-Fpo])
94b13780 88a5085f 94b13790 85ab2818 0120070a Ntfs!NtfsCommonWrite+0x1dc0 (FPO: [Non-Fpo])
94b13924 82a8a4bc 85a24020 85ab2818 85ab2818 Ntfs!NtfsFsdWrite+0x2e1 (FPO: [Non-Fpo])
94b1393c 889c120c 857ad8d8 85ab2818 00000000 nt!IofCallDriver+0x63
94b13960 889c13cb 94b13980 857ad8d8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa (FPO: [Non-Fpo])
94b13998 82a8a4bc 857ad8d8 85ab2818 85ab2818 fltmgr!FltpDispatch+0xc5 (FPO: [Non-Fpo])
94b139b0 82a82749 3f2e9f6b 899996a8 961694c0 nt!IofCallDriver+0x63
94b139c4 88a4a2bc 85a28478 857ad8d8 94b13a74 nt!IoSynchronousPageWrite+0x19d
94b13a9c 88ac238c 899996a8 3f2e9f58 00000000 Ntfs!LfsFlushLfcb+0x54d (FPO: [Non-Fpo])
94b13af0 88ac2437 019996a8 3f2e9f58 00000000 Ntfs!LfsFlushToLsnPriv+0x1a7 (FPO: [Non-Fpo])
94b13b34 82aecdab 899ba1f8 3f2e9f58 00000000 Ntfs!LfsFlushToLsn+0x87 (FPO: [Non-Fpo])
94b13bd0 82add94f 857ad208 00000000 00000000 nt!CcAcquireByteRangeForWrite+0xa6f
94b13c70 82ae68a3 8517d5dc 00000000 00000001 nt!CcFlushCache+0x244
94b13ca8 82aeeee6 94b13cc4 b334f289 848bc718 nt!CcWriteBehind+0x105
94b13d00 82abbf3b 848bc718 00000000 86bf6350 nt!CcWorkerThread+0x164
94b13d50 82c5c6d3 80000000 b334f219 00000000 nt!ExpWorkerThread+0x10d
94b13d90 82b0e0f9 82abbe2e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
 
 
// The IRP that shows the request pending \Driver\Disk created by this thread:
1: kd> !irp 85ab2818
Irp is active with 11 stacks 5 is current (= 0x85ab2918)
Mdl=86da29b8: No System Buffer: Thread 86bf6350: Irp stack trace. 
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000 
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000 
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000 
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000 
Args: 00000000 00000000 00000000 00000000
>[ 4,34] 1c e0 85749970 00000000 8884d24e-00000000 Success Error Cancel 
\Driver\Disk partmgr!PmReadWriteCompletion
Args: 00001000 00000000 bdbb1000 00000000
[ 4, 0] 1c e0 857495b0 00000000 8885e7a4-85749440 Success Error Cancel 
\Driver\partmgr volmgr!VmpReadWriteCompletionRoutine
Args: 8bbf8c09 00000020 bdbb1000 00000000
[ 4, 0] c e0 85749388 00000000 88dbb3e2-85750c28 Success Error Cancel 
\Driver\volmgr fvevol!FvePassThroughCompletion
Args: 00001000 00000000 8bbf8bf1 00000020
[ 4, 0] c e0 85750b70 00000000 88fca168-00000000 Success Error Cancel 
\Driver\fvevol rdyboost!SmdReadWriteCompletion
Args: 00001000 00000000 b76b1000 00000000
[ 4, 0] c e1 8574c020 00000000 88f92ed6-8698c198 Success Error Cancel pending
\Driver\rdyboost volsnap!VspWriteContextCompletionRoutine
Args: 00001000 3fffffff b76b1000 00000000
[ 4, 0] c e1 8574d020 00000000 88a514f9-94b1369c Success Error Cancel pending
\Driver\volsnap Ntfs!NtfsMasterIrpSyncCompletionRoutine
Args: 00001000 00000000 b76b1000 00000000
[ 4, 0] 0 0 85a24020 85a28478 00000000-00000000 
\FileSystem\Ntfs
Args: 00001000 00000000 00003000 00000000
 
1: kd> !fileobj 85a28478 
\$LogFile
Device Object: 0x85749388   \Driver\volmgr
Vpb: 0x85749ee0
Access: Read Write SharedRead SharedWrite SharedDelete 
Flags:  0x40100
 Stream File
 Handle Created
FsContext: 0x85a28500 FsContext2: 0x00000000
Private Cache Map: 0x85a283e8
CurrentByteOffset: 0
Cache Data:
  Section Object Pointers: 857ab494
  Shared Cache Map: 85a282f8         File Offset: 0 
  Data at offset 0 not mapped

I have no idea why Azureus is crashing, but I would suggest removing this app (and the Java it installs as well) to see if the problem goes away without it installed. It's not a 100% for sure analysis, but the fact werfault is suspending an app that has outstanding I/O requests to disks means it's pretty likely. It could still be drivers, so making sure your drivers are all updated (including antivirus or antimalware application drivers) and Win7 compatible is a must, in any case, regardless of whether or not this was happening.

I was aware the azures was a problem. When i created the dump file, it was empty. So I used azures to create a crash. While Azures may be a problem, it isn't "the" problem lol

When i did a discchk, i chose to repair bad sectors(took like 18 hrs for 300 gig HD )it found/repaired bad sectors in System 32 folder, could this be the problem? Could WinASO registry optimizer have caused that hiccup? That would've meant that I installed win7 over a bad sector? You can tell me to stfu at anytime lol

I uninstalled Vuze and just as i expected, it still does it. Here is an updated Dump file.

http://www.filehosting.org/file/deta...129/MEMORY.zip