BSOD & SWTOR (Dump Inside)

uGuru is back. Please remove it again.

Not Available ACPI\ABT2005\3&2411E6FE&2 The drivers for this device are not installed.

Click to expand...

Please note that the drivers aren't installed, so search Device Manager and your registry for instances of it.

Only 65 updates after SP1 - most systems have 70 or more. Please visit Windows Update and get all available updates.

You have both Logitech Setpoint and Microsoft Intellipoint installed - please remove one.

Do you have the program "Can You Run It" installed on your system? If so, please uninstall it. The cpudrv64.sys dates from 2009 and should be removed from your system.

The Driver Verifier enabled memory dump points to a Windows file. As such we have to suspect either Windows or a hardware problem. Don't add anything else to the system until you isolate the problem. Your choice - work on isolating hardware - or reinstalling Windows "clean"

Isolate hardware: http://www.sevenforums.com/crashes-debugging/212708-bsod-swtor-dump-inside-4.html#post1833761

Clean install of Windows (I think you did this already): http://www.sevenforums.com/crashes-debugging/212708-bsod-swtor-dump-inside-5.html#post1835619


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
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=MpNWMon.sys
http://www.carrona.org/drivers/driver.php?id=cpudrv64.sys

BSOD BUGCHECK SUMMARY

i had to install uguru to get rid of the UNKNOWN DEVICE in device manager, then i uninstalled it. after all this shit going on for over 2 months now im picking up a new mobo today, from ASUS that has better support than this non supported universal abit,and going to start the whole pc over from scratch, i hope i don't end up coming back to this thread but with my luck i just may.

also i have every single update windows can possibly get other than the IE stuff cause i dont want to nor will i use/update IE

Good luck!

Hey there john, this isn't a BSOD problem but im concerned it may become one. When i decided to reload windows onto the system came across severely long load times while trying to install windows 7. I initially tried installing via USB stick which normally takes 12mins but ended up taking hours and it didnt even finish. tried installing again with various disc copies of 7 and they to loaded extermely slow between setup screens. this had my friends and i thinking when i was having you troubleshoot my bsod's i remembered that allot of the bsod's gave a NTFS.SYS error. two of my computer tech friends said windows loading extermely slow may be because the hdd is riddled with bad sectors. i told them you had me test every component of the computer and everything passed but they insisted that there is either hdd issues or ram. i had my friend take the computer to his house and have him try loading 7 onto it, he called me after a few hours and said come pick up your machine its good to go. he managed to get a copy of his 7 to load onto the machine and did the first 20-30 updates before giving it back to me. i had it back at my house for no more than 45mins when i got the first BSOD while trying to download and install SP1. the error came up as NTFS.SYS. i rebooted tried installing it again and it would get partially through then BSOD again. it eventually took me 4 hours to get sp1 installed on the system after many BSOD. heres where i figured my HDD may be bad. the computer would only bsod when i was trying to write to it. I would start installing drivers and such and bam blue screens. I got fed up and my friends suggested i try another HDD and some ram if i have any available.

so i managed to find a WD green drive i forgot i had that was brand new unopened in box and i had 2 1gig sticks of gskill ram sitting around and dicided to put just those 2 gigs and the harddrive in the machine and try loading windows on it. to my surprise windows loaded and installed off the usb stick in 12-13 minutes. this install was preloaded with SP1 so i didnt have to worry about going through that headache again and just updated everything as usual. after 2 days went by with no issues on 2 gigs of ram and this green hdd i decided to RMA my Velociraptor drive and my 8 gigs of corsair ram. I also tracked down a new mobo from a local computer shop and picked up an Asus P5N-D board to replace this god awful Abit board which seems is not supported anymore because i am unable to even load up Universal Abit's website anymore. I figured the mobo purchase would be a wise investment for the time being. so i installed the new board, with still only 2 gigs of ram and that green drive and everything works fine. decided to throw in 4 more gigs to see if the old ram was stable or not while i waited for the rma ram to come in. computer has been running fine, got the new raptor drive and i installed it reloaded windows yet again, loaded all the drivers that came with the board and for my other components and everything seems good. at this point i still dont have the new ram but the old stuff has been working fine but yesterday while playing swtor the system hung up on me, didnt get to bsod just locked up in the middle of playing and i had to hard reboot. when i loaded back in i immediately went to event viewer to see wtf had happened. and i notice event viewer is riddled with this WARNING nvstor Event ID 8, did some researching and found lots of people with this problem and one guy said he fixed it by uninstalling the nforce drivers and using windows preloaded drivers instead. so i did that and all seemed well, but then i wake up this morning and at 1:28 in the morning it through a nvstor event ID 129. it only did this once but id like to completely solve this problem. when i looked up that event it says it has to do with raid but i do not have the system setup in a raid config.

