Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD regularly


  • Please log in to reply

#31
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK just as a precaution please do the following.



Go to Start then to Run
Type in compmgmt.msc and click Enter
On left side click on Disk Management
On right side you will see you hard drive.
Male sure the window is open all the way on the top right so I can see all the info it has.
Now I need you to take a screenshot and attach it to your next reply. Do the following to take a screenshot while the above is open and showing on your desktop.

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
Make sure the window is open all the way so I can see everything on the top right window.


Attach it to your next reply
  • 0

Advertisements


#32
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
here it is

Attached Thumbnails

  • untitled.JPG

  • 0

#33
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Perfect. Now on to the error message you got last. With the fact it is quoting a memory management issue I want to make sure your memory is good. Please do the following and let me know what the results are.


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). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.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:

Posted Image

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

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:


Posted Image

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.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#34
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
i ran 6 passes on memtest no errors
  • 0

#35
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK memory looks good. Any BSOD's now?
  • 0

#36
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
none yet but il have to wait and see




  • 0

#37
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The last one I see you posted was:

Crash Time : 01/08/2012 07:04:38

That was 2 days ago so it is looking good right now. :thumbsup:
  • 0

#38
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
and thanks for all the help much appreciated




  • 0

#39
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I will continue to watch for updates to make sure everything is good. ;)
  • 0

#40
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
==================================================
Dump File : Mini080512-03.dmp
Crash Time : 05/08/2012 06:25:27
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8052afbc
Parameter 3 : 0xb31a0594
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+53fbc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6223 (xpsp_sp3_gdr.120504-1619)
Processor : 32-bit
Crash Address : ntoskrnl.exe+53fbc
Stack Address 1 : ntoskrnl.exe+d242b
Stack Address 2 : ntoskrnl.exe+6a68c
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080512-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini080512-02.dmp
Crash Time : 05/08/2012 05:07:24
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x0012168c
Parameter 3 : 0xb217bcf0
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080512-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini080512-01.dmp
Crash Time : 05/08/2012 04:47:50
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x80541636
Parameter 3 : 0xb2de1cf0
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6a636
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6223 (xpsp_sp3_gdr.120504-1619)
Processor : 32-bit
Crash Address : ntoskrnl.exe+6a636
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080512-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini080112-01.dmp
Crash Time : 01/08/2012 22:13:22
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00041284
Parameter 2 : 0x008ff001
Parameter 3 : 0x00013ef9
Parameter 4 : 0xc0883000
Caused By Driver : RDPCDD.sys
Caused By Address : RDPCDD.sys+829d000
File Description : RDP Miniport
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.0 (xpclient.010817-1148)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22f5f
Stack Address 1 : ntoskrnl.exe+4c34d
Stack Address 2 : ntoskrnl.exe+4d1f5
Stack Address 3 : ntoskrnl.exe+494ef
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini080112-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

got those blue screens again i dont know whats going on


  • 0

Advertisements


#41
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
All but one seem to be the folloing:

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).




The other RDPCDD.sys has to do with remote desktop connection which in some cases could indicate a infection.
First off was there any driver or program you installed right before this all started?
  • 0

#42
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
i installed facebook messenger but when i tried to start it i got an error something about this programme need to close that it wasent responding also i ran malawarebytes got a adaware called..i watch this...i dont know how that got on my computer


  • 0

#43
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I realize you run your AV and Malwarebytes regularly but can I ask you one thing? Have you been through the Malware forum to have one of our Malware Techs take a deeper look into your system for a hidden infection?
The reason I ask is we have checked all the hardware out and it all shows good.
We could try to do system restore back before the issues started but you would have to be pretty exact when this all started.
  • 0

#44
gandolf

gandolf

    Member

  • Topic Starter
  • Member
  • PipPip
  • 59 posts
i havent been to the malware section.....and the blue screens started from the date on the previous logs
  • 0

#45
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK I would like to see if a system restore will resolve this before sending you to the malware guys.







How To Restore back to a earlier date.


To do a System Restore follow these steps:

 Click Start and then to All Programs
 Scroll to Accessories and then System Tools
 Click on System Restore
 A Welcome screen will come up and you need to click on Restore My Computer To A Earlier Date
 Then click on Next
 Now you will see in the window Select A Restore Point. From here select a date a couple of days before the problem started.
 Then click Next
 On the Confirm Restore Point Selection window verify the Restore Point you chose is correct.
 Close all open programs and click Next
 The computer will now automatically shut down and reboot. When it restarts you will see ”Restoration Complete” page and then click OK
 Once you have made sure that everything is now running correctly then please reply back with the results.
If this does not work then follow the next steps to do a Repair Installation
  • 0






Similar Topics

2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP