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

WojtekK1902

Active Member
Joined
Oct 30, 2012
Messages
79
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!
 


Attachments

Solution
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!
Your BIOS dates from 2008. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

These devices have issues in Device Manager:
Microsoft Virtual WiFi Miniport Adapter #2 {5D624F94-8850-40C3-A3FA-A4FD2080BAF3}\VWIFIMP\5&A8102B5&0&01 This device is not working properly because Windows cannot load the drivers required for this device.
VMware Virtual Ethernet Adapter for VMnet1 ROOT\VMWARE\0000 This device is disabled.
VMware Virtual Ethernet Adapter for VMnet8 ROOT\VMWARE\0001 This device is disabled.
Right click on the Microsoft Virtual WiFi Miniport Adapter #2 and select "Un-install", reboot for changes to take effect (?affect?)
Un-install VMWare Ethernet Adapters. If you need them, reinstall the latest version of them after the system has stabilized.

Comodo Internet Security occasionally has issues when it gets corrupted. Please uninstall it (and install a free anti-virus) in order to test. Ensure that the Windows Firewall is turned back on.

Memory dumps blame your wireless (although this could also have been your Comodo). Please:
- download a fresh copy of the latest wireless drivers
- un-install the current wireless drivers from your system
- install the freshly downloaded wireless drivers
- monitor for further BSOD's

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

Ph3xIB64.sys Fri May 8 17:11:49 2009 (4A04A015)
Phillips/NXP Semiconductors Inbox
Ph3xIB64.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.

If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Link Removed




Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Mon Jul  8 13:42:11.239 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071013-21262-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:48.629[/B]
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by :[B]athrx.sys ( athrx+47677 )[/B]
BugCheck [B]D1, {10, 2, 0, fffff88001473566}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001473566, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_athrx+47677[/B]
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  0418   
  BIOS Release Date             12/09/2008
  Manufacturer                  PCF
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul  6 06:04:34.908 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070613-20826-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:54.298[/B]
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by :[B]athrx.sys ( athrx+47677 )[/B]
BugCheck [B]D1, {10, 2, 0, fffff8800172d566}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800172d566, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_athrx+47677[/B]
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2341[/B]
  BIOS Version                  0418   
  BIOS Release Date             12/09/2008
  Manufacturer                  PCF
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul  4 11:39:17.035 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070413-23992-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.815[/B]
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by :[B]athrx.sys ( athrx+47677 )[/B]
BugCheck [B]D1, {10, 2, 0, fffff88001453566}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001453566, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_athrx+47677[/B]
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  0418   
  BIOS Release Date             12/09/2008
  Manufacturer                  PCF
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun 28 07:45:37.222 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062813-25677-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:59.001[/B]
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by :[B]athrx.sys ( athrx+47677 )[/B]
BugCheck [B]D1, {10, 2, 0, fffff8800152d566}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800152d566, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_athrx+47677[/B]
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  0418   
  BIOS Release Date             12/09/2008
  Manufacturer                  PCF
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jun 25 10:11:26.596 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\062513-22822-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:54.376[/B]
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by :[B]athrx.sys ( athrx+47677 )[/B]
BugCheck [B]D1, {10, 2, 0, fffff88001511566}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001511566, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_athrx+47677[/B]
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2333[/B]
  BIOS Version                  0418   
  BIOS Release Date             12/09/2008
  Manufacturer                  PCF
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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.
Code:
[FONT=lucida console]**************************Mon Jul  8 13:42:11.239 2013 (UTC - 4:00)**************************
[B]Ph3xIB64.sys                Fri May  8 17:11:49 2009 (4A04A015)[/B]
ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
[B]athrx.sys                   Tue Jun  9 14:06:49 2009 (4A2EA4B9)[/B]
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
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)
inspect.sys                 Wed Nov  7 17:07:02 2012 (509ADB86)
cmdhlp.sys                  Wed Nov  7 17:07:03 2012 (509ADB87)
cmdguard.sys                Wed Nov  7 17:07:39 2012 (509ADBAB)
nvlddmkm.sys                Thu Mar 14 21:37:00 2013 (51427B3C)
[/FONT]
Ph3xIB64.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
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
 


