BSOD & SWTOR (Dump Inside)

usasma · 10 Feb 2012

You did good work! Now let's wait and see if it BSOD's again.
Don't worry about the overclock as it's only 48 or 49 mHz.

projectdwnshft · 14 Feb 2012

ok so it seems that my problem may have not been resolved after all, just had a crash while playing SWTOR again, with chrome open as well heres the dump.

projectdwnshft · 14 Feb 2012

just crashed again heres the new dump

usasma · 14 Feb 2012

You went 4 days without a BSOD, and now you've had 2 in the space of an hour or so.
What is different today? What programs were running that haven't been used for 4 days?

Another older driver popped up - it's either the Avanquest Connection Manager - or the connection manager that you may have used to install a router. Did you do this, and can you check the router CD to see if that's where BVRPMPR5a64.sys came from? It's dated from 2007.

If the BSOD's continue, first try running Driver Verifier according to these instructions: Driver Verifier Settings

Then, upload those memory dumps and start with the free diagnostics here: Hardware Diags
Start with the memory diagnostic and Prime95.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


vmbus.sys       Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys       Sat Nov 20 04:20:02 2010 (4CE792C2)
RzSynapse.sys   Wed Apr 06 05:29:13 2011 (4D9C3269)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
LMouFilt.Sys    Sat Apr 30 07:51:45 2011 (4DBBF7D1)
LHidFilt.Sys    Sat Apr 30 07:51:39 2011 (4DBBF7CB)
cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
NisDrvWFP.sys   Wed Apr 06 16:08:53 2011 (4D9CC855)
ALSysIO64.sys   Sun Apr 19 15:41:04 2009 (49EB7E50)
Rt64win7.sys    Fri Jun 10 02:33:15 2011 (4DF1BAAB)
nvlddmkm.sys    Thu Jan 26 05:19:23 2012 (4F2128AB)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
MpNWMon.sys     Wed Apr 06 16:07:23 2011 (4D9CC7FB)
BVRPMPR5a64.SYS Wed Feb 21 12:56:15 2007 (45DC87BF)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021412-16703-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Feb 14 14:39:40.005 2012 (UTC - 5:00)
System Uptime: 0 days 1:11:14.521
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
BUGCHECK_STR:  0x1a_41284
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  swtor.exe
FAILURE_BUCKET_ID:  X64_0x1a_41284_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
Bugcheck code 0000001A
Arguments 00000000`00041284 00000000`19d7e001 00000000`00015152 fffff700`01080000
BiosVersion = 6.00 PG
BiosReleaseDate = 02/19/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2448
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021412-18015-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Feb 14 13:27:32.472 2012 (UTC - 5:00)
System Uptime: 5 days 0:30:54.217
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+14382 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+14382
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`000228b0 97f00001`56176025 fffffa80`099e5690
BiosVersion = 6.00 PG
BiosReleaseDate = 02/19/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2448
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

projectdwnshft · 14 Feb 2012

ok john the only things that i ever have running and that were also running when this happened twice now were SWTOR, Ventrillo, Coretemp which is running when my pc starts, and Chrome nothing new. On Thursday i got a new Netgear router but was unable to set it up via the supplied disk so I just set it up via router login. I popped the CD in that came with the router and did a search for that sys file and it came up in the search. so yes it must have stuck that file onto my pc even though i was unsuccessful in using the cd to begin with. how can i go about removing this driver?

Side note that I also just installed CPU-Z to keep an eye on my CPU clock and temps cause im still curious about the timings. After both crashes i went into the bios after researching my processor and I set it to the correct 226MHz x9 like it is suppose to be set at and have been running fine for the past two and a half hours.

usasma · 14 Feb 2012

To remove the BVRPMPR5a64.sys driver:
- create a System Restore point.
- create a System Repair disc and ensure that it works. To do this, go to Start...All Programs...Maintenance...Create a System Repair Disc
- disable any startups that name BVRPMPR5a64.SYS using Autoruns (free from here: Autoruns for Windows )
- rename BVRPMPR5a64.SYS to BVRPMPR5a64.BAD (it's probably in C:\Windows\System32\drivers)
- reboot and see if that fixes the problem(s)

projectdwnshft · 26 Feb 2012

ok so as you can see its been two weeks or so since that last BSOD. only thing changed in the system is im now running a friends gtx 560ti card to see if maybe if was a graphics card issue ive been having. its been inn here for 2 weeks with no issues. Started playing Batman Arkham City got 30mins in then the game froze up. i crashed it back to the desktop then BAM BSOD.

usasma · 26 Feb 2012

Older drivers (update if you're able; remove the program if not):

GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
Likely belongs to an older CD/DVD program (even could be iTunes). If unsure, rename driver to GEARAspiWDM.BAD and see what it breaks

ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50)
http://www.carrona.org/drivers/driver.php?id=ALSysIO64.sys
Likely belongs to Core Temp - CPU temperature monitor

xusb21.sys Thu Aug 13 18:10:17 2009 (4A848F49)
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
Likely belongs to XBox USB wireless controller

I'd run a memory diagnostic just to be sure. Free one here: Memory Diagnostics (read the details at the link)

Then I'd run Driver Verifier according to these directions: Driver Verifier Settings

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


vmbus.sys       Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys       Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
RzSynapse.sys   Wed Apr 06 05:29:13 2011 (4D9C3269)
Rt64win7.sys    Fri Jun 10 02:33:15 2011 (4DF1BAAB)
nvhda64v.sys    Thu Mar 03 10:59:02 2011 (4D6FBAC6)
cpuz135_x64.sys Tue Nov 09 08:33:36 2010 (4CD94DB0)
ALSysIO64.sys   Sun Apr 19 15:41:04 2009 (49EB7E50)
xusb21.sys      Thu Aug 13 18:10:17 2009 (4A848F49)
NisDrvWFP.sys   Wed Apr 06 16:08:53 2011 (4D9CC855)
LHidFilt.Sys    Sat Apr 30 07:51:39 2011 (4DBBF7CB)
LMouFilt.Sys    Sat Apr 30 07:51:45 2011 (4DBBF7D1)
MpNWMon.sys     Wed Apr 06 16:07:23 2011 (4D9CC7FB)
nvlddmkm.sys    Thu Jan 26 05:19:23 2012 (4F2128AB)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022612-30515-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 26 03:58:23.171 2012 (UTC - 5:00)
System Uptime: 8 days 23:42:59.918
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  BatmanAC.exe
FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
Bugcheck code 0000004E
Arguments 00000000`00000099 00000000`0003d1d2 00000000`00000002 00000000`0003d1cf
BiosVersion = 6.00 PG
BiosReleaseDate = 02/19/2008
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

projectdwnshft · 26 Feb 2012

thanks for the timely responce John. Ok I went in and updated the xbox drivers to microsoft current drivers, updated to the latest CORETemp, as for the GEARS i have never known what that was. I noticed it one day a while back and just never uninstalled it, so this time i did just that and removed it with CCleaner. Before I got to run memtest i did the driver verifier and wouldnt you know i get a blue screen, so heres the dump for that.
Oh and my apologies i totally forgot that i hooked up that xbox controller yesterday when i started playing Arkham City.

usasma · 26 Feb 2012

XBox controller drivers still date from 2009 - probably not an issue, but....
This memory dump blames USB. It could be:
- bad drivers
- bad hardware
- Windows problems

I'd tend to not blame the drivers - but they are from 2009.
Hardware can be either the XBox controller, the USB ports in your system, another USB device interfering, or other problems.

Visually inspect all of your USB ports to see if there's any damage to them.
Try using the XBox controller in a different port (preferably one that's on a different Hub) - if you have USB ports in the front of your case and in the back - it's best to switch from front to rear or rear to front.

If that doesn't lead anywhere, then remove the XBox controller and uninstall the software/drivers. Then use the system for a while to see if the BSOD's recur without it.

Don't forget to run MemTest

FYI - I'm having eye surgery tomorrow. I'll be limited in my webtime for about a week, but I will be available for limited times.