New
#1
Random System Freezing - No BSOD but is Unresponsive
Hello
I am getting seemingly random hangs in Windows 7 that I can't get to the bottom of. I'm hoping one of you awesome people can help me out?
It seems to happen most often when I'm in Firefox and I use my MMB to scroll the page - not the wheel, but using the MMB as a button so that I can smooth scroll with the little up/down arrow icon that appears on the page. This happens in Firefox 4, 5 and 6, so it's not just one bad version I don't think. It does happen at other times, but that is the most consistent pattern I can find. It also happens regardless of how many tabs I have open or what other applications are open in the background. The freezes do not happen under massive load (I can render with all the cores on 100% and it's stable) or as a result of excessive heat (max CPU temp gets to about 40 degrees C under full load).
This started happening about a month ago, but is happening much more frequently now -sometimes 5 times a day.
- Windows 7 x64 ?
- Full Retail
- Hardware is 4 months old
- Software installation is 4 months old
I have run Driver Verifier to force a BSOD and got this info when I restarted:
I have also used WhoCrashed to get this info:Code:Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 7177 Additional information about the problem: BCCode: c4 BCP1: 0000000000000062 BCP2: FFFFFA800AB49858 BCP3: FFFFFA800AB44D50 BCP4: 0000000000000002 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1
I have also attached the jcgriff2 info and the perfmon report to this message.Code:On Mon 2011/09/12 03:08:53 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\091211-78374-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xC4 (0x62, 0xFFFFFA800AB49858, 0xFFFFFA800AB44D50, 0x2) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 2011/09/12 03:08:53 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xC4 (0x62, 0xFFFFFA800AB49858, 0xFFFFFA800AB44D50, 0x2) Error: DRIVER_VERIFIER_DETECTED_VIOLATION Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 2011/09/12 03:03:32 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\091211-24710-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0xC4 (0x62, 0xFFFFFA800AF0D2D8, 0xFFFFFA800AF524E0, 0x2) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. The driver is unloading without first freeing its pool allocations. A bug check with this parameter occurs only when the Pool Tracking option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Attachment 175025
As far as I can tell all my hardware drivers are up to date and I have updated my BIOS too.
Thanks in advance!
David
Quote
I have updated those drivers and a whole bunch more I found through DriverIdentifier.com. I will report back if there are any further issues or if it is indeed resolved in a few days time - so far all is seemingly well.