i would appreciate it if you could help me fix this issue cause im not sure what it is or whats causing it. let me know if there are any reports you need as ill get them to you asap for you to analyse.

thanks

*edit*
I have just downloaded the latest nforce drivers andn am going to install them and see if i have any issues in the event viewer, just wanted you to know

I'll post more later, I'm headed out now.
But first a quick story.

I had a Toshiba laptop at work today that was giving NT_STATUS c00000e9 errors today (I/O error)
The system had the hard drive replaced and we weren't able to install Windows (in our case, it would error at different points).

I futzed around with it for a couple of hours, taking it apart and putting it together. The only thing I noticed was that the DVD drive didn't seem fully seated. So I firmly seated it and then proceeded to install Windows without a problem.

The point here is to check all connections. Take them apart and make sure that they're clean.

Good luck, I'll write more when I get back.

Latest nForce drivers are recommended. Download them from the nVidia site - not from Asus
Issues with storage drivers can mean:
- storage driver problems
- storage controller problems (this is hardware that's attached to the mobo)
- cable problems
- power problems
- hard drive problems
- file system problems
- or even memory problems

Here's some info about the P5 series of mobos:

FWIW - I've seen a lot of issues with the Asus P5 series of boards. I usually recommend this:
- DO NOT use the AUTO setting for memory. Go to the RAM manufacturer's website and get the recommended settings for the RAM. Then set those settings manually in the BIOS
- one person with a 2009 BIOS has experienced success by updating the BIOS. This is dangerous and one simple mistake can easily damage your motherboard so it won't work. Be VERY, VERY CAREFUL!!!
- one person reports bad caps ( Badcaps.net - How To Identify ) in this post: [SOLVED] Bad overclock and now can't load windows 7 - Tech Support Forum

Click to expand...

ive already installed the latest drivers and they didnt solve anything, just a nvstor64 event id 8 warning getting thrown up in the event viewer:
A request to this device has been cancelled.

Device: \Device\RaidPort1
Model: WDC WD6401AALS-00E3A0
Firmware Version: 05.0
Serial Number: WD-WCATR4105223
Port: 0

i noticed this is my 640gig wd black drive and it only comes up as being 596GB drive when looking at it from my computer.

Please zip up and post another copy of the jcgriff2 reports (even though you're not having BSOD's) and we'll see what we can find.

alrighty so, last night i got your last message about checking cables....so i did just that and noticed all 3 sata cables were extremely loose. so i replaced them with brand new ones that locked in real good and that warning seemed to disappear. but now i got 1 error which says volsnap event id 10 :The shadow copy of volume E: took too long to install. i have no clue what that is or means but it only came up once so im assuming there is no need to worry. i have attached a full dump for u to check out as requested

i also adjusted my memory timings accordingly as you requested even though i wasn't experiencing any issues with that.

Don't worry about single errors in Event Viewer. Windows' error correcting mechanism is pretty effective.
In this case it isn't even your OS drive (it's your E: drive)

Looks like your drivers are very, very outdated. If you installed drivers from the CD that came with the mobo - please don't do this in the future. The most current drivers are from the device manufacturer's website.

If you're unable to find them at the device manufacturer's website, then use the mobo manufacturer's website.

You can obtain the most up to date chipset drivers from here: NVIDIA DRIVERS 15.57 WHQL It's release date is 2011.

Then let's see what happens.....