[othersteve]

I have to say, if not networking-related, it sure seems to be some sort of memory access problem.

I think the next thing we should do is this:

1. Click Start > All Programs > Accessories > RIGHT-click Command Prompt and choose Run as Administrator.
2. Type chkdsk /r and press ENTER.

Let the disk check complete.

Next, I would almost suggest running a memtest86+ overnight and following up with a FULL disc scan (Long DST) with the drive manufacturer's tools.

I really think this must be where the problem lies.

~os

[Advertisements]

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.

[rshaffer61]

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.

[Klaus5000]

Okay the chkdsk is scheduled for next restart, then i will run the other things if nothing is found etc etc.

Thanks guys.

[Klaus5000]

Ran memtest overnight it seemed to get stuck at 31% twice.. Gonna leave a disk check on while im at school.

[rshaffer61]

What do you mean by get stuck at 31% twice.?
Did the test then continue on from there to eventually finish?
Did the test show a error at 31% then then start over?

[Klaus5000]

No, the test just stopped at 31% from where i left it for hours and it hadnt changed, so i did it again and it was also stuck, no errors reported, i did the disk check, im not sure how to check the results as i wasnt home when it completed.

[rshaffer61]

Try this and see if it will allow you to locate the log...

Go to >
Start > Administrative Tools > Event Viewer

click "Application" on the left

In column "Source" on the right half of the window, look for "Winlogon".
On the same row, "Event" matching 1001 is the que pasa on chkdsk.

Doubleclick that line matching both Winlogon and 1001.

[Klaus5000]

The only winlogin ones are event id of 6000

[Klaus5000]

latest minidumps see if anything enw as ive recently redone all main drivers and still happening.... Im getting ticked off ! Trying to work and game is impossible.

Last minidumps from 2 days.

Attached Files

•  Minidump.zip   286.06KB   122 downloads

[rshaffer61]

OK some points I need to go over.
On the memtest did you reboot the system with the iso disk in the drive and the test ran outside of windows?
Do you have more then one stick of memory in the system?

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


Download Autoruns from the link in my signature below:
1: Extract the Autoruns Zip file contents to a folder.
2: Double-click the "Autoruns.exe".
3: Click on the "Everything" tab
4: Remove any entries that mention "File Not Found" by right-clicking the entry and select Delete.
5: Go to File then to Export As or Save in some versions.
6: Save AutoRuns.txt file to known location like your Desktop.
7: Attach to your next reply.

[Klaus5000]

Yes i rebooted and ran the disc from startup.
and i have 4 modules,

Last 4 analysis

On Mon 30/11/2009 21:38:49 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000741A2, 0xFFFFF88009765010, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\113009-20609-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 30/11/2009 20:50:31 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005FAA828, 0xFFFFF88005FAA080, 0xFFFFF880012FC8B2)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\113009-23890-01.dmp



On Mon 30/11/2009 20:48:51 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000441A2, 0xFFFFF8800A158010, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\113009-20765-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 30/11/2009 17:24:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000346847D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\113009-21656-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 30/11/2009 17:12:38 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x18 (0xFFFFFA8003A27200, 0xFFFFFA80046A4EE0, 0x1, 0x1)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\113009-21968-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.




Autoruns.txt as atachment

thanks

Attached Files

•  AutoRuns.txt   168.57KB   273 downloads

Edited by Klaus5000, 01 December 2009 - 10:36 AM.

[rshaffer61]

Open Autoruns, click on "Logon" tab, and UN-check:

X "BtTray" ( there are two entries for this. Make sure you get the one that says File not Found)
+ "RealTray"


When done restart computer and then:



Download TFC by OldTimer to your desktop

• Please double-click TFC.exe to run it. (Note: If you are running on Vista, right-click on the file and choose Run As Administrator).
• It will close all programs when run, so make sure you have saved all your work before you begin.
• Click the Start button to begin the process. Depending on how often you clean temp files, execution time should be anywhere from a few seconds to a minute or two. Let it run uninterrupted to completion.
• Once it's finished it should reboot your machine. If it does not, please manually reboot the machine yourself to ensure a complete clean.

Download Auslogics Defrag from the link in my signature below. Auslogics Defrag in my opinion is better because:
It does a more comprehensive job at Defragging
It will actually show you what it is doing
At the end of working it will show you how much speed you picked up
You can view a online log of the files that Auslogics defragged

[Klaus5000]

I have done the TFC scan and now defragging with the other program, thank you, lets see how it goes.

[rshaffer61]

What about the first step with the autorun entries?

[Klaus5000]

Yeah did that, couldn't see the bitray one but deleted the other and restarted and looked again, and defrag is now done.