Got mouse and K/B to work, maybe I can do that DMP file.
I got up too reading the DMP files in my windows minidump directory.
Which file would you like me to open (There are 5), and how would you like me to post the information on here?
http://imgur.com/tPWeN1Q
I walked away from the PC for abit, and it appears to have crashed, didn't get time to have a look at the DMP file. I'm not sure if a fresh OS install would do the trick.
A friend thinks it may be the PSU as well, and it is making a weird buzzing sound, I'm not sure if that is normal. I have a Corsair HX850.
Just do the most recent one.
If there is a buzzing sound, check to make sure it's not one of the case fans or the CPU fan first. If not, it could just be coil whine from the PSU. I'm not too sure what the signs of a bad PSU are though.
Another thing to try is booting into safe mode to see if Windows is stable. If it is, it may be a driver issue. If not, then probably a hardware issue.
I think the fans are all fine, and yes first I did think it was a coil whine, or it could just be me overreacting about the PSU not sure.
Windows is also not stable in safe mode, the blue screen will also come up.
Sorry about the delays, life can be quite hectic at times, but this is important and I need to get this done. I really do appreciate all the help. Thank you all!
Here is the DMP file as requested.
_____________________________________________________________________________________
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\052114-8314-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Users\admin
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
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`03017000 PsLoadedModuleList = 0xfffff800`0325a890
Debug session time: Wed May 21 17:12:51.266 2014 (UTC + 10:00)
System Uptime: 0 days 1:32:02.561
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 406f8, fffff96000109160}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : win32k.sys ( win32k+c9160 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff96000109160
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: win32k
FAULTING_MODULE: fffff80003017000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52f4357b
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000308c169 to fffff8000308cbc0
STACK_TEXT:
fffff880`009f1de8 fffff800`0308c169 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt+0x75bc0
fffff880`009f1df0 00000000`0000007f : 00000000`00000008 00000000`80050031 00000000`000406f8 fffff960`00109160 : nt+0x75169
fffff880`009f1df8 00000000`00000008 : 00000000`80050031 00000000`000406f8 fffff960`00109160 00000000`00000000 : 0x7f
fffff880`009f1e00 00000000`80050031 : 00000000`000406f8 fffff960`00109160 00000000`00000000 ffffffff`ffffffff : 0x8
fffff880`009f1e08 00000000`000406f8 : fffff960`00109160 00000000`00000000 ffffffff`ffffffff ffffffff`ffffffff : 0x80050031
fffff880`009f1e10 fffff960`00109160 : 00000000`00000000 ffffffff`ffffffff ffffffff`ffffffff 40438000`00000000 : 0x406f8
fffff880`009f1e18 00000000`00000000 : ffffffff`ffffffff ffffffff`ffffffff 40438000`00000000 00000000`00000000 : win32k+0xc9160
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k+c9160
fffff960`00109160 d7 xlat byte ptr [rbx]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: win32k+c9160
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
I'm going to do a fresh install of windows when I have the time.
This is really starting to stress me out.
This happened to my mate a while ago. It turned out to be the heat sink not being attached properly. Try that if you haven't already.
Use Blue screen view to see if it comes up with a error code.
It doesn't seem to be the thermals, and I have re-applied the thermal paste and re-connected the heat sink three times. So it most likely isn't that, but thank you for the information.
I will also try out BlueScreen View, thanks.
- Tried running a live linux distro off a usb? Check stability of entire system.
- If OS is on an OCZ ssd then odd bsods are very common.
- Run hirens boot disc and do some diagnostic testing - ram ,hdds etc.
- Worst case - boot via linux - copy over files you need, then reinstall windows.
This is perfect.
After a bit of googling, the "unexpected kermel module trap" error is caused by improper CPU overclocking, defective RAM, or a damaged motherboard, as explained by this post:
http://answers.oreilly.com/topic/1496-how-to-decipher-a-blue-screen-of-death/
In some other forums people have commented that it may also be caused by the Intel Rapid Start or any ASUS programs, these things you might have installed when getting the motherboard drivers from the ASUS website. Might be a good idea to uninstall these then check for stability. That way we can rule out software.
If you have a USB stick or a blank DVD, put any distro of Linux you want (a very quick and easy one is Slax), boot up and there should be an option to run Memtest86. Run the test to check if the RAM is faulty at all. There are plenty of guides and information about Memtest in case you have questions about results.
You can also use that same boot drive to load into Slax. If there is a hardware issue, it'll likely crash Slax. If not, then Windows may have been corrupted on the hard drive. It would be at this point that I would recommend using a Windows install disk to try to repair it or reinstall the OS entirely.
Damaged motherboard, I think this may be the issue, even though this one is new (imagine the chances of getting two new motherboards that both happen to be faulty, FML).
ASUS programs, yes I have them installed, so it could also be them possibly in combination with the motherboard.
I also ran Memtest86, left it on for ages, and no errors in RAM, so we should be able to rule that out. Also my motherboard has the "MemOK" red LED light on, this means the RAM is faulty, and as I said, after numerous tests they showed different results. So I tried changing the RAM slots on the motherboard to other ones and when I boot up Windows it still crashes. So this could mean the motherboard is faulty as it is showing incorrect information.
I totally agree with you on the new OS install, this will allow me to test individual programs and remove those ASUS programs and possibly any faulty drivers in one go, thank you for all this helpful information.
I don't have any OCZ SSDs in my system.
I ran Hiren's BootCD and did lots of tests, no errors showed up.
Yes I will backup my files and then re-install Windows, thanks for the help.
I was getting the 1E Bccode quit often today thanks to failed RAM overclocks. If the ram clearer thingy didn't do anything after pushing it with power off (reset ram timings) then you should pop out the cmos battery and start fresh with the bios. Might even be worth flashing bios to newer version.
Have you gotten any 0x0000050 or 124 codes?
I seem to be getting a couple of different BSoD errors every so often, here is a link to two of them that I received.
http://imgur.com/ZLrKzB1,TJQQJBL#0
I also received SYSTEM_SERVICE_EXCEPTION, sorry I don't have a picture of that.
After looking through your posts again, you have a number of different bsods. You overclock anything?
Nah I haven't overclocked anything.
Blue Screen View seems very detailed, here is a Print Screen.
http://imgur.com/s6z9fXi
Here are the different BSoD errors, look at the "Bug Check String" section, that will show them.
http://i.imgur.com/s6z9fXi.png
I want to say it is bad memory but not entirely certain at this point. Bad ram (or an almost stable ram oc in my experience) will corrupt windows files. Have you ran sfc /scannow or scanned HDD's to check for anything yet?