[aydyty]

My system has become unstable, don't think it is malware as I run sbybot and avg -

windows vista svc pack 2
HP model m8530f
amd phenom 9550 2.2
5.5 g ram
64 bit

appreciate any help

[Advertisements]

Get WhoCrashed .Install it and click the analyze button.Scroll down to see what caused the problem.

[anuvab1911]

Get WhoCrashed .Install it and click the analyze button.Scroll down to see what caused the problem.

[aydyty]

The Whocrashed log not sure how to interp:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 6/24/2011 4:50:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini062411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1A (0x3451, 0xFFFFF6FD300790A0, 0xFFFFFA8006AFF060, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 6/24/2011 4:50:29 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: 0x1A (0x3451, 0xFFFFF6FD300790A0, 0xFFFFFA8006AFF060, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 6/14/2011 11:15:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000249D01F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 6/12/2011 8:31:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061211-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800024B0C7B, 0xFFFFFFFFFFFFFFFF, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 6/12/2011 8:27:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061211-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800024AE6D7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 6/12/2011 5:06:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800024B66D7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sat 6/11/2011 10:31:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0x0, 0x6, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 5/23/2011 7:03:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini052311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x50 (0xFFFFF800014484B0, 0x0, 0xFFFFF800024484F9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 Thu 5/12/2011 8:40:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x61FEA)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF80002475FEA, 0xFFFFFA60021AEA48, 0xFFFFFA60021AE420)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Wed 5/4/2011 10:18:10 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x50 (0xFFFFF8000195D4B0, 0x0, 0xFFFFF8000295D4F9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
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 Tue 4/19/2011 6:16:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini041911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFA6004D59A1B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 12/27/2010 6:59:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122710-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A4D0)
Bugcheck code: 0xD1 (0x14, 0x2, 0x0, 0xFFFFFA6004847A1B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.

[anuvab1911]

Either or both of AVG and Spybot S&D might be the reason for the BSOD though this isn't reflected in your error log.So do not uninstall AVG or SpyBot S&D first.(I had Avast 6 installed and it gave such different BSODs.Now I have formatted my system and everything works fine.)
Try the following steps first:

This link will be helpful:


http://www.geekstogo...ath-stop-codes/


The MEMORY_MANAGEMENT problem might be due to a bad pagefile on your drive.


1.Start > Control Panel > System > "Advanced" tab > In The "Performance" Section Select "Settings" > "Advanced" tab > In The "Virtual Memory" Section Select "Change". Change the values to 0.

2. Delete C:\pagefile.sys [C: --> Primary Driver in Which Windows Is Installed]

3. Reboot windows

4. Start > Control Panel > System > "Advanced" tab > In The "Performance" Section Select "Settings" > "Advanced" tab > In The "Virtual Memory" Section Select "Change". Change the Values to 1.5 * memory size


Formatting your system might help.Just DO NOT INSTALL Spybot S&D or AVG after that.If the problem persists then you might have a damaged RAM.


If that doesn't work then check if you have a faulty RAM by using MemTest86+.It is an ISO file which you should burn to a disc and boot and start the memory test.It must pass atleast 7 tests.Also check if your PSU/SMPS is fine.You must get yourself HWMonitor and check/compare against the standard values provided with the attachment.

Attached Thumbnails

• 

[rshaffer61]

To further elaborate on the previous instructions I just wanted to add some links.

Download Speedfan (The download link is to the right), and install it. Once it's installed, run the program and post here the information it shows.
The information I want you to post is the stuff that is circled in the example picture I have attached.
To make sure we are getting all the correct information it would help us if you were to attach a screenshot like the one below of your Speedfan results.

To do a screenshot please have click on your Print Screen on your keyboard.

• It is normally the key above your number pad between the F12 key and the Scroll Lock key
• Now go to Start and then to All Programs
• Scroll to Accessories and then click on Paint
• In the Empty White Area click and hold the CTRL key and then click the V
• Go to the File option at the top and click on Save as
• Save as file type JPEG and save it to your Desktop
• Attach it to your next reply

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.

[aydyty]

sorry could you provide a bit more clarity on the first instruction as well (i.e., - do not uninstall spbot and avg - later says do not install until after...

Secondly could you provide a bit detail on the instructions following the "memory mgmt" section, not sue it completly mathches what I see in my Virt Mem section (i.e., convert from auto to manual, etc.) seems there a few more steps?

Thanks

[anuvab1911]

I mean they should not be taken to be as confirmed reason for the problem you have cited.
#First either use HWMonitor or SpeedFan and proceed as directed by rshaffer61.If everything is OK,then the problem might be with your RAM/Virtual Memory(PageFile)/Software Installation.


#Continue with the next step i.e check and reconfigure your PageFile by right-clicking on My Computer,selecting Properties,then Advanced tab and clicking on the Settings Tab under Performance.The select Advanced Tab and click Change under Virtual Memory and set Initial Size to 8.25 GB(8448 MB) and Maximum to anything above 8448 MB.Click Set and OK.



#If still the problem persists,then continue with MemTest86+ test(available on Fedora or Ubuntu discs or use the link provided by the admin).If it traces errors,then you might have to replace your memory stick.Remember Use only single memory stick while testing with MemTest86+ to trace the bad stick.


#If your problem still persists,then uninstall SpyBot S&D and AVG phase by phase to catch the offender.If that fails too,reinstall Windows XP

[aydyty]

Here is the speed fan window - it did not have the info in the lower section per the example:

Attached Thumbnails

• 

[rshaffer61]

OK since it showed nothing then we can try Hardware Monitor
Installation (setup version only)
HWMonitor is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, fans speed.
The program handles the most common sensor chips, like ITE® IT87 series, most Winbond® ICs, and others. In addition, it can read modern CPUs on-die core thermal sensors, as well has hard drives temperature via S.M.A.R.T, and video card GPU temperature.

[aydyty]

Here is th e HWmonitior screen:

[rshaffer61]

Ok that isn't showing voltages either.
So next step is to check in the bios itself and see if it shows the voltages in there.

[aydyty]

Not sure how to do that?

[rshaffer61]

Not sure how to get in to the bios or find the voltages?

[aydyty]

Sorry, yes both

[rshaffer61]

To enter in to 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.
You will now have to look through each of the areas to find the voltages. DO NOT CHANGE ANY SETTINGS IN THE BIOS