BSOD 0x00000101 (normally under load)

[richkempo]

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?

 

[richc46]

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.

 

[richkempo]

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.

 

[richc46]

Send the actual reports as in the past.

 

[richkempo]

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.

 

[richc46]

Came up the same it says Inconclusive. This is usually hardware.
Here is a list of the hardware tests. that may be helpful.
Diagnostics

 

[richkempo]

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.

 

[richc46]

Glad to help. I just hope that with 3 of us we get it fixed.

 

[richkempo]

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.

 

[richc46]

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

 

[richkempo]

I have just ran a test using OCCT and it produced some strange reading on some of the voltages. When using the GPU:3D test, and with using error checking after a 4 minutes, it detected over 10,000 errors, and as time went on more and more were being detected. Is there any way to analyse these errors, and could this be my prime suspect on dodgy hardware?
I have attached the graphs of the readings taken from OCCT on some of the voltages, temps. etc.

Thanks.

 

[richc46]

I really cannot give you a definitive answer to your question, but it does seem that you are having problems with your GPU. This may or may not be the cause of the BSODS, but it is something that has to be looked into. Dont even know if you can upgrade your particular GPU as it may be part of the MB. All that I can tell you for certain is that you need to correct the situation before looking further.

 

[richkempo]

Got another BSOD, which had the same 101 code, but the other codes were different. Is this dumpfile any different?

 

[richc46]

I have bolded the salient parts of your report. You will see where the problem lies.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_080912-8626-01.zip\080912-8626-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.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03046670
Debug session time: Thu Aug  9 13:33:51.375 2012 (GMT-4)
System Uptime: 0 days 0:23:00.359
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff88003174180, 7}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[B]Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE[/B] )
Followup: MachineOwner
---------

 

[richkempo]

Ok, so hardware wise I have tested the RAM with memtest and found no errors. I have stress tested the GPU and I did find some errors, but after installing an old nvidia 8800GTS, I suffered the same BSOD as I would with my normal gtx 560 ti. Prime95 has been run twice for over 12 hours altogether, and found no errors. Could it be that the mobo is faulty, or not compatible with my current setup ?

 

[richc46]

Lets try the driver verifier. If it is a driver problem, this will show. If this comes up negative, thats just one more indication of hardware.
Driver Verifier
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable