New
#1
BSOD when performing computer search
I get BSOD EVERY time I perform a full computer search.
Also on other occasions, but I cannot specify the scenario(s).
Thank you !
I get BSOD EVERY time I perform a full computer search.
Also on other occasions, but I cannot specify the scenario(s).
Thank you !
Hi yoho
Run a SFC /SCANNOW
Click on type CMD inside Search programs and files . Once CMD comes up under Programs (1) right click and choose Run as administrator . Click on Yes button inside the User Access Control window. Command prompt should open up to C:\Windows\System32>_ . Type the command below inside the Command Prompt
SFC /scannowPress <ENTER>
If it finds a corrupted files run that 3 times total with Restarts of the PC in between. Once that is complete run chkdsk
Open up the command prompt as stated above and run this command . After you typed in the command Press Y and Enter and restart your computer manually
chkdsk C:\ /F /R
NoteThere are spaces in between /F and /R
Uninstall this software .
Once you uninstalled Babylon from the Control Panel run this tool belowCode:C:\Program Files\Babylon
AdwCleaner
No code has to be inserted here.
Before starting this utility, close all open programs and internet browsers.
Right Click on AdwCleaner.exe choose Run as Administrator.
Click on Delete, then confirm each time with Ok.
NoteThe PC will restart on its own
Once you're back on the desktop . Run Malwarebytes
MalwareBytes click on Download Now
After the installation has completed uncheck the Trial start of MalwareBytes Pro ( see image below )
Once completed click on the Logs tab and upload the log with your post.
TipMight want to Download both of the programs first so you won't have to come back and download one at a time
Also you would want to run a memtest . Let it run over night. If you get any errors stop the test and test each memory stick on every slot .
RAM - Test with Memtest86+
NoteYou will need a USB FLASH DRIVE
Last edited by VistaKing; 18 Apr 2013 at 13:04.
Thanks for your help. Logs attached.
Why did you pinpoint Babylon? I've been using it for a long time...
This may provide the answer, if I searched it correctly:
After performing all steps described by VistaKing, I was able to complete computer search. However, today, while only Outlook & Chrome were open (not while searching) - computer crashed again :-(
BlueRobot - I had only Babylon application, not the toolbar
The dump file you uploaded
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000020, a pool block header size is corrupt. Arg2: fffff900c0b24000, The pool entry we were looking for within the page. Arg3: fffff900c0b24630, The next pool entry. Arg4: 0000000025630000, (reserved) Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 BUGCHECK_STR: 0x19_20 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b5100 GetUlongFromAddress: unable to read from fffff800030b51c0 fffff900c0b24000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: csrss.exe
Also having issues with this driver
Reinstall MalwareBytesCode:mbam.sys
Uninstall AVG and install MSE
No code has to be inserted here.
No code has to be inserted here.
MSE
No code has to be inserted here.
Run a virus scan with MSE . Please
Code:BugCheck 19, {20, fffff900c0b24000, fffff900c0b24630, 25630000} Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )RAM and the hard-drive can also be problems of this bugcheck.Code:Usual causes: Device driver
The header for the pool allocation has become corrupted, each header also has a pool tag which describes the purpose of the allocation. There seems to be problems with how Windows is allocating memory to drivers.
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
-----------------------------
How many passes did you run MemTest86+ for? It should have been least 7-9 passes. What were the results of chkdsk (Disk Check)?
Remove AVG as VistaKing has already mentioned, this is known to cause BSODs, and isn't the best real-time protection program to use.
Driver Verifier is active
AVG was removed, and MSE performed full scan
Where can I find chkdsk logs?
Check Disk (chkdsk) - Read Event Viewer Log
The recent crash dump is not revealing much information so far, keep Driver Verifier running for least 24 hours.
I've identified a new crash pattern - whenever I open the fonts dialog inside Microsoft Wrod