Memory Loss!
Started by
Wynn_M
, May 09 2011 08:37 AM
#1
Posted 09 May 2011 - 08:37 AM
#2
Posted 09 May 2011 - 10:27 AM
Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
Either:
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Thanks to Broni for the instructions and program
This program checks for any drivers which may have been causing your computer to crash....
Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
- Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
- Double-click VEW.exe
- Under 'Select log to query', select (as appropriate):
- Application
- System
- Under 'Select type to list', select (as appropriate):
- Error
- Information
- Warning
Either:
- Click the radio button for 'Number of events'
Type 3 in the 1 to 20 box (or any number from 1 to 20)
Then click the Run button.
Notepad will open with the output log.
- Click the radio button for 'Date of events'
In the From: boxes type today's date (presuming the crash happened today) 07 05 2011
In the To: boxes type today's date (presuming the crash happened today) 07 05 2011
Then click the Run button.
Notepad will open with the output log.
Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Thanks to Broni for the instructions and program
#3
Posted 09 May 2011 - 01:18 PM
Hi, Please find the scan results from VEW for system and applications below. During the exercise a message from MS OFFICE 2003 popped up saying there was a .cab file missing and did I want to instal it now. I put the CD in and chose repair as it was already installed. The job was done on the spot. I hope the logs will reveal the problem/s OK. Thank you.
Wynn_M
Vino's Event Viewer v01c run on Windows XP in English
Report run at 09/05/2011 7:30:37 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/05/2011 6:54:20 PM
Type: error Category: 0
Event: 1 Source: sr
The System Restore filter encountered the unexpected error '0xC000007F' while processing the file 'Dd2.exe' on the volume 'HarddiskVolume2'. It has stopped monitoring the volume.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 04/05/2011 6:58:48 AM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 02/05/2011 11:28:48 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
-----------------------------------------------------------------------------------------
Vino's Event Viewer v01c run on Windows XP in English
Report run at 09/05/2011 8:13:32 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 08/05/2011 6:34:47 PM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 0, P2 moaccapability, P3 3.0.8107.0, P4 5, P5 0, P6 unspecified, P7 unspecified, P8 NIL, P9 NIL, P10 NIL.
Log: 'Application' Date/Time: 05/05/2011 4:47:01 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application EPSetup.exe, version 4.4.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 04/05/2011 4:01:37 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module mshtml.dll, version 8.0.6001.19046, fault address 0x001f3a73.
Log: 'Application' Date/Time: 03/05/2011 12:28:43 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application GH-EchoesOfSorrow.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 01/05/2011 1:54:24 PM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 0x80070003, P2 moac, P3 cachereset, P4 3.0.8107.0, P5 unspecified, P6 unspecified, P7 unspecified, P8 NIL, P9 NIL, P10 NIL.
Log: 'Application' Date/Time: 01/05/2011 1:36:58 PM
Type: error Category: 0
Event: 5000 Source: MSSecurityEssentials
The event description cannot be found.
Wynn_M
Vino's Event Viewer v01c run on Windows XP in English
Report run at 09/05/2011 7:30:37 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/05/2011 6:54:20 PM
Type: error Category: 0
Event: 1 Source: sr
The System Restore filter encountered the unexpected error '0xC000007F' while processing the file 'Dd2.exe' on the volume 'HarddiskVolume2'. It has stopped monitoring the volume.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 06/05/2011 12:07:39 PM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
Log: 'System' Date/Time: 05/05/2011 10:26:53 AM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 04/05/2011 6:58:48 AM
Type: error Category: 0
Event: 11 Source: Cdrom
The driver detected a controller error on \Device\CdRom1.
Log: 'System' Date/Time: 02/05/2011 11:28:48 AM
Type: error Category: 0
Event: 7 Source: Cdrom
The device, \Device\CdRom1, has a bad block.
-----------------------------------------------------------------------------------------
Vino's Event Viewer v01c run on Windows XP in English
Report run at 09/05/2011 8:13:32 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 08/05/2011 6:34:47 PM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 0, P2 moaccapability, P3 3.0.8107.0, P4 5, P5 0, P6 unspecified, P7 unspecified, P8 NIL, P9 NIL, P10 NIL.
Log: 'Application' Date/Time: 05/05/2011 4:47:01 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application EPSetup.exe, version 4.4.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 04/05/2011 4:01:37 PM
Type: error Category: 0
Event: 1000 Source: Application Error
Faulting application iexplore.exe, version 8.0.6001.18702, faulting module mshtml.dll, version 8.0.6001.19046, fault address 0x001f3a73.
Log: 'Application' Date/Time: 03/05/2011 12:28:43 PM
Type: error Category: 101
Event: 1002 Source: Application Hang
Hanging application GH-EchoesOfSorrow.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Log: 'Application' Date/Time: 01/05/2011 1:54:24 PM
Type: error Category: 0
Event: 5000 Source: MPSampleSubmission
EventType mptelemetry, P1 0x80070003, P2 moac, P3 cachereset, P4 3.0.8107.0, P5 unspecified, P6 unspecified, P7 unspecified, P8 NIL, P9 NIL, P10 NIL.
Log: 'Application' Date/Time: 01/05/2011 1:36:58 PM
Type: error Category: 0
Event: 5000 Source: MSSecurityEssentials
The event description cannot be found.
#4
Posted 09 May 2011 - 02:57 PM
OK first issue I notice is Dd2.exe which has been identified and known to be a virus.
Therefore I am stopping this for now so that you can check your system out with our malware people to make sure you are clean.
I suspect that you have some malware on your computer causing issues that we are not able to solve through means we can use here in the Tech Forums. I suggest you read the 'Start Here' topic found HERE. With these self-help tools you have a high chance of fixing the problems on your own. If you are still having problems after following Step 3 of the guide, continue with Step 4 and 5 and post in the Malware Forum. If you are unable to run any programs, Please create a topic stating what you have tried so far and that you are unable to run any programs. Also, Please do NOT post the logs in this thread.
If you are still having issues after the malware expert gives you a clean bill of health, Please return to THIS thread and we will pursue other options to help you solve your current problem(s).
Add a link to this topic so that malware tech can see what steps have been taken here
Therefore I am stopping this for now so that you can check your system out with our malware people to make sure you are clean.
I suspect that you have some malware on your computer causing issues that we are not able to solve through means we can use here in the Tech Forums. I suggest you read the 'Start Here' topic found HERE. With these self-help tools you have a high chance of fixing the problems on your own. If you are still having problems after following Step 3 of the guide, continue with Step 4 and 5 and post in the Malware Forum. If you are unable to run any programs, Please create a topic stating what you have tried so far and that you are unable to run any programs. Also, Please do NOT post the logs in this thread.
If you are still having issues after the malware expert gives you a clean bill of health, Please return to THIS thread and we will pursue other options to help you solve your current problem(s).
Add a link to this topic so that malware tech can see what steps have been taken here
#5
Posted 11 May 2011 - 07:45 AM
Hello rshaffer61
I responded to your instructions email on 5/10 and pasted results in Malware forum under Memory Loss on May 9th.
Since then I have saved another log from VEW and also from WhoCrashed. BlueScreenView didn't come up with any results.
Do you want me to paste the latest results in another reply on Malware forum?
Wynn_M
I responded to your instructions email on 5/10 and pasted results in Malware forum under Memory Loss on May 9th.
Since then I have saved another log from VEW and also from WhoCrashed. BlueScreenView didn't come up with any results.
Do you want me to paste the latest results in another reply on Malware forum?
Wynn_M
#6
Posted 11 May 2011 - 07:53 AM
Nope wait for the malware tech to respond. If no response in 3 days then follow the instructions in my previous post and post a topic in the Waiting Room with a link to your malware Topic.
I will monitor the Malware topic also but I cannot assist with it.
I will monitor the Malware topic also but I cannot assist with it.
#7
Posted 11 May 2011 - 08:29 AM
rshaffer61
I don't want to hassle you about this, however, I've discovered something which may be the answer to this problem and I'm worried that its causing damage. I took a look at the BIOS bootup - all devices are disabled:
CDRom: PS PhillipsD, HDD:3M-STM3250318A, and a third no name disabled - No IDE Master/Slave detected.
Does this info help?
Wynn_M
I don't want to hassle you about this, however, I've discovered something which may be the answer to this problem and I'm worried that its causing damage. I took a look at the BIOS bootup - all devices are disabled:
CDRom: PS PhillipsD, HDD:3M-STM3250318A, and a third no name disabled - No IDE Master/Slave detected.
Does this info help?
Wynn_M
#8
Posted 11 May 2011 - 09:15 AM
Try resetting the bios to default. It should be one of the choices when you first enter bios.
#9
Posted 11 May 2011 - 11:52 AM
Boot default = CDROM:PS Philips.DVDR1640P Now Set to default.
2nd option: HDD 3M-STM3250318A5
3rd option: Disabled
Rebooting/Closing down - Error is in P1UTL.exe
Wynn_M
I'm not comfortable working in the BIOS - Driver Detective previously came up with an update for the chipset driver. The info I found on this one states that chipsets should be installed immediately after installing the OS and before any other drivers - too late for that. Scary!! Any way around it?
2nd option: HDD 3M-STM3250318A5
3rd option: Disabled
Rebooting/Closing down - Error is in P1UTL.exe
Wynn_M
I'm not comfortable working in the BIOS - Driver Detective previously came up with an update for the chipset driver. The info I found on this one states that chipsets should be installed immediately after installing the OS and before any other drivers - too late for that. Scary!! Any way around it?
#10
Posted 11 May 2011 - 12:07 PM
Can't install chipset driver unless you can get into windows. Did you save the settings before exiting the bios?
Usually this is accomplished by clicking either F10 or clicking on the line that saves Save and Exit
You then should be asked to click Y to verify everything.
Usually this is accomplished by clicking either F10 or clicking on the line that saves Save and Exit
You then should be asked to click Y to verify everything.
#11
Posted 11 May 2011 - 12:32 PM
Don't understand about getting into Windows! Yes, I saved changes with F10.
#12
Posted 11 May 2011 - 12:46 PM
In other words the chipset driver is part of the mobo. To install it you have to be in windows to do that.
You are able to get into windows but until the malware tech has declared your system healthy and free of any infections we are spinning our wheels here.
Be patient as they are very busy there.
You are able to get into windows but until the malware tech has declared your system healthy and free of any infections we are spinning our wheels here.
Be patient as they are very busy there.
#13
Posted 25 May 2011 - 07:44 AM
Hello rshaffer61,
Seems my PC now has a clean bill of health, bugwise anyway, Now I'd like to continue with the unsolved problems we started with previously if you are available and willing to work with me.
On completing the malware forum problems there is still an annoying reboot/closedown OX/can't be read which foiled both Dakeyras and myself. Seems its not malware. You know about all the chipset updates waiting to be dealt with from our previous contact but it might be exacerbated by a faulty bootup sequence.
The PC is booting up into Windows XP Home Edition just now. Don't know how that happened except I may have unwittingly changed the bootup sequence when initially trying to find the default Master sequence - CDROM: PM-Pioneer DVD-ROM ATAPIM which is the default for this PC. Secondary is CDROM; PS PHILLIPS DVDR1640P. However, although I found the sequence via F8 and chose the correct one it stubbornly boots into WinXP Home Edition with a second choice of restoration. I'm not comfortable working with the BIOS. Please can you help me with this? Thank you.
Wynn_M
Seems my PC now has a clean bill of health, bugwise anyway, Now I'd like to continue with the unsolved problems we started with previously if you are available and willing to work with me.
On completing the malware forum problems there is still an annoying reboot/closedown OX/can't be read which foiled both Dakeyras and myself. Seems its not malware. You know about all the chipset updates waiting to be dealt with from our previous contact but it might be exacerbated by a faulty bootup sequence.
The PC is booting up into Windows XP Home Edition just now. Don't know how that happened except I may have unwittingly changed the bootup sequence when initially trying to find the default Master sequence - CDROM: PM-Pioneer DVD-ROM ATAPIM which is the default for this PC. Secondary is CDROM; PS PHILLIPS DVDR1640P. However, although I found the sequence via F8 and chose the correct one it stubbornly boots into WinXP Home Edition with a second choice of restoration. I'm not comfortable working with the BIOS. Please can you help me with this? Thank you.
Wynn_M
#14
Posted 25 May 2011 - 08:41 AM
When you say it is booting but stubbornly what do you mean exactly?
Are you given a choice when booting to push any key to boot to cdrom?
If so don't click a key and it will boot normally into windows then.
This is normal behavior when the cdrom is the first boot drive.
This is the optimal setting in case of a problem you can still boot using the cdrom drive and a boot disk.
The chipset driver is the most important item to make sure is up to date.
I want to check the memory now to make sure that is not the issue.
If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:
8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:
10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.
To change Boot Sequence in your BIOS
Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
The running program will look something like this depending on the size and number of ram modules installed:
It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.
The following image is the test results area:
The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
Are you given a choice when booting to push any key to boot to cdrom?
If so don't click a key and it will boot normally into windows then.
This is normal behavior when the cdrom is the first boot drive.
This is the optimal setting in case of a problem you can still boot using the cdrom drive and a boot disk.
The chipset driver is the most important item to make sure is up to date.
I want to check the memory now to make sure that is not the issue.
If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:
8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:
10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.
To change Boot Sequence in your BIOS
Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.
The running program will look something like this depending on the size and number of ram modules installed:
It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.
The following image is the test results area:
The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
#15
Posted 25 May 2011 - 11:20 AM
Also just as a suggestion try this.
ok I need you to do the following and let me know what it says
Click the Start and then Right click My Computer
Select Manage and In the Computer Management window, select Device Manager
In the right pane, click to expand IDE ATA/ATAPI controllers
The click on the + sign next to your CD/DVD drive controller which will most likely be the Secondary Controller
Right click on the drive and select Uninstall
Click the OK button.
Reboot to make sure all settings take affect and reply back with your results
ok I need you to do the following and let me know what it says
Click the Start and then Right click My Computer
Select Manage and In the Computer Management window, select Device Manager
In the right pane, click to expand IDE ATA/ATAPI controllers
The click on the + sign next to your CD/DVD drive controller which will most likely be the Secondary Controller
Right click on the drive and select Uninstall
Click the OK button.
Reboot to make sure all settings take affect and reply back with your results
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users