New
#11
Did the BSOD-s reoccur? :)
Computer BSOD's When it Realizes It's Alone
-
-
New #12
it did just the other day actually, but i don't think its the same problem. even then, i have bigger problems. currently, windows has killed the drivers for any network card. and won't let me reinstall them. i made a thread in the drivers section, nobody seems to have replied. at this point, i think i'm just going to reinstall windows when i get the chance. hopefully that will solve the majority of my problems. Thanks for checking back! and thanks for solving my BSOD problem!
-
New #13
I see.
Post back if you have issues related to BSOD-s or something else. I'm no expert at anything but will try to help. :)
-
New #14
(Return of)PC BSOD's When it Realizes it's Alone
Hello, i have a similar problem to the one that was fixed in my first thread, where Avast! Antivirus was the culprit. This time, I have only recently reinstalled windows due to some glitches and bugs that i just got tired of. Now, my PC is doing a similar thing, only now it seems to happen more frequently, around 5-6 times a day, and it only seems to happen while the computer is either idol or i am away from it. I can play games and browse the web for hours, but the moment i walk away for more than half an hour, the PC bluescreens and reboots. I don't use Avast! anymore, as it was determined to be the cause of the problem before. Now, whenever the computer BSOD's, the stop message is usually something along the lines of SYSTEM_SERVICE_EXCEPTION. I have tried my best using windbg to figure out the problem, but like last time, it just says NTKRNLMP.exe or something that's part of the root windows files. It also says something about an undefined symbol. I am using the symbols from MS's website as the path, so i figure it should be up to date, right? Anyway, i figure i'm not exactly doing everything right, so i'll leave it to the professionals here. Thanks in advance to anybody who helps out!
-
New #15
Hi.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
The goal is to test all the RAM sticks and all the motherboard slots.
Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.
If you get errors, stop the test and continue with the next step.
1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.If this stick passes the test then go to step #3.
2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.4. If you find a stick that passes the test, test it in all the other motherboard slots.
If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.
In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.InformationErrors are sometimes found after 8 passes.
TipDo this test overnight, before going to bed.
-
New #16
will do, i'll come back when it's finished with the results. If the memory is bad, this wouldn't be the first time memory has gone bad in this motherboard, and it would also not be the first time this motherboard has been fried and RMA'd. I have encountered nothing but problems with it...
-
New #17
Fried, RMA'd and you got the same MB back?
Your case seems similar to this one: https://www.sevenforums.com/crashes-d...x0000003b.html
I'm hoping not though..
-
New #18
I ran memtest, but didn't set it to eight passes, i'll do that tomorrow morning. The first two passes came back all clear though, and i'll let it run all night.
I see you moved my thread, i considered posting here, but was hesitant to revive an old thread. Plus, this thread was already solved
The board started out freezing just like in that other post you linked, but it would also crash and artifact to a bunch of jumbled up colors within twenty minutes of starting it, and after that it had to be unplugged before it would boot again. it got to the point where it didn't even work anymore, so i RMA'd it, and i'm pretty sure it's not the same board, either way, now, less frequently than the bluescreens, it just freezes, no reboot, nothing, it will do this at any time, during startup, at the login, in linux, windows, even before booting. Next time, i will be hesitant to buy Asus, but that's only because of my bad experiences with this model.
-
New #19
There are a few stress tests that can be performed..
Hardware - Stress Test With Prime95
CPU - Stress Test Using IntelBurnTest
Video Card - Stress Test with Furmark
Monitor your temps with Speccy during these tests
Video Memory Test:
-
New #20
oooh, this looks bad. It's currently on the seventh pass, and says somewhere around a hundred thousand errors. This almost proves my theory, being that this is the second set of ram that has fried in this model motherboard, do you think i have any hope with Asus sending me a different model if i send this one in?
Quote
Related Discussions