New
#41
Remember to run MemTest86+
Memtest86+ is a very accurate RAM test, if the RAM fails with the test it can, and will, fail when other programs are run too. Running it for a full 8 passes, or more, will flesh out and bad RAM. If you get just one error, that's bad.
Done memtest86, nothing, what else can it be?
Random freeze/crashes, have to hard reset, error 0x1A shown up on 3 installs, 2with my disc 1 with the guys I bought it online from, so I doubt its my disc, then the whole league of legends, which happened without me installing a single program 0x1A.
Anything to do with bios voltages or that? I'm clueless.
Please do the following:
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable
Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.
I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create
If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode
was just coming online to check and follow steps, went to pass 9 with no errors but got this before I could start verifier etc;
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002e879e3, 0xfffff88009470f60, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 020714-31964-01.
attached dmp, will try above steps.
& desktop just turned off monitor/keyboard, but still power to the mouse edit- no power to mouse lol, I'll try follow steps if it stays on long enough! lol.
Have created restore point and enabled driver verifier, should I disable verifier even if I have to hard reset?; e.g no power to mouse monitor and keyboard?.
Last edited by sezan1; 08 Feb 2014 at 01:40.
Happened during verifier running;
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000406f8, 0xfffff80002e8b14f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .
Unable to produce a minidump file from the full dump file.
Will try again.
~
This time just got a screen crash, no bsod or anything, everything had lines through it
& no power to keyboard mouse or monitor x3.
gonna sleep will attempt again later.
Edit
Managed to get a blue screen upon startup with driver verifier although no dump again.. and event viewer isn't showing it, think this one was due to verifier running & windows was trying to configure one update.
Last edited by sezan1; 08 Feb 2014 at 06:18.