Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: I desperately need help with BSOD


13 Feb 2011   #1

Windows 7 64 Bit
 
 
I desperately need help with BSOD

I had someone custom build a system for me almost a year ago and recently started experiencing the Blue Screen of Death (BSOD). My dump logs dates the problems back to last month and WhoCrashed says its a memory problem, but it can be cause by improperly installed drivers. I get the BSOD at different times and atleast once a day. my system specs are:
Biostar Th55 HD mobo
2 gigs ram
Ati Radeon 5450 HD
Integrated mobo sound
Windows Ultimate x64 (I dont know if it's an oem version it came on the pc)

Attached you will find the files that can hopefully help you help me. Thanx in advance.

My System SpecsSystem Spec
.

13 Feb 2011   #2
Microsoft MVP

 
 

The ATKFUSService.exe (ATK Fast User Switch Service) is having issues. Please reinstall the software for this. It's available from the Asus support website: ASUSTeK Computer Inc.-Support-

The Intel Turbo Boost Technology Driver (Impcd.sys) is having issues. Please reinstall the software for this. It's available from the Intel Download Center website: http://downloadcenter.intel.com

Visit Windows Update to ensure that you have all available updates.

Your system only shows 179 mB of available memory and it's experiencing excessive pagination.
You need more memory (RAM). You have 2 gB on the system. Until you can get more RAM, please stop all of the programs that are loading at startup. There are 23 listed in the MSINFO32...Software Environment...Startup Programs report. Do not stop your antivirus from loading.

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Windows Update exceptions may be noted below for Windows drivers:
Code:

PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
http://www.carrona.org/dvrref.html#PxHlpa64.sys 

SaibVdAd64.sys Mon Oct 27 23:56:20 2008 (49068D64)
http://www.carrona.org/dvrref.html#SaibVdAd64.sys 

aswNdis2.sys Mon Jun 28 16:39:22 2010 (4C29087A)
http://www.carrona.org/dvrref.html#aswNdis2.sys 

aswNdis.sys  Sat Jan 09 16:22:03 2010 (4B48F37B)
http://www.carrona.org/dvrref.html#aswNdis.sys 

Saibad64.sys Mon Oct 27 23:56:15 2008 (49068D5F)
http://www.carrona.org/dvrref.html#Saibad64.sys 

Sahdad64.sys Mon Oct 27 23:56:11 2008 (49068D5B)
http://www.carrona.org/dvrref.html#Sahdad64.sys 

aswSnx.SYS   Mon Jun 28 16:39:47 2010 (4C290893)
http://www.carrona.org/dvrref.html#aswSnx.SYS 

lvuvc64.sys  Tue Nov 09 21:37:14 2010 (4CDA055A)
http://www.carrona.org/dvrref.html#lvuvc64.sys 

vpcvmm.sys   Wed Jul 22 18:20:22 2009 (4A6790A6)
http://www.carrona.org/dvrref.html#vpcvmm.sys 

aswFW.SYS    Mon Jun 28 16:39:59 2010 (4C29089F)
http://www.carrona.org/dvrref.html#aswFW.SYS 

aswTdi.SYS   Mon Jun 28 16:37:54 2010 (4C290822)
http://www.carrona.org/dvrref.html#aswTdi.SYS 

aswRdr.SYS   Mon Jun 28 16:33:15 2010 (4C29070B)
http://www.carrona.org/dvrref.html#aswRdr.SYS 

vpcnfltr.sys Wed Jul 22 18:20:17 2009 (4A6790A1)
http://www.carrona.org/dvrref.html#vpcnfltr.sys 

atikmpag.sys Tue Oct 26 22:14:23 2010 (4CC78AFF)
http://www.carrona.org/dvrref.html#atikmpag.sys 

cbfs64.sys   Wed Aug 12 14:33:09 2009 (4A830AE5)
http://www.carrona.org/dvrref.html#cbfs64.sys 

BS_I2cIo.sys Mon Jun 16 02:45:18 2008 (48560BFE)
http://www.carrona.org/dvrref.html#BS_I2cIo.sys 

BIOS64.sys   Sat Jun 07 20:12:00 2003 (3EE27F50)
http://www.carrona.org/dvrref.html#BIOS64.sys 

aswSP.SYS    Mon Jun 28 16:37:34 2010 (4C29080E)
http://www.carrona.org/dvrref.html#aswSP.SYS 

ISODrv64.sys Fri Nov 02 23:21:18 2007 (472BE92E)
http://www.carrona.org/dvrref.html#ISODrv64.sys 

ATKDispLowFilter.sys Tue May 13 23:03:13 2008 (482A5671)
http://www.carrona.org/dvrref.html#ATKDispLowFilter.sys 

atikmdag.sys Tue Oct 26 22:29:53 2010 (4CC78EA1)
http://www.carrona.org/dvrref.html#atikmdag.sys 

Rt64win7.sys Wed Jun 23 05:10:45 2010 (4C21CF95)
http://www.carrona.org/dvrref.html#Rt64win7.sys 

asusgsb.sys  Thu Sep 27 09:14:50 2007 (46FBACCA)
http://www.carrona.org/dvrref.html#asusgsb.sys 

mcdbus.sys   Tue Feb 24 05:34:07 2009 (49A3CD1F)
http://www.carrona.org/dvrref.html#mcdbus.sys 

vpcusb.sys   Wed Jul 22 18:20:23 2009 (4A6790A7)
http://www.carrona.org/dvrref.html#vpcusb.sys 

usbrpm.sys   Mon Jul 13 20:35:14 2009 (4A5BD2C2)
http://www.carrona.org/dvrref.html#usbrpm.sys 

vpchbus.sys  Wed Jul 22 18:20:23 2009 (4A6790A7)
http://www.carrona.org/dvrref.html#vpchbus.sys 

aswMonFlt.sys Mon Jun 28 16:32:58 2010 (4C2906FA)
http://www.carrona.org/dvrref.html#aswMonFlt.sys 

aswFsBlk.SYS Mon Jun 28 16:32:34 2010 (4C2906E2)
http://www.carrona.org/dvrref.html#aswFsBlk.SYS 

xusb21.sys   Thu Aug 13 18:10:17 2009 (4A848F49)
http://www.carrona.org/dvrref.html#xusb21.sys 

lvrs64.sys   Tue Nov 09 21:36:46 2010 (4CDA053E)
http://www.carrona.org/dvrref.html#lvrs64.sys 

RTKVHD64.sys Tue Jul 06 06:05:16 2010 (4C32FFDC)
http://www.carrona.org/dvrref.html#RTKVHD64.sys 

LUsbFilt.Sys Tue Nov 10 06:46:27 2009 (4AF95293)
http://www.carrona.org/dvrref.html#LUsbFilt.Sys 

LHidFilt.Sys Tue Nov 10 06:46:17 2009 (4AF95289)
http://www.carrona.org/dvrref.html#LHidFilt.Sys 

LMouFilt.Sys Tue Nov 10 06:46:23 2009 (4AF9528F)
http://www.carrona.org/dvrref.html#LMouFilt.Sys 

cpuz133_x64.sys Tue Mar 30 17:34:16 2010 (4BB26E58)
http://www.carrona.org/dvrref.html#cpuz133_x64.sys 

LVPr2M64.sys Fri May 07 21:38:16 2010 (4BE4C088)
http://www.carrona.org/dvrref.html#LVPr2M64.sys 

aw_host5.sys Mon Feb 19 05:35:33 2007 (45D97D75)
http://www.carrona.org/dvrref.html#aw_host5.sys 

awechomd.sys Mon Feb 19 05:35:10 2007 (45D97D5E)
http://www.carrona.org/dvrref.html#awechomd.sys 

8 memory dumps over a period of approximately 1 month
4 different BSOD error codes
2 different causes are blamed.
This isn't a clear cut hardware problem. I'd suggest running Driver Verifier according to these instructions if the above steps haven't fixed the problem:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code:
Delete these registry keys (works in XP, Vista, Windows 7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
While waiting for a reply to your next post, I'd suggest these free, bootable hardware diagnostics:
Quote:
I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Feb 11 23:58:32.111 2011 (UTC - 5:00)
System Uptime: 0 days 9:15:02.251
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00000030 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Feb 11 14:42:24.307 2011 (UTC - 5:00)
System Uptime: 0 days 17:41:35.463
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+10 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObFastReferenceObject+10
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`05094950 fffff880`080d9860 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Feb 10 20:59:41.860 2011 (UTC - 5:00)
System Uptime: 4 days 16:55:23.000
Probably caused by : memory_corruption ( nt!MiLogPageAccess+dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiLogPageAccess+dc
Bugcheck code 0000000A
Arguments fffffa80`0674120a 00000000`00000000 00000000`00000000 fffff800`05181d0c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Feb  6 04:03:12.604 2011 (UTC - 5:00)
System Uptime: 4 days 12:12:25.760
Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+1e4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  BumpTop.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!MiEmptyWorkingSet+1e4
Bugcheck code 00000050
Arguments fffffcca`e3000018 00000000`00000000 fffff800`051d8314 00000000`00000007
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Jan 24 21:57:48.191 2011 (UTC - 5:00)
System Uptime: 1 days 12:10:53.347
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339e3 )
BUGCHECK_STR:  0x1a_3452
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+339e3
Bugcheck code 0000001A
Arguments 00000000`00003452 00000000`1d86f000 fffff700`010e2218 bb200000`04f24c46
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Jan 15 15:46:30.879 2011 (UTC - 5:00)
System Uptime: 0 days 17:35:51.973
Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveMappedFileFault+8e
Bugcheck code 0000000A
Arguments 00000000`00000038 00000000`00000002 00000000`00000000 fffff800`0507168e
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Jan 14 22:09:29.908 2011 (UTC - 5:00)
System Uptime: 0 days 23:07:02.001
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00000038 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan 12 01:55:42.145 2011 (UTC - 5:00)
System Uptime: 3 days 22:00:27.301
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00000030 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
14 Feb 2011   #3

Windows 7 64 Bit
 
 

OK. I'm in the process of downloading and replacing outdated drivers, also have 2 gigs of memory to be delivered. I dont think i want to mess around with driver verifier though. I will follow your suggestions and post the results. Thank you so much for assisting me.
My System SpecsSystem Spec
.


15 Feb 2011   #4

Windows 7 64 Bit
 
 

So far I've updated some drivers. Others are software drivers like avast anti-virus which was installed before the first crash started occuring, so I left themalone for now. I've also installed an additional 2 gigs ram. Instead of the BSOD it now windows 7 now freezes. My next move is to continue replacing outdated drivers, and run harware test. Will continue to post update.
My System SpecsSystem Spec
15 Feb 2011   #5
Microsoft MVP

 
 

While Avast may have been present on the system before the crashes started - so were the other drivers.
Also, while the program may have been working normally previously, it's possible that internal corruption could have occurred - or that a recent update is interfering with it's working.

It's worthy to note that 3 of the BSOD's occurred in PROCESS_NAME: AvastSvc.exe
While this doesn't necessarily point to the cause - I have to wonder why it happens more in that process than in others.

Try this:
Quote:
Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes (I suggest Microsoft Security Essentials): Free AntiVirus
- uninstall the Avast from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Avast using this free tool: http://www.avast.com/eng/avast-uninstall-utility.html
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's
My System SpecsSystem Spec
15 Feb 2011   #6

Windows 7 64 Bit
 
 

Thanx i will uninstall and update avast or switch virus software aswell.
My System SpecsSystem Spec
18 Feb 2011   #7

Windows 7 64 Bit
 
 

Well I updated the drivers with a free program called DriverMax, I got the updated asus graphics driver from asus's website. Next, I unistalled avast and use it removal tool to get rid of its traces, then installed an updated version. I also removed magicDisc virtual disc software. Lastly, I upgraded my RAM by 2 gigs. So far the computer has been on for three days continuously with no BSOD's. Also my windows is now very responsive and aero effects that wasn't working has turned itself back on. This is a far cry from the nightly occurances of BSOD's and system freezing. Thanx alot SevenForums you rock.

Issue Solved ***Hopefully***
My System SpecsSystem Spec
Reply

 I desperately need help with BSOD




Thread Tools



Similar help and support threads for2: I desperately need help with BSOD
Thread Forum
Solved Desperately need help here Installation & Setup
Solved Desperately needed help on BSOD BSOD Help and Support
Please desperately in need of help General Discussion
BSOD I need help desperately, thank you! BSOD Help and Support
HELP desperately needed - Win 7 upgrade General Discussion
Help desperately needed! Hardware & Devices

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 04:09 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33