 | |
| |
| 08 Oct 2011 | #11 |
| | Hi, I'm wondering if someone else can help me now then since I am STILL having this problem, it has not magically gone away. I have cut it down to 4GB ram, taking out my old sticks and leaving in my new 1600 ram, STILL bluescreening. The new ram settings are as they should be, manual and running 9-9-9-24, 1600 at 1.65v, and still crashing! I ran Memtest on the new 4gb and not a single error, ran it for 9 passes and each passed. I have also reseated everything. I'm not sure what else to do now! it STILL crashes on 4gb!!! nevermind crashing on the 8GB. I'm come to the conclusion that it is NOT the ram. When I run stress tests like Prime 95 using 'blend' it comes up with an error saying one of the cores failed, could this be my processor crapping out? shortly after it bluescreens. I have uploaded a picture of the core that fails for you to see. It is 'Worker' (core) #4. Please, guys, I need help here. I'm at the point of RMA'ing the LOT and starting over at this rate!!! I'm out of options!!! Last edited by RussUK; 08 Oct 2011 at 06:56 AM.. |
My System Specs | |
| 08 Oct 2011 | #12 |
| | Russ With prime showing that error I would think hardware but your comment about running 6 hours in safe mode without problem makes me think software. It might be easier to -reinstall win 7 clean than to RMA the computer. At least then if it re-occured you can eliminate software. Just a thought can you run a system file check to verify the OS files Run a system file check to verify and repair your system files. To do this type cmd in search, then right click to run as administrator, then SFC /SCANNOW Read here for more information SFC /SCANNOW Command - System File Checker Let us know the results from the report at the end. |
| My System Specs |
| 08 Oct 2011 | #13 |
| | 
Quote: Originally Posted by zigzag3143  Russ With prime showing that error I would think hardware but your comment about running 6 hours in safe mode without problem makes me think software. It might be easier to -reinstall win 7 clean than to RMA the computer. At least then if it re-occured you can eliminate software. Just a thought can you run a system file check to verify the OS files Run a system file check to verify and repair your system files. To do this type cmd in search, then right click to run as administrator, then SFC /SCANNOW Read here for more information SFC /SCANNOW Command - System File Checker Let us know the results from the report at the end. I have ran SFC /SCANNOW. This is the result: Windows Resource Protection did not find any integrity violations. image attached. Had a few more since my last post, MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXEPTION. Nothing different really, except I can't give you the dumps as windows/minidump is empty. |
| My System Specs |
| . |
| |
| 08 Oct 2011 | #14 |
| | Russ Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result There is a test called driver verifier that would catch an offending driver. You might give that a try. Quote: I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . Then, here's the procedure: - Go to Start and type in "verifier" (without the quotes) and press Enter - Select "Create custom settings (for code developers)" and click "Next" - Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next" - Select "Select driver names from a list" and click "Next" Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page. Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). If you can't get into Windows because it crashes too soon, try it in Safe Mode. If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. |
| My System Specs |
| 09 Oct 2011 | #15 |
| |
Quote: Originally Posted by zigzag3143 Russ Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result There is a test called driver verifier that would catch an offending driver. You might give that a try. Quote: I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . Then, here's the procedure: - Go to Start and type in "verifier" (without the quotes) and press Enter - Select "Create custom settings (for code developers)" and click "Next" - Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next" - Select "Select driver names from a list" and click "Next" Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page. Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). If you can't get into Windows because it crashes too soon, try it in Safe Mode. If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. I have re-ran verifier. I had about 7-8 blue screens in a row, as expected I suppose. Some of these were: RTKVHD.sys (?) multiple of them, my comp restarts quickly so i only catch a few seconds. I believe this is Realtek drivers. One BSOD may have been '64' as well, I've had these before. APC (Possibly API? Sorry they're quick)_INDEX_MISMATCH (?) Never had this before. MEMORY_MANAGEMENT, a usual occurence. SYSTEM_SERVICE_EXEPTION, usual again. IRQL_NOT_LESS_OR_EQUAL, usual. It crashed as soon as it hit the 'welcome' screen before it loads the desktop once, then got into windows for a few seconds on the second attempt before crashing, it did this a few times before crashing at the welcome screen again before finally being 'stable' for a minute or so that I could get to verifier and reset the settings and restart my pc. I hope this helps. Russ. |
| My System Specs |
| 09 Oct 2011 | #16 |
| |
Quote: Originally Posted by RussUK
Quote: Originally Posted by zigzag3143 Russ Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result There is a test called driver verifier that would catch an offending driver. You might give that a try. Quote: I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature). In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu . Then, here's the procedure: - Go to Start and type in "verifier" (without the quotes) and press Enter - Select "Create custom settings (for code developers)" and click "Next" - Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next" - Select "Select driver names from a list" and click "Next" Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page. Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). If you can't get into Windows because it crashes too soon, try it in Safe Mode. If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. I have re-ran verifier. I had about 7-8 blue screens in a row, as expected I suppose. Some of these were: RTKVHD.sys (?) multiple of them, my comp restarts quickly so i only catch a few seconds. I believe this is Realtek drivers. One BSOD may have been '64' as well, I've had these before. APC (Possibly API? Sorry they're quick)_INDEX_MISMATCH (?) Never had this before. MEMORY_MANAGEMENT, a usual occurence. SYSTEM_SERVICE_EXEPTION, usual again. IRQL_NOT_LESS_OR_EQUAL, usual. It crashed as soon as it hit the 'welcome' screen before it loads the desktop once, then got into windows for a few seconds on the second attempt before crashing, it did this a few times before crashing at the welcome screen again before finally being 'stable' for a minute or so that I could get to verifier and reset the settings and restart my pc. I hope this helps. Russ. |
| My System Specs |
| 09 Oct 2011 | #17 |
| |
Quote: Originally Posted by zigzag3143
Quote: Originally Posted by RussUK
Quote: Originally Posted by zigzag3143 Russ Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result There is a test called driver verifier that would catch an offending driver. You might give that a try. I have re-ran verifier. I had about 7-8 blue screens in a row, as expected I suppose. Some of these were: RTKVHD.sys (?) multiple of them, my comp restarts quickly so i only catch a few seconds. I believe this is Realtek drivers. One BSOD may have been '64' as well, I've had these before. APC (Possibly API? Sorry they're quick)_INDEX_MISMATCH (?) Never had this before. MEMORY_MANAGEMENT, a usual occurence. SYSTEM_SERVICE_EXEPTION, usual again. IRQL_NOT_LESS_OR_EQUAL, usual. It crashed as soon as it hit the 'welcome' screen before it loads the desktop once, then got into windows for a few seconds on the second attempt before crashing, it did this a few times before crashing at the welcome screen again before finally being 'stable' for a minute or so that I could get to verifier and reset the settings and restart my pc. I hope this helps. Russ. A perfmon report is also in the rar, incase it helps. I've also just checked Event Viewer and I'm having tons and tons of 'Critical' messages, is this normal? An image is attached. |
| My System Specs |
| 13 Oct 2011 | #18 |
| | Hi again, I've had 4+ more bluescreens since my last reply. I don't know what else to try other than another full re-install of windows from scratch, which I would like to avoid. Do you have anything else I could try? |
| My System Specs |
| 14 Oct 2011 | #19 |
| |
Quote: Originally Posted by RussUK Hi again, I've had 4+ more bluescreens since my last reply. I don't know what else to try other than another full re-install of windows from scratch, which I would like to avoid. Do you have anything else I could try? |
| My System Specs |
| 15 Oct 2011 | #20 |
| |
Quote: Originally Posted by zigzag3143
Quote: Originally Posted by RussUK Hi again, I've had 4+ more bluescreens since my last reply. I don't know what else to try other than another full re-install of windows from scratch, which I would like to avoid. Do you have anything else I could try? Great, how would I find out which is the faulty hardware? I'm guessing my processor, as it is a new mobo, new ram and i very much doubt it to be my 5850. Prime 95 shows the error on a core when I run the blend test, so does OCCT, images attached. It fails too. I'm guessing processor. Arghh, just so happens to be the most expensive change :P Oh well, I'll just go for the 1090T or 1100T black edition processors instead since they're better. I imagine I'll ring AMD and tell them my problem with my processor, and they'll RMA it? |
| My System Specs |
 |
Random BSODs that are baffling - Occur at any time problems?
| Thread Tools | |
| Similar help and support threads for: Random BSODs that are baffling - Occur at any time | ||||
| Thread | Forum | |||
| Random BSODS - different files every time | BSOD Help and Support | |||
| Several BSODs - 9f (seems to occur around standby mode), e6 | BSOD Help and Support | |||
 Random BSODs during different tasks each time | BSOD Help and Support | |||
| Recurring but different BSODs with different codes that occur randomly | BSOD Help and Support | |||
| Random BSODs (Thank you in advance for your time) | BSOD Help and Support | |||
All times are GMT -5. The time now is 08:14 AM.
