Hi I've just been trying to let my son play a little while and see results I will try today a for hours and definately reply and let you know results it hasn't had BSOD yet anyway
-
Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.
Why not Click Here To Sign Up and start enjoying great FREE Tech Support.
This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Solved any help would be great
- Thread starter allan hogg
- Start date
- Status
hi just to let you know it worked this morning all morning ran fine then we left on and i come back threw later and its on but no signal on screen now it turns on and keyboard lights when pressed but goes straight off after also seen that hardrive monitor light on box isnt flashing at all and when it was pc was starting up
dont know where to go from here sorry
dont know where to go from here sorry
ive tried removing RAM And swapping etc but to no avail i personally think and have thought hardrive is away as that light doesnt flash like my other pc
to show hardrive working and ive noticed when pc was working it was
to show hardrive working and ive noticed when pc was working it was
Did you ever test the RAM like was suggested?
Follow the instructions it may take a while if the HDD is larger give it time to complete.
pchelpforum.net
To post the results follow these instructions
Here is one way that you can pull the log to view it. You can also COPY and PASTE the contents from the CHKDSKResults.txt file into a post.
1. Press the Windows + R keys to open the Run dialog, type powershell.exe, and press Enter.
2. In PowerShell, copy and paste the command below, and press Enter.
Follow the instructions it may take a while if the HDD is larger give it time to complete.
Run CHKDSK using Command Prompt
1. Click the Start button. 2. Type cmd in the box 3. Right click on CMD to bring up the short cut menu. 4. Select Run as Administrator A User Account Control window will come up click Yes. To access the Administrator Command Prompt for...
To post the results follow these instructions
Here is one way that you can pull the log to view it. You can also COPY and PASTE the contents from the CHKDSKResults.txt file into a post.
1. Press the Windows + R keys to open the Run dialog, type powershell.exe, and press Enter.
2. In PowerShell, copy and paste the command below, and press Enter.
3. CHKDSKResults.txt file will be created on your desktop, that is the log file of your chkdsk scan results from Event Viewer.
hi thabks for replying going to run CHKDSK right now i managed to get this pc to start up again i could only test RAM yesterday By seeing if they made difference to pc startup in which they didnt it seems that if i take power plug from it then put back in it resets and starts again
It's running CHKDSK right now says fixing fixing files c: which I hope is what meant to say I have previously done this with 0 problems found think this will take a while
Curious if something else is going on here...
Please download the FRST 32 bit or FRST 64bit version to suit your operating system. It is important FRST is downloaded to your desktop.
If you are unsure if your operating system is 32 or 64 Bit please go HERE.
Once downloaded right click the FRST desktop icon and select "Run as administrator" from the menu"
If you receive any security warnings, or the User Account Control warning opens at any time whilst using FRST you can safely allow FRST to proceed.
FRST will open with two dialogue boxes, accept the disclaimer.
Frst will take a few minutes to scan your computer, and when finished will produce two log files on your desktop, FRST.txt, and Addition.txt. They will display immediately on the desktop, but can be reopened later as a notepad file.
Please Copy and Paste the contents of these logs in your next post for review by our Security Team
Please download the FRST 32 bit or FRST 64bit version to suit your operating system. It is important FRST is downloaded to your desktop.
If you are unsure if your operating system is 32 or 64 Bit please go HERE.
Once downloaded right click the FRST desktop icon and select "Run as administrator" from the menu"
If you receive any security warnings, or the User Account Control warning opens at any time whilst using FRST you can safely allow FRST to proceed.
FRST will open with two dialogue boxes, accept the disclaimer.
- Accept the default whitelist options,
- If the additions.txt options box is not checked please select it.
- Then select Scan
Frst will take a few minutes to scan your computer, and when finished will produce two log files on your desktop, FRST.txt, and Addition.txt. They will display immediately on the desktop, but can be reopened later as a notepad file.
Please Copy and Paste the contents of these logs in your next post for review by our Security Team
it says this when doing that thing threw powershell
et-winevent : The term 'et-winevent' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ et-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$ ...
+ ~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (et-winevent:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
et-winevent : The term 'et-winevent' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ et-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$ ...
+ ~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (et-winevent:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Lets try the link here and see if this work to get the information.
www.tenforums.com
Once you get to step 4 and can see the one that you ran on the side select copy
Then in the text box here left click and select paste.
If the same information does not paste in then open note pad and pasted into there.
Save the file and attach it using the Attach files button on the lower left of that text box.
Plus everything shows that the RAM is bad and needs be replaced or the ports that the RAM insert int the Motherboard are bad and the Motherboard needs replaced.
Read Chkdsk Log in Event Viewer in Windows 10
How to Read Event Viewer Log for Chkdsk (Check Disk) in Windows 10
www.tenforums.com
Then in the text box here left click and select paste.
If the same information does not paste in then open note pad and pasted into there.
Save the file and attach it using the Attach files button on the lower left of that text box.
Please explain this in more detail.
What is the make and model. The one that you replaced it with many not be powerful enough to run everything.
Plus everything shows that the RAM is bad and needs be replaced or the ports that the RAM insert int the Motherboard are bad and the Motherboard needs replaced.
sorry if im vague really dont mean to be yesterday when away from pc it went off and i couldnt get it to turn back on so i removed all wires and reput all wires back in place and taped up all the excess plugs and wires just incase of arking also took ram out one by one and tried to get to boot and also switched them places but still to no avail but eventually with everything back in and the power cable removed and put back in a few times it booted and h/drive light started flashing again as normal
the new pcu i replaced it with is a new one from scan only a month old its a EVGA700 gold as he had a generic 500w psu in standard i must say the BSOD screens Happened both before and after new psu replacement
as of today there hasnt been one BSOD which is strange as it was regular yesterday before i reset windows
the new pcu i replaced it with is a new one from scan only a month old its a EVGA700 gold as he had a generic 500w psu in standard i must say the BSOD screens Happened both before and after new psu replacement
as of today there hasnt been one BSOD which is strange as it was regular yesterday before i reset windows
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
648704 file records processed.
File verification completed.
Phase duration (File record verification): 8.78 seconds.
6142 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.92 milliseconds.
Stage 2: Examining file name linkage ...
8199 reparse records processed.
707288 index entries processed.
Index verification completed.
Phase duration (Index verification): 2.75 minutes.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 615.19 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 33.79 seconds.
8199 reparse records processed.
Phase duration (Reparse point and Object ID verification): 30.88 milliseconds.
Stage 3: Examining security descriptors ...
Cleaning up 3259 unused index entries from index $SII of file 0x9.
Cleaning up 3259 unused index entries from index $SDH of file 0x9.
Cleaning up 3259 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 147.50 milliseconds.
29293 data files processed.
Phase duration (Data attribute verification): 1.02 milliseconds.
CHKDSK is verifying Usn Journal...
34507880 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 975.61 milliseconds.
Stage 4: Looking for bad clusters in user file data ...
648688 files processed.
File data verification completed.
Phase duration (User file recovery): 7.48 minutes.
Stage 5: Looking for bad, free clusters ...
237945304 free clusters processed.
Free space verification is complete.
Phase duration (Free space recovery): 0.00 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
975670136 KB total disk space.
23024456 KB in 108893 files.
78228 KB in 29294 indexes.
0 KB in bad sectors.
786232 KB in use by the system.
65536 KB occupied by the log file.
951781220 KB available on disk.
4096 bytes in each allocation unit.
243917534 total allocation units on disk.
237945305 allocation units available on disk.
Total duration: 11.00 minutes (660545 ms).
Internal Info:
00 e6 09 00 d4 1b 02 00 46 2f 04 00 00 00 00 00 ........F/......
42 00 00 00 c5 1f 00 00 00 00 00 00 00 00 00 00 B...............
Windows has finished checking your disk.
Please wait while your computer restarts.
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
648704 file records processed.
File verification completed.
Phase duration (File record verification): 8.78 seconds.
6142 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.92 milliseconds.
Stage 2: Examining file name linkage ...
8199 reparse records processed.
707288 index entries processed.
Index verification completed.
Phase duration (Index verification): 2.75 minutes.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 615.19 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 33.79 seconds.
8199 reparse records processed.
Phase duration (Reparse point and Object ID verification): 30.88 milliseconds.
Stage 3: Examining security descriptors ...
Cleaning up 3259 unused index entries from index $SII of file 0x9.
Cleaning up 3259 unused index entries from index $SDH of file 0x9.
Cleaning up 3259 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 147.50 milliseconds.
29293 data files processed.
Phase duration (Data attribute verification): 1.02 milliseconds.
CHKDSK is verifying Usn Journal...
34507880 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 975.61 milliseconds.
Stage 4: Looking for bad clusters in user file data ...
648688 files processed.
File data verification completed.
Phase duration (User file recovery): 7.48 minutes.
Stage 5: Looking for bad, free clusters ...
237945304 free clusters processed.
Free space verification is complete.
Phase duration (Free space recovery): 0.00 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
975670136 KB total disk space.
23024456 KB in 108893 files.
78228 KB in 29294 indexes.
0 KB in bad sectors.
786232 KB in use by the system.
65536 KB occupied by the log file.
951781220 KB available on disk.
4096 bytes in each allocation unit.
243917534 total allocation units on disk.
237945305 allocation units available on disk.
Total duration: 11.00 minutes (660545 ms).
Internal Info:
00 e6 09 00 d4 1b 02 00 46 2f 04 00 00 00 00 00 ........F/......
42 00 00 00 c5 1f 00 00 00 00 00 00 00 00 00 00 B...............
Windows has finished checking your disk.
Please wait while your computer restarts.
The BSODs may not show for a few days or with in the next few minutes.
The CHKDSK shows the hard drive is ok.
The PSU is a good one so no issue there.
Everything that come back keeps showing the RAM and or the ports are the issue.
The CHKDSK shows the hard drive is ok.
The PSU is a good one so no issue there.
Everything that come back keeps showing the RAM and or the ports are the issue.
From the FRST reports
Percentage of memory in use: 41%
Total physical RAM: 8138.79 MB
Available physical RAM: 4750.97 MB
From the Speccy report
Physical Memory
Memory Usage: 33 %
Total Physical: 7.95 GB
Available Physical:5.28 GB
As you can see the RAM is reporting incorrectly and in you first post you show that Memtest86 is reporting issues with the RAM.
Which can cause file to be stored incorrectly and failure to run correctly.
Percentage of memory in use: 41%
Total physical RAM: 8138.79 MB
Available physical RAM: 4750.97 MB
From the Speccy report
Physical Memory
Memory Usage: 33 %
Total Physical: 7.95 GB
Available Physical:5.28 GB
As you can see the RAM is reporting incorrectly and in you first post you show that Memtest86 is reporting issues with the RAM.
Which can cause file to be stored incorrectly and failure to run correctly.
perfect i cant thank you enough i have ordered new ram and also a sata hdrive so al let u know when i put in if u want if not you can put as solved
THANK YOU VERY MUCH
i know ive been hard to work with
THANK YOU VERY MUCH
i know ive been hard to work with
Monday or Tuesday only bought 4gb just now is there away I can use something like speccy again to make sure I get right memory reading I'm also going to buy another 4gb on Friday
Speccy is public software so by all means run it and if you have question or issues feel free to ask.
hi ive put one new stick of ram in and one old and this was speccy results
Memory Usage:
39 %
Total Physical:
7.95 GB
Available Physical:
4.83 GB
Total Virtual:
9.82 GB
Available Virtual:
5.82 GB
Memory Usage:
39 %
Total Physical:
7.95 GB
Available Physical:
4.83 GB
Total Virtual:
9.82 GB
Available Virtual:
5.82 GB
then i have changed old ones around and kept new one and i get there results
Memory Usage:
27 %
Total Physical:
7.95 GB
Available Physical:
5.74 GB
Total Virtual:
9.82 GB
Available Virtual:
6.82 GB
Memory Usage:
27 %
Total Physical:
7.95 GB
Available Physical:
5.74 GB
Total Virtual:
9.82 GB
Available Virtual:
6.82 GB
- Status