|
Hey everybody, I read the guide thread and tried to get as much information as I could. I had to be rather fast with the imgur upload because the computer was between crashes.
So here is my wifes computer specs and the program tests requested.
http://imgur.com/a/4FCwb#4
One ran rather long as I needed to tend to my sick child throwing up for a while.
Some background, it turns off. Sometimes it's a blue screen other times i'm not sure as I'm not always there.
I've tried re installing windows, system restore, registry fixes and my brother in law has tried hard re sets? Idk I'm very bad at this!
I tried to run the burn test but the PC crashes. The memory test comes back fine and the IN Place large FTTS test on Prime has a failed window 4.
A blue screen did also come up and I managed to jot down the I technical note? I think.
0x0000007e (0xffffffffc0000005, 0xfffff8000c16b2ad, 08xfffff880009a94a8, 0xfffff880009a8d00)
Update: Just crashed again and I got 0x00000050
Also! I got the error code when the system came back up.
Problem signature 01: 6.1.7600.16385 Problem signature 02: 6.1.7600.16385 Problem signature 03: Unknown Problem signature 04: 22 Problem signature 05: Auto fail over Problem signature 06: Bad driver OS Version: 6.1.7601.2.1.2.1.0.256.1 Local ID: 1033
Some more information about the crashes: Some of them are when NOTHING is running. It runs games fine and sometimes it crashes then too so I have no idea if it's random!
The power supply is a Thermal take TR2-600w so I think it should be enough but again, I am clue less about this and in your mercy.
I really hope you guys can help as I am at a loss . I'm not very computer savvy so I tried to gather all I could before I posted.
|
Problem signature 06: Bad driver = ? if you look in control panel -> device manager , do you see yellow question marks/unrecognized devices? run a Dxdiag maybe you get some info there: start -> run -> type dxdiag -> ok
from that picture, the motherboard temp looks pretty high and the CPU, for an Athlon, looks high too (AMD states that the danger temperature for 9950s is ~63C) (if you upgraded the CPU (from a 9500 to a 9550 or something), check if your bios supports it))
Edit: check if you have Cool’n’Quiet enabled in bios
|
On September 12 2014 16:45 xM(Z wrote: Problem signature 06: Bad driver = ? if you look in control panel -> device manager , do you see yellow question marks/unrecognized devices? run a Dxdiag maybe you get some info there: start -> run -> type dxdiag -> ok
from that picture, the motherboard temp looks pretty high and the CPU, for an Athlon, looks high too (AMD states that the danger temperature for 9950s is ~63C) (if you upgraded the CPU (from a 9500 to a 9550 or something), check if your bios supports it))
Edit: check if you have Cool’n’Quiet enabled in bios
No question marks or unrecognized devices.
http://imgur.com/6AQBki6 <-- dxdiag, all windows say no problem found.
I don't know how to operate bios or how to check if it supports it.
|
Hit the Delete key at the black screen when you turn the computer on and is showing all the devices/etc - tap it about every once a second and the bottom will say "Entering Setup"
Cool and Quiet is under the "Cell Menu" - use the arrow keys and enter, not the mouse.
http://us.msi.com/support/mb/DKA790GX.html#down-manual
Do you have kids? I wonder if someone played in the BIOS and changed the overclocking/memory timings/etc - That would cause the issues you are having as well, we may want to reset it to factory defaults next.
|
On September 13 2014 14:31 scott31337 wrote:Hit the Delete key at the black screen when you turn the computer on and is showing all the devices/etc - tap it about every once a second and the bottom will say "Entering Setup" Cool and Quiet is under the "Cell Menu" - use the arrow keys and enter, not the mouse. http://us.msi.com/support/mb/DKA790GX.html#down-manualDo you have kids? I wonder if someone played in the BIOS and changed the overclocking/memory timings/etc - That would cause the issues you are having as well, we may want to reset it to factory defaults next.
It was disabled, I did enable it, saved and exited. I do have 2 children and they love smashing the keyboard.
Edit: so far no crashes I will post something if it does. Sometimes it last a day sometimes it crashes after a few minutes.
|
If it now works, it might be like what xM(Z said and high temperatures were the problem. Did you ever clean the inside of the PC? If you never did, the CPU cooler (and everything else) might be stuffed with dust and cleaning might fix everything.
+ Show Spoiler +If you decide to clean, don't use a vaccum cleaner because it can shock things through static charges building up.
|
On September 14 2014 08:04 Ropid wrote:If it now works, it might be like what xM(Z said and high temperatures were the problem. Did you ever clean the inside of the PC? If you never did, the CPU cooler (and everything else) might be stuffed with dust and cleaning might fix everything. + Show Spoiler +If you decide to clean, don't use a vaccum cleaner because it can shock things through static charges building up.
I use those air cans to clean them usually. My wife has been at work so I won't know until this evening, tomorrow morning if it's probably going to crash. She however doesn't usually clean her PC. I did when I first noticed a problem, however I probably didn't do the best job.
|
So the computer seems to not be crashing, as far as I notice anyway. However on startup it does keep asking to repair or startup normally. but to my knowledge it was turned off. This issue was there during the crashes as well.
|
well it'll stop asking that if you actually run that repair else you'll get it forever
|
On September 15 2014 01:06 xM(Z wrote:well it'll stop asking that if you actually run that repair else you'll get it forever
I've done the repair a few times actually, it just keeps coming back. I thought a registry fix would stop it but everytime the computer starts up there are always 1-4 more errors.
|
Things on the drive might have gotten corrupted at the same time when all those crashes happened.
You should first run the error checking tool for the C: drive. It will want to restart the PC and check the drive outside of Windows if there's issues to fix.
After that's done, there's a tool to check all Windows files and restore them to the originals if they are corrupted. That might help. You open a command prompt window as Administrator and type this command:
sfc /scannow
That takes a while, but the PC can be used while it's working.
If it finds something and repairs some files but also says there were things it couldn't fix, you should run it again to see if it can fix some more files with each new run. If there's no change with a new run or if it finds a million files it wants to repair, this means the area where it stores copies of the original files is broken and I think there's no solution on Windows 7.
|
So the computer was doing fine up until today where these two blue screens came up, any ideas?
|
Can you go into the BIOS and take a picture of the "Cell menu" screen? I want to see if you are overclocking.
I've had memory tests pass and pass even if a stick is bad, maybe try only one stick? Usually STOP errors all over the place are memory or overclocking or something else failing.
|
Hello, There are a few questions and possible things for you to try.
1: When did these problems start occurring? 2. How old is this specific machine? 3. Do you know the make/model of the current machine you are running? (If not, right click on My Computer or Computer, and click on properties) It should tell you the model. 4. What version of Windows do you have? Windows 7 professional? Home? Windows XP? Vista? Info needed 5. Do you keep up to date with Windows Update? 6. You stated that you reinstalled Windows. When you did so, how long was it before the crashes started happening again? If you reinstalled Windows and these problems are still occurring, more than likely it has to do with a bad piece of hardware. 7 Now that you know how to go into the Bios, have you attempted to load the BIOS and set everything back to default? Try that and see what happens. 8. There are a few things you can try as well. What kind of virus scanning/adware scanning software do you have? 9. Click on Start and search for "Event Viewer". When you open Event Viewer, expand Windows Logs, and click on "System". There should be a errors posted here. Can you try and pinpoint the time that your computer crashed and related it to one of the errors? 10. Have you tried opening cmd.exe and typing sfc /scannow. See if that comes up with any errors 11. You stated that you often have to "Repair" when your computer starts up and that it actually repairs things. Can you try and remember some of the things it's repairing? Typically, if the computer constantly is loading into the repair section, it usually is an indicated that your Hard Drive is going bad (Especially if it is trying to repair things) (Aka the partitions) 12. On the Manufacturer's website for your computer, you can usually download hard drive checking tools. If not, you should google some and scan your hard drive for issues. 13. The other test you can run is a memory test. http://www.memtest86.com/. Google how to use this.
My initial thought is that the hard drive is going bad. Especially if these problems are occurring after you just did a clean install of Windows. However, the more information and things you start to notice, the better.
|
i'd start reading stuff: http://msdn.microsoft.com/en-us/library/ms854226.aspx
RQL_NOT_LESS_OR_EQUAL Explanation: This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
or random google stuff: http://www.techyv.com/questions/blue-screen-appeared-while-im-working http://www.tomshardware.co.uk/forum/6258-63-windows-bsod-boot http://www.tomshardware.co.uk/faq/id-1653275/fix-irql-equal-error-windows.html
Edit: but mostly you're screwed, since it's not that easy to diagnose . remember what you did, what she did before those errors appeared. Edit1: i'd start with drivers/recently installed programs
|
On September 17 2014 12:43 scott31337 wrote: Can you go into the BIOS and take a picture of the "Cell menu" screen? I want to see if you are overclocking.
I've had memory tests pass and pass even if a stick is bad, maybe try only one stick? Usually STOP errors all over the place are memory or overclocking or something else failing.
This is what I see
On September 17 2014 12:47 Managomous wrote:Hello, There are a few questions and possible things for you to try. 1: When did these problems start occurring? 2. How old is this specific machine? 3. Do you know the make/model of the current machine you are running? (If not, right click on My Computer or Computer, and click on properties) It should tell you the model. 4. What version of Windows do you have? Windows 7 professional? Home? Windows XP? Vista? Info needed 5. Do you keep up to date with Windows Update? 6. You stated that you reinstalled Windows. When you did so, how long was it before the crashes started happening again? If you reinstalled Windows and these problems are still occurring, more than likely it has to do with a bad piece of hardware. 7 Now that you know how to go into the Bios, have you attempted to load the BIOS and set everything back to default? Try that and see what happens. 8. There are a few things you can try as well. What kind of virus scanning/adware scanning software do you have? 9. Click on Start and search for "Event Viewer". When you open Event Viewer, expand Windows Logs, and click on "System". There should be a errors posted here. Can you try and pinpoint the time that your computer crashed and related it to one of the errors? 10. Have you tried opening cmd.exe and typing sfc /scannow. See if that comes up with any errors 11. You stated that you often have to "Repair" when your computer starts up and that it actually repairs things. Can you try and remember some of the things it's repairing? Typically, if the computer constantly is loading into the repair section, it usually is an indicated that your Hard Drive is going bad (Especially if it is trying to repair things) (Aka the partitions) 12. On the Manufacturer's website for your computer, you can usually download hard drive checking tools. If not, you should google some and scan your hard drive for issues. 13. The other test you can run is a memory test. http://www.memtest86.com/. Google how to use this. My initial thought is that the hard drive is going bad. Especially if these problems are occurring after you just did a clean install of Windows. However, the more information and things you start to notice, the better.
1. About a year ago, my brother in law said he was working on it but he spaced it off for so long. <.< I didn't want to be rude and ask for it back. 2. 3-4 years? Maybe 3. Is it one of these? 4. I think just windows 7 5. Yes I try to install the updates 6. 1-3 times yes, as early as the next day. 7. Would this require the installation CD? 8. I don't really have any, my brother in law does this stuff. I think one of the ones he uses is spybot. 9. This is what I see, the dates and times though don't seem to be consistent with yesterdays crashes. 10. It's telling me i'm not an administrator? Which is weird because it's the only one on there. 11. Yeah the repair mode is pretty vague but the registry fixer that I run after it starts up always seems to have something after a crash. This image again on 3 shows the registry cleaner. 12. Could you tell me which was the hard drive from 3? 13. Looking into it!
|
Bluescreens that show a different error code each time they happen, that's often caused by some sort of memory corruption going on. This does not have to mean the RAM is bad. It can also be a driver misbehaving. It can be program files on the drive having been corrupted from all that crashing in the past.
Everything you need is pretty much already built into Windows. You can check memory and you can check the drive with built-in tools.
For the memory test, you type "memory" into the Start menu's search box and you'll see it in the search results. It will want to restart the PC and test outside of Windows. If you look around on the screen when it runs, you'll see a key mentioned that you can press for more options. You can then increase the amount of time it spends on testing. The default test is pretty short and might overlook a problem with the RAM.
For the disk error checking, you open the Properties window of the C: drive and then go to the Tools tab and you'll see it. It might also want to restart the PC and do its testing outside of Windows if it finds things it wants to repair.
After that, you can then run that "sfc /scannow" thingy I mentioned a few posts back.
If the crashes still happen after all of this, you can then decide if you want to try reinstall Windows, or hunt for problems caused by drivers, or hunt for a problem with one of the hardware parts.
+ Show Spoiler +I'm pretty skeptical about Registry cleaner tools like what you show on your screenshot. It can break stuff by trying to repair something it does not understand. The next time you reinstall Windows on that machine, perhaps try to not use it for as long as possible.
|
On September 18 2014 00:33 Ropid wrote: Bluescreens that show a different error code each time they happen, that's often caused by some sort of memory corruption going on. This does not have to mean the RAM is bad. It can also be a driver misbehaving. It can be program files on the drive having been corrupted from all that crashing in the past.
For the memory test, you type "memory" into the Start menu's search box and you'll see it in the search results. It will want to restart the PC and test outside of Windows. If you look around on the screen when it runs, you'll see a key mentioned that you can press for more options. You can then increase the amount of time it spends on testing. The default test is pretty short and might overlook a problem with the RAM.
"Hardware problems were detected. To identify and repair these problems please contact the computer manufacturer." I got this doing the test.
|
If the PC has two memory sticks, you should now remove them and test each one individually.
If a memory stick went bad, it's unlikely that it happened to both at the same time. This means testing each stick individually would give you a hint about the RAM being bad or something else about the PC not working right. If one stick works but the other does not, you'll know that it was the RAM. If both work or both don't work if tested individually, something else is likely going on.
|
On September 18 2014 06:14 Ropid wrote: If the PC has two memory sticks, you should now remove them and test each one individually.
If a memory stick went bad, it's unlikely that it happened to both at the same time. This means testing each stick individually would give you a hint about the RAM being bad or something else about the PC not working right. If one stick works but the other does not, you'll know that it was the RAM. If both work or both don't work if tested individually, something else is likely going on.
So remove 1, do the memory test, try the other with the same test?
|
|
|
|