Last edited:
Hello,
Thank you very much for your kind help.
I have updated BIOS and removed Microsoft Virtual WiFi Miniport Adapter. I have also update atheros driver (athrx.sys).
Unfortunately, I have more problems with other drivers:
1) I have no idea what Ph3xIB64.sys is... I have googled for it and found only sites that tell it may be the cause of many problems and that offer me some software to download, purchase and update that driver... I don't trust them...
2) I have the latest version of ASACPI.sys driver... It is dated from 2009 but there is no newer one on ASUS site...

Can you help me with Ph3xIB64.sys driver?
 


The Ph3xIB64.sys driver is related to a Phillips 713x Inbox PCI TV Card -

Could you check your motherboard and see if you have any extra PCI card (aside from graphics and/or networking card) plugged in - that could be the TV Card.

To Enable/Uninstall this driver (first thing I'd do), go to Devices & Printers in your Control Panel (Under: Control Panel > Hardware and Sound > Devices and Printers) and look for any icon that displays the TV Card. It should be under "Devices", but I'm pretty sure cards such as these can be listed under "Unspecified" or not at all.

IF: You see the device in Control Panel -
To Remove:
Right-click, "remove device".

Alternatively, if it's listed under "Unspecified":
Go to "Device Manager", and under (I think, look around if it isn't there) "Monitors", "Display Adapters" and other related "Media" tabs. Once you've located the TV Card, right click it and select "Uninstall".

Once you've removed this driver, and assuming you still want/need it:
Locate the driver disk related to the product (if you can't find it/don't have it, contact Phillips and ask) and reinstall the drivers.
 


Thanks GeneralHiningII!!!

DO NOT pay for programs to update/uninstall/remove drivers - there are many good products out there that will do it for free (if needed). Personally I don't use them because it's much simpler and more reliable to do it manually.

As for the ASACPI.sys driver, the 2009 version is the most current - so it's the one to leave installed.
Usually I remove the RED highlighting, but must've missed it with the last post - sorry!

Once the Ph3xIB64.sys driver is updated/removed, then we wait for the next BSOD.
If you don't get any - well then it's fixed!
If you do get some - zip up the contents of C:\Windows\Minidump and upload it with your next post.
 


Hello!
Thank you for your reply. Unfortunately I cannot find the TV Card in Device Manager...
Up to this time I didn't have any BSOD but unfortunately the computer has hanged once and after I restarted it, after few minutes it restarted itself...
 


Looking through old forum posts I found this:

Hi,
1. Have you made any changes to the computer prior to the issue?
Try the Methods provided below and check if the issue persists.
Method 1:
Windows Device Manager needs to have the Plug and Play service enabled in order to work correctly
Try the steps provided below to check and enable the plug and play service.
a) Click on start
b) Type “Services” in the start search bar
c) Scroll down and find the Plug and Play service. Double-click on it and make sure the Start up type is set to Automatic and click Start if the service is not running.
d) Restart the computer.
Check to see if your Device Manager is still blank or not.
Method 2:
a) Go to "Start", and enter "regedt"
b) Maximize the "HKEY_LOCAL_MACHINE" window.
c) Scroll down to "SYSTEM\CurrentControlSet\Enum"
d) With "Enum" selected click the "Security", "Permissions" menu.
Note: At this point you will probably notice there are no permissions on this key
e) Click "Add".
f) . Add the group "Everyone" and the user "SYSTEM".
g) Select "Everyone" and check "Read" ONLY!
h) Select "SYSTEM" and check "Full Control".
i) Click the "Advanced" button at the bottom of the window
j) On the Advanced window check "Reset permissions on all child objects...
k) Click "OK"
l) On the warning window click "Yes"
m) Close Regedit
Note:
Modifying REGISTRY settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of REGISTRY settings can be solved. Modifications of these settings are at your own risk.

using this fix, see if you can find your TV card.

IF not, poke around your CD collection and see if you can find the driver installation disc for this TV Card. Put it in and reinstall the driver, then uninstall it.

To add on to usasma's first analysis:


