Multiple BSODs, Several times per day.

Status
Not open for further replies.

NewJerky

Distinguished
Dec 29, 2011
7
0
18,510
Hello, I am an amateur computer builder who has had this homebuilt PC for about 2 years now. Recently, I got Skyrim and was having major problems with it. Those are not necessarily fixed but now I am having general problems.

My computer Bluescreens whenever I am watching online videos, listening to music via spotify, or sometimes just using the internet in general. It is a gaming system so sometimes they happen then. Every blue screen happens for a different reason. Here are a couple.

System Service Exception
Reference by Pointer
Page Fault in Nonpaged Area
Bad Pool Header/Caller
IRQL Not Less or Equal

In addition, certain files have been mentioned:
dgmms1.sys
usbport.sys
npfs.sys

These stop codes appear:
0x0A
0x03B
0x0C2
0x024
0x018
0x01E

I have heard of drivers being mentioned, or hardware. Not sure. Here are my system specs.

Windows 7 64 Bit
Radeon HD 4850 1Gb
4Gb OCZ Gold RAM
ASUS M4A75TD Motherboard
Seagate 750GB Hard Drive
Direct X 11
AMD Phenom II X3 2.8GHz

Can anyone help? I cant keep my computer on for an entire day before it bluescreens doing mundane tasks.

 
Solution
Look at your memory. Run memtest 86 . Down the page a bit is a download link for a burnable and bootable iso link. Get this one. It will keep windows from preventing memtest to test the memory it occupies. You will want to run memtest multiple times. Some say 2 or 3 others say up to 13. If you have multiple sticks of ram, test them one at a time on one or 2 passes each. Since none of the software based memory test is foolproof, even if all ram comes back as tested ok, I would run windows one stick at a time for a day, if you have 2 sticks. If you have 4 sticks, pull out one and run windows for a day. Next day, rotate the ram and pull out a different stick and reinsert the first one pulled out.

Another thing that has helped others...
Are you running the most up to date video card drivers? That sounds to me like possibly memory issues in your video card. Did you perhaps try rolling back your video card drivers to an older version and see if the problem still occurs?

Also make sure you have the latest windows updates, I've seen those solve peoples problems before.
 
Look at your memory. Run memtest 86 . Down the page a bit is a download link for a burnable and bootable iso link. Get this one. It will keep windows from preventing memtest to test the memory it occupies. You will want to run memtest multiple times. Some say 2 or 3 others say up to 13. If you have multiple sticks of ram, test them one at a time on one or 2 passes each. Since none of the software based memory test is foolproof, even if all ram comes back as tested ok, I would run windows one stick at a time for a day, if you have 2 sticks. If you have 4 sticks, pull out one and run windows for a day. Next day, rotate the ram and pull out a different stick and reinsert the first one pulled out.

Another thing that has helped others in the past is to simply rearrange the ram sticks into different slots.

Check other cables within the computer. Sata cables etc.
 
Solution
It's not really generally speaking to be able to install ram in the wrong slot. Different factors are built in to prevent this. Like Gamer said, test them individually. There is a bootable version of memtest86 available here burn a cd or usb flash drive. Boot to it and then test. Windows will try to protect areas of ram in which it resides. Memtest86 will not do this. I assume relocate itself to an area of ram that has already been tested and found ok.

I built a computer last April. By August a 4 gig stick was buggy. Pulled that stick out and no problems since.
 
nirsoft have a dump file reader, also look at whocrashed both will look at dump files and help you to help us.

whocrashed did point the finger at a driver that was not even released at the time of the crash for me so its interpretations might be suspect, it could be using todays driver details to interpret past crashes however, which in normal usage of interpreting very recent crashes is not important.
 
^^ Whocrashed simply points to the driver that actually caused the problem. But if the memory is faulty, any other number of programs could have been the one that did the damage.

I'll say again: IRQL BSOD's are almost always memory. Bad Pool and Page Fault BSODs are certainly memory realated. I'm pointing squarely at RAM. Test each stick one at a time with memtest.
 
Status
Not open for further replies.