0 Members and 1 Guest are viewing this topic.
Okay, so your blue screening still? What is the stop error code?Also, I have seen some mother board and processor combinations that were very picky about memory timings. Especially so with brand name computers like HP and dell for examples. If you can enter the BIOS settings and check to see if there is a turbo setting. If so, try disabling it to see if it helps.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041201, 0xfffff6800017ff98, 0xc45000017f05d867, 0xfffffa8006be0c10).
Most people say that you have to make, (at the very least) 5 passes. 10 passes for a normal run. 20 passes for a extended test. You can run 1 chip at a time but that could take a couple of days to complete 4 extended tests. I assume that your main board has dual channel memory configuration? I would recommend running the mem test with 2 sticks completing 1 channel. Then through the process of elimination, run the test 1 at a time on the pair that failed.
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 4105Additional information about the problem: BCCode: a BCP1: FFFFFAAFD4919128 BCP2: 0000000000000002 BCP3: 0000000000000000 BCP4: FFFFF80003119195 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1Files that help describe the problem: C:\Windows\Minidump\022116-54397-01.dmp C:\Users\Angie\AppData\Local\Temp\WER-83257-0.sysdata.xmlRead our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
Just use MSI Afterburner. It is not a resource hog like Mooo is.
Moo0 is a resource hog?
Quote from: [IA] KT KaBo0M on February 23, 2016, 11:16:37 pmMoo0 is a resource hog?Umm, don't you read your own links?
I was referring to the links you posted for afterburner and Moo0.
Out of curiosity, what resources does Moo0 tend to hog? I've used it on a variety of different comnputers and the only thing it felt laggie on was a netbook (but what isn't on a netbook).
(Symptom) It uses lots of CPU on Windows 7 running on Virtual PC.It's because Virtual PC doesn't support hosting Windows 7 yet. Even if you turn off SystemMonitor, Windows Task Manger will then use lots of CPU instead. You simply need to wait for Virtual PC to support Winwdows 7. (VMware has no problem of such.)
While we wait for Jeff to answer u Dave, I got a question for both of u. I noticed just now when I plugged my cell phone into the front of my case (usb 2) my keyboard lost power. The keyboard is plugged into the back in the usb 2.0 on the motherboard. I tried it again and same thing. Right now I am typing this with Windows On-Screen Keyboard since I only have one computer (Netbook is at my mom's). If I unplug the keyboard and plug it back in it detects it again but automatically disconnects again . It seems I have to unplug my cell phone and unplug my keyboard and plug it back in for it to work again.
Quote from: [IA] KT KaBo0M on February 24, 2016, 05:50:59 pmWhile we wait for Jeff to answer u Dave, I got a question for both of u. I noticed just now when I plugged my cell phone into the front of my case (usb 2) my keyboard lost power. The keyboard is plugged into the back in the usb 2.0 on the motherboard. I tried it again and same thing. Right now I am typing this with Windows On-Screen Keyboard since I only have one computer (Netbook is at my mom's). If I unplug the keyboard and plug it back in it detects it again but automatically disconnects again . It seems I have to unplug my cell phone and unplug my keyboard and plug it back in for it to work again.Sorry about the double post. I have some questions before I attempt to answer this. But it sounds like a short circuit. #1 Are you using a USB pci expansion card?#2 Are you using a USB 1.1, 2.0 or 3.0 hub?#3 Does the front IO panel connect directly to the main board with a single group connector or individual connectors? Are you sure it's connected correctly?
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 4105Additional information about the problem: BCCode: 7a BCP1: FFFFF6FC40008690 BCP2: FFFFFFFFC0000185 BCP3: 0000000108289860 BCP4: FFFFF880010D293C OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1