BSoD Issues, im having problems with freezing and BSoD

[Grane]

i have been having issues with getting the BSoD for awhile now, ive taken it to Fix My Pc they suggested a new harddrive(cuz they had no idea what was wrong) so i bought a new hard drive, still ended up having issues later down the road. My friend bought me some new RAM 4 gigs to be exact, didnt have problems for awhile, but now they are back. Usually i get a KERNEL_INPAGE_STACK_ERROR i believe is what its called, and i havnt had a chance to catch the bottom numbers because most of the time the computer will restart automatically after the BSoD hits me. I usually am having my problems while talking on Ventrillo and gaming, if anyone can suggest to me a fix for my problems id highly appreciate it.

[thesmokingun]

what games do you play? it sounds like you are having over heating issues, since you've replaced the hard drive and ram. have you checked your gpu temps while playing?

[Grane]

Thx so much guys for your help, im going to talk to my friend about what yall suggested to me, hes more experienced with computers then i am, so ima suggest what yall did to me to him, and hes gonna help me out. i play eve online and city of villians, and a couple other games. My computer isnt the best, just attempted to fix my issues with the harddrive and RAM replacement.. i appreciate your help so much, been trying to get answers for awhile.

[Grane]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

************************************************************
WARNING: Dump file has been truncated.  Data may be missing.
************************************************************
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Fri Jul  3 01:00:47.906 2009 (GMT-5)
System Uptime: 0 days 0:18:16.650
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
..............
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 8906ca18, 8906cb8c, 805d1142}

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
Probably caused by : winsrv.dll ( winsrv!_ValidateEH3RN+0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8906ca18, Terminating object
Arg3: 8906cb8c, Process image file name
Arg4: 805d1142, Explanatory message (ascii)

Debugging Details:
------------------

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

PROCESS_OBJECT: 8906ca18

IMAGE_NAME:  winsrv.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  411096b7

FAULTING_MODULE: 4a680000 csrss

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  f76f6d10 -- (.exr 0xfffffffff76f6d10)
ExceptionAddress: 75b8f9e5 (winsrv!_ValidateEH3RN)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000008
   Parameter[1]: 75b8f9e5
   Parameter[2]: c0000056
Inpage operation failed at 75b8f9e5, due to I/O error c0000056

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

DEFAULT_BUCKET_ID:  DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

EXCEPTION_PARAMETER1:  00000008

EXCEPTION_PARAMETER2:  75b8f9e5

EXCEPTION_PARAMETER3:  c0000056

IO_ERROR: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.

EXCEPTION_STR:  0xc0000006_c0000056

FAULTING_IP: 
winsrv!_ValidateEH3RN+0
75b8f9e5 ??              ???

BUGCHECK_STR:  0xF4_IOERR_C0000056

FOLLOWUP_IP: 
winsrv!_ValidateEH3RN+0
75b8f9e5 ??              ???

SYMBOL_NAME:  winsrv!_ValidateEH3RN+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: winsrv

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  0xF4_IOERR_C0000056_winsrv!_ValidateEH3RN+0

BUCKET_ID:  0xF4_IOERR_C0000056_winsrv!_ValidateEH3RN+0

Followup: MachineOwner
---------

That is what it is saying. He deleted the csrss.exe file, which in other forums people say if it's in the wrong place or if there is a duplicate it is a nasty virus.

Hopefully this can help yall to helping me solve my issues.


P.S. I will run memtest over night and tell you if i got any errors and reply with my temps.

[Grane]

Originally Posted by thesmokingun

what games do you play? it sounds like you are having over heating issues, since you've replaced the hard drive and ram. have you checked your gpu temps while playing?

I have been getting these weird blue lines along my screen while playing EVE Online, do you think that could have anything to do with my other problems?

[thesmokingun]

this is starting to sound like you could have a few things going on...
you might want to run through the malware removal steps before doing anything else.
http://forums.majorgeeks.com/showthread.php?t=35407

[Grane]

My friend helped me get that posted, i got BSoD again last night after he went to bed, so ill get that info from the most recent BSoD up here later.

[Grane]

I ran the clean-up you suggested and I will post the log files here for you.

[Grane]

Here is the 5th one.

[chaslang]

Your BSOD and freezing issues may not be due to malware. Let's cleanup what I do see and then decide.

First you are way out of date with your version of Malwarebytes. Please run Malwarebytes and click the Update tab. Then click the Check for Updates button so you update to the current version of the program and database. Then run a new scan with it too. Attach the new log.


Uninstall the below software:
Viewpoint Media Player <-- should have been uninstalled in step 1 of the READ ME

Run C:\MGtools\analyse.exe by double clicking on it (Note: if using Vista, don't double click, use right click and select Run As Administrator). This is really HijackThis (select Do a system scan only) and select the following lines but DO NOT CLICK FIX until you exit all browser sessions including the one you are reading in right now:

R3 - URLSearchHook: (no name) - *{CFBFAE00-17A6-11D0-99CB-00C04FD64497} - (no file)
O2 - BHO: (no name) - {02478D38-C3F9-4efb-9B51-7695ECA05670} - (no file)
O2 - BHO: (no name) - {5C255C8A-E604-49b4-9D64-90988571CECB} - (no file)
O3 - Toolbar: (no name) - {A057A204-BACC-4D26-9990-79A187E2698E} - (no file)
O4 - HKCU\..\Run: [MSMSGS] "C:\Program Files\Messenger\msmsgs.exe" /background

After clicking Fix, exit HJT.

Now run this Disable/Remove Windows Messenger to remove Windows Messenger. Do not confuse Windows Messenger with MSN Messenger because they are not the same. Windows Messenger is a frequent cause of popups.


Now we need to use ComboFix to remove a bunch of malware files.

• Make sure that combofix.exe that you downloaded while doing the READ & RUN ME is on your Desktop but Do not run it!
  • If it is not on your Desktop, the below will not work.
• Also make sure you have shut down all protection software (antivirus, antispyware...etc) or they may get in the way of allowing ComboFix to run properly.
• If ComboFix tells you it needs to update to a new version, make sure you allow it to update.
• Open Notepad and copy/paste the text in the below quote box into it:

KILLALL::
Driver::
cggmcuqj
FGXSCSI

File::
c:\windows\system32\drivers\enmph.sys
c:\windows\system32\DRIVERS\fgxscsi.sys

Folder::
C:\0d361375df72de4b25e15043030c
C:\26037aecf2c307a2cec4f27c926f40
C:\401a37f86220dcae0e

Registry::
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{02478D38-C3F9-4efb-9B51-7695ECA05670}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{5C255C8A-E604-49b4-9D64-90988571CECB}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{A057A204-BACC-4D26-9990-79A187E2698E}]

• Save the above as CFscript.txt and make sure you save it to the same location (should be on your Desktop) as ComboFix.exe
• At this point, you MUST EXIT ALL BROWSERS NOW before continuing!
• You should have both the ComboFix.exe and CFScript.txt icons on your Desktop.
• Now use your mouse to drag CFscript.txt on top of ComboFix.exe
• Follow the prompts.
• When it finishes, a log will be produced named c:\combofix.txt
• I will ask for this log below

Note:

Do not mouseclick combofix's window while it is running. That may cause it to stall.

Now run Ccleaner. Only use the Run Cleaner button. Do not run anything else on any other forms.

Now download the current version of MGtools and save it to your root folder. Overwrite your previous MGtools.exe file with this one.

Run MGtools.exe ( Note: If using Vista make sure UAC is still disabled. Also don't double click on it, use right click and select Run As Administrator )


Now attach the below log:

• C:\ComboFix.txt
• C:\MGlogs.zip

Make sure you tell me how things are working now!