BSOD(old solution not working)

[interdpth]

I keep getting a BSOD Page Fault in Unpaged Area i'm running Windows 7 Pro, I think it may be sound driver related, because i'm always playing a song, when it blue screens, I got the actuall drivers, this fixed the problem before when I was running the RC, but it's not working right now, and as per the google searches I did run the memtest and my ram passed the tests

The drivers i'm concerned with are the realtek drivers, I used the executable hoping it'd get installed correctly.

Any advice?

 

[Jacee]

System Manufacturer/Model Number Compaq
OS Windows 7
CPU AMD Athlon 64 3800+
Motherboard Some Nvidia thing
Memory 2 gigs of Ram
Graphics Card Nvidia 8600 GT
Sound Card not sure
Monitor(s) Displays 1

We need more info than that.
Windows7 pro .... RC?
Motherboard Some Nvidia thing ... <--Use Belarc Advisor to find out
Sound Card not sure... <--Belarc Advisor, again will tell you your system specs.

Belarc Advisor - Free Personal PC Audit

 

[interdpth]

Direct copy and paste of the belarc thing does not look good xD

Multimedia: Realtek High Definition Audio

Main Circuit Board:
Board: ECS Iris 1.0
Bus Clock: 201 megahertz
BIOS: Phoenix Technologies, LTD 5.09 05/03/2007

Let me know anything else you need

 

[usasma]

Exact model number of the Compaq?
Please navigate to C:\Windows\Minidump, zip up the contents of that folder, then upload/attach the .zip file with your next post.

 

[interdpth]

it's a SR5110nx
attached the minidump

 

[H2SO4]

it's a SR5110nx
attached the minidump

No obvious involvement from sound drivers in any of these crashes. In fact, they're very diverse: some win32k.sys rendering faults, some memory manager structures broken... even a volsnap initialisation breakdown.

Updating the NIC/sound/video/anti-malware/other drivers is always a good start in these situations.

If that doesn't help, you can get the OS to keep tabs on what the drivers are doing, in the hope of exposing problems in their actions immediately instead of afterwards when it's too late to pinpoint the exact culprit. To enable that extra scrutiny, run VERIFIER /ALL from an elevated (run as admin) command prompt. The next dump after that may contain more specific info. When done with your investigation, disable verifier by running VERIFIER /RESET. You certainly don't want your machine running that way forever.

Lastly, if the machine is over-clocked or under-cooled, that can cause almost any crash pattern imaginable. There's a possibility that your many and varied crashes are caused by a hardware-layer fault.