[busybelle]

Hi, Can someone please help me? Rorschach112 sent me over from Newbie.
My Laptop started crashing on me a few weeks ago producing a blue screen reading Error and memory dump..
Last week it started to run very slowly and i thought i had picked up a nasty. I have went through every procedure with Newbie help and am assured that it is clean with no nasties after having ran numerous scans.
FYI http://www.newbie.or...amp;#entry47953

I cannot run Malwarebytes in regular mode. It freezes after 20 seconds and i have to reboot. I can however run Malwarebytes in safe mode and it says that it is clean.

The laptop is very slow and takes a few minutes to move between programs and crashes every hour or so.
It is not a year old and has had a new hard drive about 5 months ago as the first one died..

I am using Vista. I am only using 20% of the memory space.

Are there any checks i can run to see why it is so slow?
I constantly clean out everything and have AVG, Malwarebytes anti spy, TFC. spywareblaster.

Any help would be much appreciated,
thanks

[Advertisements]

Hello,

What is the blue screen error you are getting?

Download BlueScreenView, and run it to give us some info on your BSOD.

• Open the zipped archive.
• Extract all contents.
• Double-click on BlueScreenView.exe 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.

Kudos and thanks to Broni for instructions and program!

Could be a Ram/Memory problem:

A. 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.
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.

(Hope I'm not stealing this canned fix rshaffer61 or Broni.. it's very well written, thanks! )

Report back what you find, I'll wait patiently

-Tony

[ersatz]

Hello,

What is the blue screen error you are getting?

Download BlueScreenView, and run it to give us some info on your BSOD.

• Open the zipped archive.
• Extract all contents.
• Double-click on BlueScreenView.exe 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.

Kudos and thanks to Broni for instructions and program!

Could be a Ram/Memory problem:

A. 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.
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.

(Hope I'm not stealing this canned fix rshaffer61 or Broni.. it's very well written, thanks! )

Report back what you find, I'll wait patiently

-Tony

[busybelle]

==================================================
Dump File : Mini030310-01.dmp
Crash Time : 3/3/2010 2:55:16 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc040c6c0
Parameter 2 : 0xc0000185
Parameter 3 : 0x2418f8c0
Parameter 4 : 0x818d8000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini030310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini030210-01.dmp
Crash Time : 3/2/2010 7:32:40 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc04d78f0
Parameter 2 : 0xc0000185
Parameter 3 : 0x201de8c0
Parameter 4 : 0x9af1e000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini030210-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini030110-02.dmp
Crash Time : 3/1/2010 3:44:50 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc044b908
Parameter 2 : 0xc0000185
Parameter 3 : 0x046638c0
Parameter 4 : 0x89721000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini030110-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini030110-01.dmp
Crash Time : 3/1/2010 11:12:30 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x84ae8038
Parameter 2 : 0x00000000
Parameter 3 : 0x9a11fd3d
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+9838d
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini030110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022810-06.dmp
Crash Time : 2/28/2010 8:55:52 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0xb3c40000
Parameter 2 : 0x00000000
Parameter 3 : 0x81e377d4
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+9838d
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022810-06.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022810-05.dmp
Crash Time : 2/28/2010 8:29:18 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x84b4100b
Parameter 2 : 0x00000000
Parameter 3 : 0x9a520f60
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+9838d
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022810-05.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022810-04.dmp
Crash Time : 2/28/2010 8:07:32 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000007
Parameter 2 : 0x00021f7b
Parameter 3 : 0x00000001
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+40ed
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022810-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022810-03.dmp
Crash Time : 2/28/2010 7:51:21 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x84af700b
Parameter 2 : 0x00000000
Parameter 3 : 0x9a523f60
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+9838d
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022810-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022810-02.dmp
Crash Time : 2/28/2010 7:23:06 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x81e60d95
Parameter 3 : 0xa3290a54
Parameter 4 : 0x00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+16c66
File Description : Microsoft Filesystem Filter Manager
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022810-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022810-01.dmp
Crash Time : 2/28/2010 5:26:01 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc04eb2e0
Parameter 2 : 0xc0000185
Parameter 3 : 0x34d988c0
Parameter 4 : 0x9d65c000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022810-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