All your dumps have been caused by athrx.sys, which is Atheros' driver for their WLAN Card/Adapters (external/internal). I'm going to go on a limb here and say that if you disable that driver (or the whole device) your blue screens will hopefully stop.

To get rid of this driver you have a few options:

Option 1
Link Removed - A free tool which lets you fully remove drivers from your system. In my opinion much better than Windows Device Manager.
Download and install Driver Sweeper, and reboot your computer in to Safe Mode. Once you're in Safe Mode, run Driver Sweeper and check the relevant driver boxes for athrx.sys.
Then click Analyze & Clean.
Reboot your computer once more, and test for bluescreens.

Option 2
Device Manager -
In Device Manager, under theNetwork Adapters tab -
Right click the relevant wireless card and under Properties and Uninstall.

<Alternatively, if you need this WLAN Adapter>:
Under Properties > Advanced (If there is no "Advanced" option, click the Drivers tab).
There should be a button called "Roll Back Driver". Click this and let Windows install an older driver version for this device.
To make sure this works, you could change Windows Updates settings, and change it so that Windows Update will notify you of updates, but will not download and install them automatically.
 


Hello,

I found that my TV card is marked as ASUSteK Tiger Capture Device. I found the newest drivers on ASUSteK website and installed them.

I am afraid that I cannot uninstall Atheros drivers... I think that without them, my network won't work... Don't you think so?

Unfortunately, my computer hanged and restarted itself once more... Strange is the fact, that it sometimes restarts or hangs on startup (before Windows are run). Moreover, I had another BSOD - I have added it as an attachment...

Thank you for your help...
 


Attachments

From my previous post:
Comodo Internet Security occasionally has issues when it gets corrupted. Please un-install it (and install a free anti-virus) in order to test. Ensure that the Windows Firewall is turned back on.
This problem involves your networking sub-system - and nothing goes through the networking sub-system unless Comodo OK's it. Corruption to this program is (IME) fairly common - and it frequently caused BSOD's (again, IME).

If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Link Removed

Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Wed Jul 17 14:11:48.272 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071713-42042-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:04:42.051[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]win32k.sys ( win32k+1919c4 )[/B]
BugCheck [B]7F, {8, 80050031, 6f8, fffff800032cd447}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff800032cd447
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: [B]X64_0x7f_8_win32k+1919c4[/B]
CPUID:        "Intel(R) Core(TM)2 Quad  CPU   Q8200  @ 2.33GHz"
MaxSpeed:     2330
CurrentSpeed: [B]2341[/B]
  BIOS Version                  0802   
  BIOS Release Date             05/12/2010
  Manufacturer                  PCF
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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.
Code:
[FONT=lucida console]**************************Wed Jul 17 14:11:48.272 2013 (UTC - 4:00)**************************
ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
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)
inspect.sys                 Wed Nov  7 17:07:02 2012 (509ADB86)
cmdhlp.sys                  Wed Nov  7 17:07:03 2012 (509ADB87)
cmdguard.sys                Wed Nov  7 17:07:39 2012 (509ADBAB)
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
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
Link Removed
Link Removed
Link Removed
 


Last edited:
Thank you for your reply. I have uninstalled Comodo and turned on Windows Firewall. I will see if it helps.
However, I would like to have some better firewall than Windows one. Can you suggest anything free?
 


I haven't used a 3rd party firewall since I started using the beta's of Windows Vista in 2006 (I used the Sygate Personal Firewall in XP).

Throughout the years I've found that other firewalls seem to be more trouble than they are worth - and have stayed away from them. I did find the Sphinx Firewall control back when I was using Win7 and other users seemed to like it: Windows7FirewallControl: Sphinx Software I don't use it either.

