Windows 7 Daily BSOD Problems

Anh Nguyen

New Member
Joined
Jul 29, 2013
Messages
3
I've been getting daily BSODs for the last week or so (and one while compiling system specs for this post, so that most recent dump isn't on here). They throw different error messages, but all seem to point to ntoskrnl.exe as the source (from BlueScreenViewer). Also, it seems to happen almost exclusively while I'm browsing in Chrome (I can play games for hours and hours with no problem whatsoever).

Before I do anything drastic to try to fix this and possibly ruin some things, I figured I'd best ask some professionals about it first. I've attached the ZIP files as requested, can't seem to get RAMMon to run.
 


Attachments

Solution
Update the SSD firmware for now. Update the Intel Rapid Storage Technology (RST) drivers from either the mobo manufacturer's website or the Intel site ( Link Removed) - they're not critical right now, so if you don't get them updated don't worry for now.

Leave the Sonic CD/DVD driver alone for now. Manually removing it is likely to make the system unbootable.

The Asus AI Charger is the silly little utility that let's you charge USB devices even if the system is off. A while back (a year or more as I recall) they caused BSOD's. We haven't seen any blamed recently, so don't worry about it if you can't find it right now

All the stuff I'm telling you not to worry about could still be a problem. Once you remove all the other...
Just FYI - ntoskrnl.exe is the kernel (core) of the operating system. If it was actually to blame, you'd be seeing all sorts of problems - not just the occasional BSOD. In cases like these we look for 3rd party drivers that are interfering with the memory address' "owned" by ntoskrnl.exe

You have a NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.

The following devices have issues in Device Manager:
archlp ROOT\LEGACY_ARCSEC\0000 This device is not present, is not working properly, or does not have all its drivers installed.

Intel(R) 82579V Gigabit Network Connection PCI\VEN_8086&DEV_1503&SUBSYS_849C1043&REV_05\3&11583659&0&C8 This device is disabled.

