Windows 7 [BSOD] Random BSOD's and hangs at startup

[WojtekK1902]

Hello,
I have very annoying problem with BSOD and computer hangs at the computer start:
After Windows 7 is started there is always a BSOD, sometimes I have to restart the computer many times to make it work again, because it hangs (or shows BSOD) at every startup (even before Windows is run) or when the welcome screen of Windows 7 or desktop appears.
It's getting worse and worse - eg. today I had to restart it 7 times, because it was crashing all the time.
When at last it starts properly, everything is fine and there is no problem, but when I turn it off and turn it on again, everything happens again... Only seldom system crashes long time after startup - the whole problem occurs at startup.
I am sending the zip file as an attachment - there are logs and dumps from W7F Diagnostic Tool, screens from CPU-Z and HTML file from PassMark RAMMon.
Thank you in advance for any help!

 

[WojtekK1902]

Hello,
I am sorry that I haven't responded for such a long time, but I wasn't at home.
Unfortunately, it is getting worse and worse with the computer... Today it hanged or restarted itself about 15 times... I had huge difficulties to turn it on at all. Majority of these hooks happened before booting Windows.
When I finally managed to run the computer and noticed that it is stable, I performed few tests.
I have performed the test with the use of OCCT (it has a Power Supply test). I set the one-hour benchmark, but I had to stop it about half an hour earlier as the temperature of my Graphic Card was 97 centidegrees and I didn't want to burn it. I'm attaching the result charts of the OCCT test - could you please have a look on them?
I am also attaching the data from CPUID HWMonitor - the screenshot and text data (Monitoring data and SMBus data) as well. Maybe you could find some interesting information there?
Moreover, I am attaching new minidump files as there were also some BSODs.
I am also providing the latest Administrative Events.

Could you please take a look on all of these files? Thank you!

 

[usasma]