==================================================
Dump File : Mini022710-01.dmp
Crash Time : 2/27/2010 3:04:31 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc043dd98
Parameter 2 : 0xc0000185
Parameter 3 : 0x242698c0
Parameter 4 : 0x87bb3008
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18160 (vistasp2_gdr.091208-0542)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\Mini022710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
==================================================

[ersatz]

Don't forget to post that memtest when it's finished, but also check your disk for errors.

To run chkdsk:

(For Vista/7)
Start > (type in:) cmd

In the prompt, type: chkdsk /r
Choose Y to run on next restart.
Restart your computer.

Best regards,

-Tony

[busybelle]

thanks Tony, I am working through it now...might take me a while, i am no wizz lol
Belle

[ersatz]

Alright No rush, I'll be here.

Best regards-

[busybelle]

Hi, The memtest came up with 0 errors after 5 passes. I did not know how to save the report but copied most of it if you need it.
Can you explain how to make chkdsk /r run..
I typed it in and it said access denied..
I dont know where to type Y.
sorry,

thanks Belle

[ersatz]

Sorry, I forgot:

Start > (type in:) cmd
(RIGHT-CLICK) cmd, and choose Run as Administrator.

This is known as an Elevated Command Prompt.
Then:

In the prompt, type: chkdsk /r
Choose Y to run on next restart.
Restart your computer.

-Tony

[busybelle]

Tony, I am runnning the chkdsk /r like you asked..
It has been sitting at 11% for over an hour now. Is this normal? Looks like it is stuck!
the screen has lots of replaced bad clusters up until the 11% stage.
Should i just leave it like this to see if it finishes?

ps. it is also making a litle ticking noise

Thanks
Belle

Edited by busybelle, 05 March 2010 - 07:28 AM.

[rshaffer61]

Hi everyone just a peek in and to add some advice.
It is normal for chkdsk /r to take some time. In some instances a couple of hours. Since you state the bad cluster issue then yes it will appear to halt or stall. It may even seem to go backwards at times. Now that you have seen the errors and it fixing them I would suggest that once it is done you rerun the program again to make sure it got everything.
DO NOT TURN SYSTEM OFF OR REBOOT IT> This may result in damage to the hard drive and or the system to a point that you will have to format and start over. As fas as the ticking sound you are hearing... is this the first time you have heard this?
The ticking sound from a hard drive can be the Tick of Death as it is called and would point to a hard drive failure. If this does turn out to be the case then a immediate backup is needed and replacement of the hard drive is needed.
Again please let chkdsk /r finish on its own. It will reboot the system normally on it's own when it is finished.

[busybelle]

Hi, Thanks for the reply.
Ok i will leave it run all day if i have to.
This is the first time i have noticed the ticking. My laptop is not a year old and is already on its 2nd hard drive:( rather than get a 3rd i may just replace it, never buying this brand again!!
What do i do if it does not go past this point? It has not move in 2 hrs now.
i am starting to think throw it in the garbage..
I have it backed up to date.
Thanks again, i will let you know the outcome.
Belle

[rshaffer61]

What do i do if it does not go past this point? It has not move in 2 hrs now.

At that point we would have to look at a recovery.

[busybelle]

Update:
I am 4hrs into the scan and it has not moved past 11% for the past 3hrs.
thanks

[ersatz]

This is very odd. I just replaced the hard drive on my laptop due to failure, and every since I've been on this website (3 days) I have seen about 4 more cases where disk drive failure is the most probably cause... Had no idea it was this common; Perhaps it's me and I'm jinxing it.

Did the chkdsk every finish? Which stage was it at of 11% and what file (if any) was it going through on that point?

-Tony

[busybelle]

Stopped at 95852 of 129840 files processed. It is doing nothing now, just ticking away