Microsoft Virtual WiFi Miniport Adapter {5D624F94-8850-40C3-A3FA-A4FD2080BAF3}\VWIFIMP\7&1C9B64FD&0&01 This device is disabled.
The first device is likely associated with a program named Total Media Theater or an imaging type program from ArcSoft ( http://www.arcsoft.com/ ). If you've uninstalled this program, then go into Device Manager and uninstall the device by right clicking on it and selecting "Uninstall"
If unable to locate the device, click on the "View" menu item and select "Show hidden devices"

The other 2 devices are disabled. Is this deliberate? If so, why? Please enable the devices, update their drivers, then feel free to disable them again if you'd like.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] Link Removed [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: http://www.disc-tools.com/download/sptd
Manual procedure here: http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html

You have a wireless USB XBox controller (driver named xusb21.sys) that is known to cause BSOD's in Windows systems. Please uninstall it's software and physically remove the device from the system in order to test it.

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! :

PxHlpa64.sys Wed Oct 18 13:34:14 2006 (45366596)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Link Removed

AiCharger.sys Wed Oct 20 08:00:33 2010 (4CBED9E1)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed

Although I don't suspect it, the last BSOD blames your anti-virus drivers. In order to be sure you can reinstall the anti-virus program to eliminate any possibility of a corruption causing this.


Analysis:
The following is for informational purposes only.
**************************Mon Jul 29 22:00:12.045 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072913-17175-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 9:38:42.777
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by :aswMonFlt.sys ( aswMonFlt+5010 )
BugCheck 19, {20, fffff8a004809000, fffff8a004809420, 5420400}
BugCheck Info: Link Removed
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff8a004809000, The pool entry we were looking for within the page.
Arg3: fffff8a004809420, The next pool entry.
Arg4: 0000000005420400, (reserved)
BUGCHECK_STR: 0x19_20
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x19_20_aswMonFlt+5010
CPUID: "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed: 3600
CurrentSpeed: 3602
BIOS Version 1103
BIOS Release Date 04/10/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 28 18:39:55.301 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072813-14586-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 5:20:37.145
Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+100 )
BugCheck 7E, {ffffffffc0000005, fffff800031f99bc, fffff880065d2618, fffff880065d1e70}
BugCheck Info: Link Removed
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800031f99bc, The address that the exception occurred at
Arg3: fffff880065d2618, Exception Record Address
Arg4: fffff880065d1e70, Context Record Address
PROCESS_NAME: System
BUGCHECK_STR: 0x7E
FAILURE_BUCKET_ID: X64_0x7E_nt!ExDeferredFreePool+100
CPUID: "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed: 3600
CurrentSpeed: 3602
BIOS Version 1103
BIOS Release Date 04/10/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 27 22:41:42.602 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072713-14851-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 10:14:26.445
Probably caused by :memory_corruption ( nt!MiBadShareCount+4c )
BugCheck 4E, {99, 25001, 1, 25901}
BugCheck Info: Link Removed
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000025001, page frame number
Arg3: 0000000000000001, current page state
Arg4: 0000000000025901, 0
BUGCHECK_STR: 0x4E_99
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
CPUID: "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed: 3600
CurrentSpeed: 3602
BIOS Version 1103
BIOS Release Date 04/10/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 26 21:22:03.428 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072613-14632-02.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 1:50:51.271
Probably caused by :memory_corruption ( nt!MiBadShareCount+4c )
BugCheck 4E, {99, 36a24, 0, 109ca4}
BugCheck Info: Link Removed
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000036a24, page frame number
Arg3: 0000000000000000, current page state
Arg4: 0000000000109ca4, 0
BUGCHECK_STR: 0x4E_99
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
CPUID: "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed: 3600
CurrentSpeed: 3602
BIOS Version 1103
BIOS Release Date 04/10/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 26 19:03:12.864 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072613-14632-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:0 days 4:20:47.660
Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
BugCheck 1A, {41790, fffffa8000fade50, ffff, 0}
BugCheck Info: Link Removed
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000fade50
Arg3: 000000000000ffff
Arg4: 0000000000000000
BUGCHECK_STR: 0x1a_41790
PROCESS_NAME: privoxy.exe
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084
CPUID: "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed: 3600
CurrentSpeed: 3602
BIOS Version 1103
BIOS Release Date 04/10/2012
Manufacturer System manufacturer
Product Name System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

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.
**************************Mon Jul 29 22:00:12.045 2013 (UTC - 4:00)**************************
PxHlpa64.sys Wed Oct 18 13:34:14 2006 (45366596)
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
xusb21.sys Thu Aug 13 18:10:17 2009 (4A848F49)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys Mon Aug 2 22:47:59 2010 (4C57835F)
ICCWDT.sys Wed Aug 18 04:27:45 2010 (4C6B9981)
AsIO.sys Mon Aug 23 21:53:02 2010 (4C7325FE)
AiCharger.sys Wed Oct 20 08:00:33 2010 (4CBED9E1)
asahci64.sys Wed Mar 23 03:36:15 2011 (4D89A2EF)
bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604)
HECIx64.sys Mon Aug 15 13:29:24 2011 (4E495774)
iaStorF.sys Fri Aug 26 13:54:23 2011 (4E57DDCF)
dump_iaStorA.sys Fri Aug 26 13:55:27 2011 (4E57DE0F)
iaStorA.sys Fri Aug 26 13:55:27 2011 (4E57DE0F)
ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
asmtxhci.sys Wed Nov 2 23:00:22 2011 (4EB203C6)
asmthub3.sys Wed Nov 2 23:00:32 2011 (4EB203D0)
ax7v3974.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)
dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)
sptd.sys Sat Mar 3 11:45:52 2012 (4F524AC0)

GEARAspiWDM.sys Thu May 3 15:56:17 2012 (4FA2E2E1)
AtihdW76.sys Tue Nov 6 16:41:51 2012 (5099841F)
atikmpag.sys Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys Wed Dec 19 15:38:55 2012 (50D225DF)
NuidFltr.sys Fri Dec 28 06:15:22 2012 (50DD7F4A)
point64.sys Fri Apr 12 08:15:29 2013 (5167FAE1)
dc3d.sys Fri Apr 12 08:15:46 2013 (5167FAF2)
aswRvrt.sys Thu May 9 04:47:02 2013 (518B6286)
aswFsBlk.SYS Thu May 9 04:47:16 2013 (518B6294)
aswMonFlt.sys Thu May 9 04:47:23 2013 (518B629B)
aswTdi.SYS Thu May 9 04:47:32 2013 (518B62A4)
aswrdr2.sys Thu May 9 04:47:41 2013 (518B62AD)
avgtpx64.sys Tue May 28 10:57:10 2013 (51A4C5C6)
aswVmm.sys Thu Jun 27 11:35:59 2013 (51CC5BDF)
aswSP.SYS Thu Jun 27 11:37:21 2013 (51CC5C31)
aswSnx.SYS Thu Jun 27 11:37:25 2013 (51CC5C35)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Jul 28 18:39:55.301 2013 (UTC - 4:00)**************************
anio61hx.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 27 22:41:42.602 2013 (UTC - 4:00)**************************
a15qnvbp.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 26 21:22:03.428 2013 (UTC - 4:00)**************************
a0eilmbz.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 26 19:03:12.864 2013 (UTC - 4:00)**************************
abx5udtu.SYS Tue Dec 27 17:30:45 2011 (4EFA4715)
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
ax7v3974.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
aswrdr2.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
anio61hx.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.
a15qnvbp.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.
a0eilmbz.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.
abx5udtu.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.
 