Leave the Comodo off until you've determined if it's the cause or not (by the absence of BSOD's). You can always install a fresh copy and see if that works. And, should the BSOD's recur - then you know that the first thing to try is removing the Comodo.
 


Hello,
Unfortunately, my computer restarted itself again, even without Comodo... But there wasn't BSOD, so I cannot attach any minidump file. Do you know what could I do?
 


Please zip up and upload the contents of C:\Windows\Minidump

Please do the following:
- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

Please run Driver Verifier according to these instructions: Link Removed
 


Thank you very much for your answer. I'm attaching files you asked for.
I have also followed the instructions of using the Driver Verifier but up to this time there was no BSOD.
 


Attachments

There's a lot of errors in the Admin report - and some are suggestive of hardware problems.
Please also run these free hardware diagnostics: Link Removed
Let us know the results and we can move on from there.
 


Uninstall and reinstall your Atheros drivers - if you have a 4G wireless card then you can use that if you are in dire need of internet.

First download the corresponding drivers from Atheros' site, but don't install it. The downloaded file should be an executable file (.exe), so copy it and paste it on to your Desktop or a place where you can remember easily.

Now, following my instructions:
Option 1
Link Removed - A free tool which lets you fully remove drivers from your system. In my opinion much better than Windows Device Manager.
Download and install Driver Sweeper, and reboot your computer in to Safe Mode. Once you're in Safe Mode, run Driver Sweeper and check the relevant driver boxes for athrx.sys.
Then click Analyze & Clean.
Reboot your computer once more, and test for bluescreens.

Option 2
Device Manager -
In Device Manager, under theNetwork Adapters tab -
Right click the relevant wireless card and under Properties and Uninstall.

<Alternatively, if you need this WLAN Adapter>:
Under Properties > Advanced (If there is no "Advanced" option, click the Drivers tab).
There should be a button called "Roll Back Driver". Click this and let Windows install an older driver version for this device.
To make sure this works, you could change Windows Updates settings, and change it so that Windows Update will notify you of updates, butwill not download and install them automatically.​
I also provided a section at the bottom for still using the same device and rolling back the drivers through Windows Device Manager.
 


Hello,
I have made two hardware test - one of graphic card and one of CPU. There were no errors and everything went fine.
Moreover, I didn't have any problem for a few days - there were no hangs, no BSODs etc.
Unfortunately, today suddenly I had next BSODs... I am sending dumps as an attachment - could you please have a look and tell me what was the problem?
 


Attachments

There are more than just CPU and graphics tests in the link that I provided. Please perform ALL of the tests at the link.

These memory dumps are STOP 0x1A errors and point to hardware. There is a memory test listed as one of the first tests in the link that I provided ( Link Removed ) - please run it (and the rest of the tests).

Analysis:
The following is for informational purposes only.
**************************Sun Jul 28 08:04:19.227 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072813-23821-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 0:00:47.007
Probably caused by :hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )
BugCheck 1A, {41287, 2, 0, 0}
BugCheck Info: Link Removed
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
Parameter 2 contains the referenced virtual address.
Arg2: 0000000000000002
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR: 0x1a_41287
PROCESS_NAME: WerFault.exe
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 28 08:02:17.774 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072813-25069-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 0:00:15.568
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2984f )
BugCheck 1A, {5003, fffff781c0000000, 557, 55900000a8e}
BugCheck Info: Link Removed
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 0000000000000557
Arg4: 0000055900000a8e
BUGCHECK_STR: 0x1a_5003
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x1a_5003_VRF_nt!_??_::FNODOBFM::_string_+2984f
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

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.
**************************Sun Jul 28 08:04:19.227 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)
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)
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
 


Hello,
Thank you very much for your reply. I am sorry I didn't run the other tests - I thought that I should run these described on that page only.
However, I did the tests of:
1) memory (3 passes) with 0 errors
2) HDD (full test) with 0 errors
3) malware (the one from Trend Micro) with 0 threats found
So I really don't know where is the problem... One time I thought that the problem could be related to the power supply adaptor. Is there any test that could check this? What is really suspicious is the fact that sometimes, when the computer freezes and I have to switch it off (I don't have "restart" button) and then I switch it on again, it behaves very strangely: it starts to run, it turns off itself (!!!) and after a short while it turns on itself again (!!!). What could be the reason?
 


There is a power supply test in one of the video tests (at the link I gave earlier).
Please run the rest of the tests listed at the link that I provided.

Once the tests are complete, then we start with this: Link Removed
 


Back
Top