[cookieman264]

Hello,

Just recently my computer started going crazy on me. It has been randomly rebooting at any given time - sometimes right after logging on Windows, or sometimes an hour later. I have tried reformatting/reinstalling Windows, but the problem is still persisting. It's really frustrating me.

When I see the blue screen of death, I see these error codes: STOP 0x000000F (0x000000D, 0x000000, 0x000000, 0x000000)

Here are some logs from BlueScreenView:

Mini032211-01.dmp 3/22/2011 4:04:26 PM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000 ntoskrnl.exe ntoskrnl.exe+47ee6 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) 32-bit C:\WINDOWS\Minidump\Mini032211-01.dmp 2 15 2600 65,536

Mini032211-03.dmp 3/22/2011 4:20:57 PM UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000 yukonwxp.sys yukonwxp.sys+7f70 NDIS5.1 Miniport Driver for Marvell Yukon Gigabit Ethernet Adapter Marvell Yukon Gigabit Ethernet Adapter Marvell Semiconductor Inc. 6.28 built by: WinDDK 32-bit C:\WINDOWS\Minidump\Mini032211-03.dmp 2 15 2600 65,536

Mini032211-11.dmp 3/22/2011 11:22:07 PM UNEXPECTED_KERNEL_MODE_TRAP 0x1000007f 0x0000000d 0x00000000 0x00000000 0x00000000 tcpip.sys tcpip.sys+1aead TCP/IP Protocol Driver Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) 32-bit C:\WINDOWS\Minidump\Mini032211-11.dmp 2 15 2600 90,112


Mini032211-12.dmp 3/22/2011 11:27:29 PM UNEXPECTED_KERNEL_MODE_TRAP 0x1000007f 0x0000000d 0x00000000 0x00000000 0x00000000 tcpip.sys tcpip.sys+3ede TCP/IP Protocol Driver Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) 32-bit C:\WINDOWS\Minidump\Mini032211-12.dmp 2 15 2600 90,112

Can anyone help me out?

Edited by cookieman264, 23 March 2011 - 01:06 AM.

[Advertisements]

Hi Cookieman264. Can I join you in the "Random Reboot" discussion? I get a unrequested restart randomly on my PC also. G2G have helped me eliminate any malware problems and I was planning to move to this Forum to start a thread based on a possible hardware fault. My approach is to look for G2G help in understanding what the "Event Viewer" log entries are telling me about the source of the problem. Have you tried that approach? Also, how do you get the BSofD reading? Ta, LiamB

[LiamB]

Hi Cookieman264. Can I join you in the "Random Reboot" discussion? I get a unrequested restart randomly on my PC also. G2G have helped me eliminate any malware problems and I was planning to move to this Forum to start a thread based on a possible hardware fault. My approach is to look for G2G help in understanding what the "Event Viewer" log entries are telling me about the source of the problem. Have you tried that approach? Also, how do you get the BSofD reading? Ta, LiamB

[rshaffer61]

Direct to: LiamB

Please start your own topic
Although your issue may seem similar there can be other factors that may need to be resolved.
By bumping on someone's topic it makes it confusing for the tech to understand who they are helping. This can in turn cause the wrong support to be given and can cause instability or worse to happen to your system.
Please post more information as to your exact issue in your topic. Include any error messages you get as well as your system specs. This will help us to assist you more efficiently.
Thank you for your cooperation.

[rshaffer61]

cookieman264 please do the following and let us know the results.

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem







Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions



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.

[cookieman264]

Thank you rshaffer61 for the extensive reply! At the moment I am trying to run chkdsk on my computer. However it keeps crashing/rebooting during the chkdsk process, at least 10 times now. It always reboots at stage 4 of 5 at around 33%, where it says "CHKDSK is verifying file data." I pulled the internet cord out to see if it might help, but it's still just crashing. I'm not sure what's wrong?

[rshaffer61]

ok I need to see something real quick. Boot back into windows and do the following.

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

[cookieman264]

Okay here is the screenshot.

[rshaffer61]

WOW some hot temps showing there.
Is this a laptop or Desktop system?

[cookieman264]

This is a desktop. I didn't realize I have a temperature problem. Do I have one?

[rshaffer61]

According to speedfan you do.
When was the last time you opened the case and blew out the system with a can of air?
Paying close attention to the fans.
NOTE: Do not allow the fan blades to turn freely while blowing air in them. Use a Q-tip or something to hold the fans blades stationary.

[cookieman264]

I air dusted my computer the first thing after my computer started crashing. I see that 127C is pretty hot.. but where would that be? I focused on dusting my GPU, VGA fan, and two case fans.

[rshaffer61]

I'm worried more about the CPU and PSU fans. Those are the two that over heating will occur most frequently.

[cookieman264]

Well all the fans everything seems to be clear of any major dust, and I don't see any area that seems to be overheating. But I noticed that it always says 127C every time I open SpeedFan. Perhaps it is a false alarm? I would think it would fluctuate at least a little bit.

[rshaffer61]

Try this program to verify the temps.




Download SIW from HERE and get the Standalone English version
It will install itself and when finished

Then Click on SIW Icon to run program
On the left side click on the Motherboard directory and then on the right, copy and paste the information in your next reply
On the left side click on the Sensors directory and then on the right, copy and paste the information in your next reply

http://www.gtopala.c...w-download.html

[cookieman264]

Well I just found out that my problem was bad RAM. I wasn't able to run memtest or any diagnostic tools because my computer was so unstable that Windows XP setup would crash.

I had tried using only one ram stick at a time, and my computer would still crash. Then I tried replacing both sticks entirely with some old ones, and now it works just fine! Is this possible that BOTH of my sticks are faulty? I bought one of them a year ago, but both are 1GB sticks (one is Corsair and one is Kingston).