Completely random BSODS

[mpohutsk]

Ok so, my computer has been doing some really random BSODs. I want to post my minidump files but for some reason the folder has a lock on it and I can't even compress them into a zip, let alone look at them in MSDbg. Whenever I try to open them I get an 'access denied' error.

Any tips on this? I can't seem to find any way around this when I google it and I really want to find out what's causing these.

 

[torrentg]

C:\Windows\Minidump

Compress to .rar the latest few crash dumps, upload to Rapidshare and post a link here.

Winrar should do it. If not

takeown /f command on the folder and/or file(s), with elevated command prompt.

takeown /? if you need help with that.

 

[mpohutsk]

takeown /f command on the folder and/or file(s), with elevated command prompt.

takeown /? if you need help with that.

Did that. It still won't let me open the individual files. I can see myself having permissions for the folder itself as a user, but the files within the folder do not list me as being able to access them under their individual security tabs.

 

[mpohutsk]

Nevermind. I just copied them to the desktop and was then able to access them. The 2 files with 102809 are obviously the most recent.

 

[torrentg]

It's your usbaudio.sys triggering these errors. Update your chipset drivers from motherboard manufacturer and also update the driver for any usb devices that create sound in any form...

i.e. usb audio "sound card" or usb audio interface you may be using.

nvlddmkm.sys is also problematic to your system. Update your NVidia card driver from NVidia.com to latest.

After doing those things, run a Windows Update.

 

[mpohutsk]

Ok I updated the chipset for the motherboard. The USB audio device I'm using is my headset. It also has analog options so I can try plugging it into my soundcard with just those instead of plugging it into a USB port. I have the latest nVidia drivers already installed. The most recent ones that are Windows 7 x64 compatible were on October 5th. I'll keep checking for a newer release.

 

[torrentg]

Very well. If you remember, let us know how your system is behaving after some time.

 

[mpohutsk]

Forgot to mention that the USB headset was a driverless device on its own. Is there, perhaps an updated USBAudio.sys out there? Should I also attempt to use the USB version of it since I've upgraded the chipset drivers?

 

[torrentg]

USBAudio.sys might be a generic Win 7 driver. Dunno.

If your system isn't running a cracked activation, you can run this command:

sfc /scannow from elevated command prompt. It will check on all your system files to see if they are corrupt in any way and fix it if they are.

If system is running crack, it won't be any longer after that command. If you have custom themes where you have replaced files, it will revert back to default files. Just a heads up in case.

Upgrading chipset driver was good. Use your system in whatever way you like. That's why you have it. Gotta fix it if it's still broken, heh heh.

 

[mpohutsk]

Aaaaand 2 more BSODs within 5 minutes of one another this morning. And now for some reason my computer refuses to display in anything but the lowest resolution.

 

[mpohutsk]

Still need more help with this. Here's the latest batch of minidump files. If anyone can be of assistance I would REALLY appreciate it.

 

[torrentg]

Update bios to P5Q SE2 BIOS 0601

http://usa.asus.com/product.aspx?P_ID=URA00A6u0GrUqHiH

Let us know if this fixes it.

Please consider the following as well:

"This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions."

 

[usasma]

ASACPI.SYS from 2005 is likely to cause BDOD's - especially on the P5 series of mobo's.
Please install the Asus AISuite from the download link here (under the Utilities section): ASUSTeK Computer Inc.-Support- download_item_mkt

Also, please uninstall the Riva Tuner and leave it uninstalled until the problem with your system is solved.

The dump files all blame ntoskrnl - but if that were the case there would be many other problems with your system because that file is the "kernel" of your Windows OS.
So, we've gotta look deeper in the dump files....

There's a couple of Memory Management errors - so that would suggest a memory diagnostic to me. Here's a free one: Memory Diagnostics

The errors are all over the place, but the 3rd error contains a reference to intelppm.sys in the stack text - and that's a driver for your Intel processor (but is a built in Microsoft file. Running SFC.EXE /SCANNOW from an elevated (Run as administrator) Command Prompt would be a good idea.

In short, I suspect that the ASACPI.SYS file is the culprit here, but it could easily be the other drivers that have been mentioned. If these things don't fix the error, then I'd suggest running Driver Verfier - but wait to do that until we've posted some instructions for you.

 

[mpohutsk]

Thanks for the update. While I would love to be able to try some of these things, my computer has apparently bricked. I have outstanding RMA offers on my video card, RAM, and CPU but let me back up a bit.

Yesterday I tried to turn it on and it wouldn't (this was after I just shut it off after a BSOD the previous night). There was no sound, no light, no nothing. I'd press the power button and nothing happened. I assumed it was probably the PSU since it was the only component in my machine that hadn't been replaced since I originally built it (Summer '04) and at 420W, wasn't exactly designed to work efficiently with most of the parts in my machine. I went out and bought a 650W one, and began the installation process.

Halfway through, I noticed the heatsink/fan on my CPU (the stock one that came from my E8400) wasn't properly seated and was loose on the side closest to the top of the chassis. Noting the fact that a previous reply here said the error could be temperature related, and knowing that this CPU has had a tendency to run quite hot since I originally bought it, I figured that the CPU had failed. To be perfectly honest, I'm not even sure how long the heatsink had been seated like that. For all I know it could have been like that from the day I installed it. I had read on other forums that the E8400s had a tendency to run hot so I just assumed that it was an issue with the stock cooler.

I had called Intel a few days prior and they offered to RMA it if I applied some more thermal paste and it was still running hot. Obviously, I didn't do so, but I'm going to say that I did, and forget to mention the not properly mounted thing. The reason I believe it's the CPU is that the motherboard IS getting power because the indicator LED is lighting up. If it wasn't the PSU, big deal, it needed to be replaced anyway, and now at least if it wasn't I have a spare.

Edit: Forgot to mention that after installing the new PSU, the system, obviously, still would not turn on. I've gone through massive amounts of troubleshooting and tried every step imaginable, but it still won't turn on, that's why I've narrowed it down to the CPU.

 

[torrentg]

Going by all clues following your post, I agree. Most likely cpu damage. Good luck on the RMA with that. Let us know how it goes once you receive a replacement.