The most significant item here is your description of the graphics card overheating. There are also EventID 41 codes in the Admin Event Viewer logs - and this is suggestive of a shutdown due to overheating. This shouldn't happen, so it's time to look at the cooling solution for the graphics card. Check the fan to make sure it's working, make sure the cooler doesn't have dirt/dust in it; make sure that the cooler is firmly attached to the card (DO NOT TOUCH IT!!! I've received 2nd degree burns doing this!!!) and make sure that there's adequate airflow to the card.

The memory dumps are also suggestive of hardware problems - which brings us back to fixing the overheating first.
If the BSOD's continue and the video card doesn't overheat - then we'll look at other hardware causes (try these free diagnostics: Link Removed )

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Mon Aug 12 09:12:19.466 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\081213-28516-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:49.856[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for hcmon.sys
*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
Probably caused by :[B]hcmon.sys ( hcmon+6289 )[/B]
BugCheck [B]A, {fffff98001528fa0, 2, 1, fffff80003397578}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff98001528fa0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
   bit 0 : value 0 = read operation, 1 = write operation
   bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003397578, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID: [B][COLOR=RED]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
PROCESS_NAME:  vmware-usbarbi
FAILURE_BUCKET_ID: [B]X64_0xA_VRF_hcmon+6289[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 11 07:14:43.012 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\081113-25287-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_8b484024`5c8b48cb
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_8b484024`5c8b48cb
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:03:34.792[/B]
*** WARNING: Unable to verify timestamp for Unknown_Module_8b484024`5c8b48cb
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_8b484024`5c8b48cb
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff88002f91b10, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002f91b10, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug  9 10:35:47.401 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080913-26816-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:16.180[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for disk.sys
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for volmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for volsnap.sys
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.sys
Probably caused by :[B]disk.sys ( disk+12c6 )[/B]
BugCheck [B]C1, {fffff9801c280fe0, fffff9801c280e78, 190018, 32}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff9801c280fe0, address trying to free
Arg2: fffff9801c280e78, address where one bit is corrupted
Arg3: 0000000000190018, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
BUGCHECK_STR:  0xC1_32
PROCESS_NAME:  NMIndexStoreSv
FAILURE_BUCKET_ID: [B]X64_0xC1_32_VRF_disk+12c6[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Aug  9 10:32:35.566 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080913-25038-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:02:05.361[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+200e6 )[/B]
BugCheck [B]1A, {5010, fffff781c0000000, c7, d8000001ac}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000005010, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 00000000000000c7
Arg4: 000000d8000001ac
BUGCHECK_STR:  0x1a_5010
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0x1a_5010_VRF_nt!_??_::FNODOBFM::_string_+200e6[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug  6 08:44:55.055 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080913-26083-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:25:12.814[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by :[B]win32k.sys ( win32k!HMFreeObject+136 )[/B]
BugCheck [B]C2, {7, 109b, 0, fffff900c0809a60}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff900c0809a60, Address of the block of pool being deallocated
BUGCHECK_STR:  0xc2_7
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: [B]X64_0xc2_7_VRF_win32k!HMFreeObject+136[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Aug  6 08:16:46.414 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080613-30030-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:43.208[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for hcmon.sys
*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys
Probably caused by :[B]hcmon.sys ( hcmon+6289 )[/B]
BugCheck [B]A, {fffff980015b6fa0, 2, 1, fffff80003351578}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff980015b6fa0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
   bit 0 : value 0 = read operation, 1 = write operation
   bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003351578, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID: [B][COLOR=RED]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
PROCESS_NAME:  vmware-usbarbi
FAILURE_BUCKET_ID: [B]X64_0xA_VRF_hcmon+6289[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Mon Aug 12 09:12:19.466 2013 (UTC - 4:00)**************************
ASACPI.sys  Wed May 13 21:25:17 2009 (4A0B72FD)
intelppm.sys  Mon Jul 13 19:19:25 2009 (4A5BC0FD)
3xHybr64.sys  Thu Dec 17 04:07:06 2009 (4B29F4BA)
amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
vmci.sys  Mon Apr 30 21:14:27 2012 (4F9F38F3)
GEARAspiWDM.sys  Thu May  3 15:56:17 2012 (4FA2E2E1)
Rt64win7.sys  Tue Jun 12 10:00:29 2012 (4FD74B7D)
RTKVHD64.sys  Tue Jun 19 04:50:56 2012 (4FE03D70)
VMNET.SYS  Sun Jul  8 03:58:34 2012 (4FF93DAA)
vmnetbridge.sys  Sun Jul  8 03:59:19 2012 (4FF93DD7)
vsock.sys  Tue Aug 21 17:10:15 2012 (5033F937)
hcmon.sys  Thu Oct 11 20:15:27 2012 (5077611F)
MpFilter.sys  Wed Oct 31 18:43:06 2012 (5091A97A)
VMparport.sys  Thu Nov  1 03:48:19 2012 (50922943)
vmnetuserif.sys  Thu Nov  1 04:00:20 2012 (50922C14)
VMkbd.sys  Thu Nov  1 04:31:30 2012 (50923362)
vmx86.sys  Thu Nov  1 05:23:47 2012 (50923FA3)
athrx.sys  Mon Mar 11 07:04:29 2013 (513DBA3D)
nvlddmkm.sys  Fri Jun 21 05:06:16 2013 (51C41788)
[/font]

Link Removed
Link Removed
3xHybr64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[WojtekK1902]

Thank you for your reply, I will try this. What is the highest allowed temperature of graphic card during these stress tests?
However, I have one more question - I have taken a look to the CPUID HWMonitor right after Windows starts. What I noticed is that the value of voltage on +12V at the beginning is about 9V and after a while it very slowly increases to 11.933V. I am just wondering if 9V is not too low? Especially taking into consideration the fact that all the problems happen at the start of the computer?

 

[usasma]

I don't like to see graphics cards above 90ºC when doing stress testing.
The problem with the voltage is (IMO) not good. But I'm not a hardware expert. I'd have to suggest that you post in the hardware forums for further advice (about replacing the power supply).

Good luck!

 

[WojtekK1902]

Hello everybody,

I am writing to you with the following problem - in THIS thread I receive help with very annoying problems - BSODs and hangs etc. I was told that everything indicated that it was the problem related to the hardware. I have noticed in the CPUID HWMonitor that right after Windows starts, the value of voltage on +12V at the beginning is about 9V and after a while it very slowly increases to 11.933V. I am just wondering if 9V is not too low? Especially taking into consideration the fact that all the problems with the computer happen at the start of the computer?

 

[WojtekK1902]

Thank you very much for your reply and advice. I have posted the question in the hardware forums: Link Removed

 

[Mike]

Coming off the 12V rail should be 12.xV. Use AIDA64 just to make sure. It should not go down to 9V. As far as any CPU or RAM voltage modifications, do not even touch it in the BIOS. Use failsafe settings for stability if necessary Your CPU/motherboard combo should self-regulate with your board and your processor. I looked at the old upload and it looks right. What we never got was voltage going directly to the GPU. That will be the cause of your woe if its a PSU issue and lack of power coming off the rail. When does it stall most often? When GPU is at full acceleration or...? If the problem has been going on for this long, it may well be time to upgrade your PSU. How many watts is the PSU? There is an online calculator for this based on your HW specs.

 

[Mike]

Merged as one issue.

 

[Mike]

I have performed the test with the use of OCCT (it has a Power Supply test). I set the one-hour benchmark, but I had to stop it about half an hour earlier as the temperature of my Graphic Card was 97 centidegrees and I didn't want to burn it.

The TJMAXX for the GeForce 9800 series is 105 C you are lucky you did not melt down the entire system. I would seriously consider either a better PSU or a new card. The cheapest way is a higher wattage PSU and if it doesn't work send it back. If you upgrade your card and the PSU can't support it, no use doing that.

http://www.extreme.outervision.com/psucalculatorlite.jsp

 

[WojtekK1902]

Hello Mike, thank you very much for your reply and help.
Unfortunately I would like to ask you for some explanation... First of all, where in AIDA64 could I find the current voltage?
Moreover, is there any possibility to check the value of voltage going directly to GPU?
And the computer stalls at the computer's start - sometimes a minute or two after Windows starts and sometimes even before Windows boots.

 

[Mike]

Hello Mike, thank you very much for your reply and help.
Unfortunately I would like to ask you for some explanation... First of all, where in AIDA64 could I find the current voltage?
Moreover, is there any possibility to check the value of voltage going directly to GPU?
And the computer stalls at the computer's start - sometimes a minute or two after Windows starts and sometimes even before Windows boots.

Under Computer - Sensors - Voltage Values

If a 12V rail is connecting into the GPU, it's going to be 12V

 

[WojtekK1902]

Thank you. Unfortunately I have trial version, so it looks like this:

And, as you can see, I don't have so many Voltage values as you...

 

[Mike]

This also depends on whether a 12V rail is literally going out of the PSU and into the graphics card. This is required for higher end cards. It looks normal to me. The computer simply will not start with not enough voltage. The concern is whether or not the entire system is getting enough wattage from the PSU, because you have not specified how many watts your PSU is. You really need to use the calculator I gave you above to get some estimate because it is either going to end up being:

The video graphics card is defective.
You do not have enough power to operate all of your PCI devices with the current PSU.

So its going to be one or the other. If you have a 1,000 watt power supply, we immediately can rule out a PSU problem for now and its probably the card. But if you don't know, or can't bother to check, this is going to keep going on forever.

 

[WojtekK1902]

I am sorry that I haven't written how many watts my PSU is, I had to check this... But now I know that it is 400W. What do you think about this? Unfortunately the PSU calculator you have given doesn't work...

 

[Mike]

"400 watts is enough for the average system with a dual or quad core CPU running at stock speed, with a single hard drive, 4gb of RAM and single DVD/CD drive, and the 9800GT installed." However, these PSU's degrade with time, although, quite differently.

If it was the PSU, I suspect the system would be experiencing all sorts of weird shutdowns. You talked to John earlier about overheating the GPU. Is that still happening? Its possible that for all this time you just have a defective card. I really can't say. Usually what you do in this situation is you buy both parts if you can, and whichever one solves the problem, you send the other one back. In the ideal situation that is what would be done.

 

[WojtekK1902]

I believe that the problem is not related to the GPU. At least I hope so. Currently I am going to buy new PSU. I don't think that situation when there is about 9V at 12V is normal, even if it increases later...
And at this moment the temperature of GPU is 57 centidegrees.

 

[WojtekK1902]

Hello,

I would like to thank you all for your kind help - my problem is resolved at last! I have bought a new PSU and I have no problems at all! I think that the old one was broken so there were some issues with the voltage. Thank you once again!