Wow, that was fast, and incredibly thorough, thank you very much.

You have a NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter...

Got it, I've been looking for a reason to replace that anyways.

SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's...

I can update the SSD firmware, but how would I go about updating the controller drivers on the motherboard?

The following devices have issues in Device Manager:
The first device is likely associated with a program named Total Media Theater or an imaging type program from ArcSoft ( http://www.arcsoft.com/ ). If you've uninstalled this program, then go into Device Manager and uninstall the device by right clicking on it and selecting "Uninstall"
If unable to locate the device, click on the "View" menu item and select "Show hidden devices"

Done.

The other 2 devices are disabled. Is this deliberate? If so, why? Please enable the devices, update their drivers, then feel free to disable them again if you'd like.

I uninstalled both, Intel(R) 82579V Gigabit Network Connection PCI was automatically reinstalled and updated. Don't know where that third one came from, but it's gone now.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

You have a wireless USB XBox controller (driver named xusb21.sys) that is known to cause BSOD's in Windows systems. Please uninstall it's software and physically remove the device from the system in order to test it.

Both are removed.

PxHlpa64.sys Wed Oct 18 13:34:14 2006 (45366596)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Link Removed

Can't find the program that corresponds to this, but did remove several CD/DVD burning utilities. How would I go about removing the driver itself?

AiCharger.sys Wed Oct 20 08:00:33 2010 (4CBED9E1)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
Link Removed

Can't seem to find this, either, but dropping by the ASUS site and checking up on my motherboard shows that I'm behind about two-years worth of BIOS updates. Would it be a good idea to proceed with that?

Also, silly side note: I distinctly remember buying 16 GB of RAM that came in 4 x 4 GB sticks. I've checked that all four are installed, yet it seems only 8 GB of that are functioning. I've tried reseating them in the same slots twice, will try again in different slots and in sets of 3 to find out which, if any, are malfunctioning.

Again, thank you very much for you help. I will return with updates (good or bad) after I've carried out these procedures.

EDIT: Memory's fine, just seating problems. It's fixed now and I'm back to glorious 16 GB. I don't know how long the memory's been problematic, however, so it may or may not have played into the BSOD issues (or caused by BSOD issues).
 


Last edited:
Update the SSD firmware for now. Update the Intel Rapid Storage Technology (RST) drivers from either the mobo manufacturer's website or the Intel site ( Link Removed) - they're not critical right now, so if you don't get them updated don't worry for now.

Leave the Sonic CD/DVD driver alone for now. Manually removing it is likely to make the system unbootable.

The Asus AI Charger is the silly little utility that let's you charge USB devices even if the system is off. A while back (a year or more as I recall) they caused BSOD's. We haven't seen any blamed recently, so don't worry about it if you can't find it right now

All the stuff I'm telling you not to worry about could still be a problem. Once you remove all the other problems, then if the problems continue we can deal with the "don't worry" list one-by-one.

I have an Asus P6T Deluxe v2 mobo that does the same thing (and has been doing it since at least last June). I had problems with the v1 of this mobo and that's why I moved to v2 - and now I'm retiring that system because of the issues.

As for the BIOS updates - yes, perform the updates. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard. Flash from within Windows (if possible) that'll help prevent mistakes from being written to the BIOS.
 


Solution
Well, it's been a couple of days and everything's running much smoother. No BSOD since I updated the SSD firmware.

Thought I'd drop by with the good news. Thank you very much. I hope we never meet here again.
 


Back
Top