New
#1
Error 0x000000F4, when starting a game.
Hello
My PC does BSOD when i am playing WoW. I can log in and maybe play 2 min, and then it does BSOD with the error 0x000000F4, anyone know how to fix this problem?
Thanks for the help.
Hello
My PC does BSOD when i am playing WoW. I can log in and maybe play 2 min, and then it does BSOD with the error 0x000000F4, anyone know how to fix this problem?
Thanks for the help.
This error is usually a Storage (Hard Drive) one.Code:Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\USER\Downloads\Compressed\JEPPE-PC-30-12-2014__11410,63\123014-22417-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea1890 Debug session time: Tue Dec 30 05:02:20.785 2014 (UTC + 6:00) System Uptime: 0 days 1:06:11.675 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7A, {fffff6fc40006df0, ffffffffc000000e, 6993c860, fffff88000dbe630} GetPointerFromAddress: unable to read from fffff80002f0b278 *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption ---------
Run Disk Check on your Hard Drive for file system errors and bad sectors on it.
Hard Drive Diagnostics
- Double click and open my computer.
- Right click on desired drive and hit properties.
- Click on tools tab and Check now.
Read complete instructions on the tutorial: Disk Check
Other Tests:
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.
TipMemtest should be done overnight.