New
#21
I don't think the CPU is bad if it passed IBT at 62C max. Running it at high or more can cause BSODs a lot.
Someone else will have to analyze your dumps for you. :)
I don't think the CPU is bad if it passed IBT at 62C max. Running it at high or more can cause BSODs a lot.
Someone else will have to analyze your dumps for you. :)
Code:BugCheck DE, {2, fffff8a002cbca50, fffff8a002cbcb51, 27a2b8c0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2c8e1 )This bugcheck indicates that a driver has corrupt the pool pages being paged out to the disk.Code:Usual causes: Device driver, Memory
Your Sophos Anti-Virus On-Access Driver seems to be causing problems, please remove the program completely and then install these free and proven alternatives which work best with the operating system due to their lightweight nature on system resources and compatibility.Code:3: kd> lmvm savonaccess start end module name fffff880`06c32000 fffff880`06c62000 savonaccess T (no symbols) Loaded symbol image file: savonaccess.sys Image path: \SystemRoot\system32\DRIVERS\savonaccess.sys Image name: savonaccess.sys Timestamp: Fri Jan 27 11:08:07 2012 (4F228597) CheckSum: 0002DE2C ImageSize: 00030000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Install and perform full scans with:
- Malwarebytes : Free anti-malware download
- Microsoft Security Essentials | Protect against viruses, spyware, and other malware
InformationRemember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system
You can also view this thread for a complete free and lightweight security protection combination:
Ok, I've uninstalled Sophos and am installing malwarebytes and MSE.
I'll update again if I have anymore problems, thankyou for your help!
Welcome, will look forward for an update :)
So after running full scans with both Malwarebytes and MSE, my computer was clean (apart from some registry files found by Malwarebytes, which I removed).
However, playing GW2 today I got another blue screen, this time memory_management 1a (minidump attached). This seems to be my most common one, however I can't seem to narrow down the problem.
-I've run memtest86+ twice and it has run both times no errors over 9-10 passes.
-I've ran FurMark once with no problems
-I've ran IBT three times, with only a blue screen occuring during the Very High test, Standard and High tests were passes.
Code:BugCheck 1A, {403, fffff68000477f00, caa0000027a2b867, fffff68000477e00} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3211c )This bugcheck indicates that the page table and PFNs are out of sync, parameters 3 and 4 differ quite sustainability, and therefore I believe at the moment it more of a software problem.Code:Usual causes: Device driver, memory, kernel
There also seems to be a pending IRP associated with the thread, since this is a Minidump, I'm not able to gather the IRP stack and any associated drivers.Code:3: kd> !thread GetPointerFromAddress: unable to read from fffff8000dd00000 THREAD fffffa800a6d7060 Cid 03f4.1148 Teb: 00000000fff86000 Win32Thread: fffff900c219a5d0 RUNNING on processor 3 IRP List: Unable to read nt!_IRP @ fffffa800a692880 Not impersonating GetUlongFromAddress: unable to read from fffff8000dc3fba4 Owning Process fffffa8006a89390 Image: Gw2.exe Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 173647 Context Switch Count 4751028 IdealProcessor: 0 LargeStack ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address 0x0000000000942433 Stack Init fffff8800c1d4c70 Current fffff8800c1d47c0 Base fffff8800c1d5000 Limit fffff8800c1cc000 Call 0 Priority 11 BasePriority 8 UnusualBoost 0 ForegroundBoost 2 IoPriority 2 PagePriority 5
Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
InformationAdditional Help - Using Driver Verifier to identify issues with Drivers
Well looks as though it's a driver problem. After setting up driver verifier as per the instructions you posted, I immediately got a blue screen straight after the 'starting windows' screen. Minidump attached, my desktop is filled with these things now haha.
Also, what would I do in regards to the IRP?
A IRP isn't an error, it's a completely normal procedure (IRP = I/O Request Packet), if you mean what would you in a debugging sense, then you would use !irp with the address of that IRP.
This bugcheck is caused when Driver Verifier finding a I/O violation, the error can be seen with the first parameter. A driver marked a IRP pending but didn't return the STATUS_PENDING flag.Code:BugCheck C9, {23e, fffff88004401324, fffff98009706ee0, 0} *** WARNING: Unable to verify timestamp for GEARAspiWDM.sys *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dtsoftbus01.sys *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
Remove:
Code:Start Menu\Programs\DAEMON Tools LiteCode:2: kd> lmvm dtsoftbus01 start end module name fffff880`04400000 fffff880`04449000 dtsoftbus01 T (no symbols) Loaded symbol image file: dtsoftbus01.sys Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys Image name: dtsoftbus01.sys Timestamp: Fri Jan 13 13:45:46 2012 (4F10358A) CheckSum: 00046D1E ImageSize: 00049000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4This driver is usually either used by iTunes or GEAR software programs, please update any associated programs or remove them completely.Code:2: kd> lmvm GEARAspiWDM start end module name fffff880`079be000 fffff880`079cb000 GEARAspiWDM T (no symbols) Loaded symbol image file: GEARAspiWDM.sys Image path: \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys Image name: GEARAspiWDM.sys Timestamp: Mon May 18 13:17:04 2009 (4A1151C0) CheckSum: 000159B4 ImageSize: 0000D000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Phew, I uninstalled Daemon tools and iTunes (and other leftover Apple programs) and got rid of that GEAR driver.
I am currently running Driver verifier again and it's looking good as I've actually managed to log on! I'll keep it running all day and post back if I get anything else.
Thanks :)