Im messing about with Windbg atm, and ran across this error message.
Followup: MachineOwner
---------
0: kd> .reload
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
Are the sys32 and win32 normal for my 64 bit system?
That is not a problem. The important portion of that blurb is ntoskrnl.exe. That is a driver that I have seen in your reports before. That is a lead driver and not the cause of your problem. All part of the CLUES that the reports give. Many clues but seldom an answer. That clue indicates a driver problem, but not ntoskrnl.
Just received a load of info from windbg, which I can't make sense of. Maybe someone with more knowledge can interpret.
See attached .txt
Cheers.
Ok this file was saved using the program itself. I could't find any other way to save the report itself, so I hope this file is sufficient.
Thanks.
Came up the same it says Inconclusive. This is usually hardware.
Here is a list of the hardware tests. that may be helpful.
Diagnostics
Ok well I am planning to visit a friend soon and take my PC over to him, and I will be able to put some of his components in my PC and hopefully will be able to narrow down the options of what could be causing my problems. Prime95 has been going over 6 hours now, and has returned no errors.
Thanks for your time and help.
Just installed some updates on the pc, and whilst doing this it bsod'd. There were 4 updates all regarding .net framework 4. When the computer booted up again, I was met with an error message which I have never seen before saying "
An error has occured with your network adapter.
The application will now exit.
Please contact customer services with Code:
Err:101 (Input string was not in a correct format). "
I re-installed the updates which failed, which took longer than usual, but eventually installed. But I was met with the same error message with the network adapter upon the next restart.
Is the 101 error on that anything to do with the BSOD do you think? I am using a homeplug ethernet adapter.
Thanks.
If you get information about a potential driver, make sure that you have the most up to date. Network drivers are the source of manyproblems.
This is what 101 means.
STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes: Device driver, BIOS bug, hardware defect
Quote