BSOD IRQ then MEMORY MANAGEMENT

I had two BSODs yesterday and I'm at a loss to understand them. I've always operated under the theory that one could be a fluke, two is a problem.

The first happened while I was away from the computer. I was running Handbrake, and was encoding some video files to MP4. It gave an IRQ LESS THAN type BSOD. Later that evening I was trying to transfer some files to my NAS. It was transferring at a unusually slow rate, so I cancled the transfer, closed all my programs then tried to restart my system. I got a BSOD Memory Management BSOD. Up until yesterday, I hadn't any problems that I'm aware of.

Ran SeaTools for Windows to check SeaGate hard-drive. No errors. I ran Memtest86+ from bootup CD for 9.5 hours, 11 passes, no errors.

There's only one thing that does concern me. First there seems to be a Bluetooth compatibility problem with the Logitech keyboard. This keeps coming up. But if I download and install the Broadcom bluetooth driver/software it disables my Logitech keyboard. Then I have uninstall it and use Logitechs Setpoint software anyways.

System Specs
Shuttle SX48P2E
Intel Core 2 Duo E8500 @ 3.16
Corsair2X1024-6400 (2 pairs total 4GB)
EVGA/NVIDIA GeForce 8800 GTS
LG Black 12X BD-R 2X BD-RE 16X DVD+R 12X DVD-RAM 10X BD-ROM 4MB Cache SATA Super Multi WH12LS30
Seagate ST3640323AS 640GB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal Hard Drive (Primary)
Western Digital Caviar SE16 320GB 7200 RPM 16MB Cache SATA 3.0 (Second drive)
Logitech Bluetooth MX5000 keyboard + Mouse Combo
Dell 2405 monitor
Onboard audio using Realtec codecs
Windows 7 Ultimate x64bit sp1 (full retail upgrade edition)
Norton Security Suite (Norton 360)
Elby CloneDrive driver (AnyDVD) (vitual mounting drive)

Just an FYI. While Norton was not directly blamed it is a major cause of BSOD's. Just to test I would remove it and replace with Microsoft Security Essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

Thanks. What was directly blamed?

agogley said:

Thanks. What was directly blamed?

An OS file that cant possibly be the cause. Just to check you can run system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

I ran it and received the following message at completion:

"Windows Resource Protection did not find any integrity violations."

I received another couple suggestions from a friend. He recommended running Verifier and checking my memory sticks with Memtest, 1 stick at a time for 1-2 passes. I'm a little hesitant to run Verifier though.

As an aside, I haven't had any BSODs since those two I posted. I've put my computer through pretty intensive encoding and nothing. I'm starting to suspect that my virtual mounting software (driver reads Elby SCSI or something like that) or Power DVD since those are the only two pieces of software I haven't used since having my BSOD.

agogley said:

I received another couple suggestions from a friend. He recommended running Verifier and checking my memory sticks with Memtest, 1 stick at a time for 1-2 passes. I'm a little hesitant to run Verifier though.

As an aside, I haven't had any BSODs since those two I posted. I've put my computer through pretty intensive encoding and nothing. I'm starting to suspect that my virtual mounting software (driver reads Elby SCSI or something like that) or Power DVD since those are the only two pieces of software I haven't used since having my BSOD.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

I already have a Memtest86+ bootable CD. I ran it originally but with all four sticks present. I left it for 9.5 hours with 11 passes and nothing. Is there some benefit to running it on one stick of RAM at a time (other than identifying the culprit after an error is detected?)

agogley said:

I already have a Memtest86+ bootable CD. I ran it originally but with all four sticks present. I left it for 9.5 hours with 11 passes and nothing. Is there some benefit to running it on one stick of RAM at a time (other than identifying the culprit after an error is detected?)

Often using a single stick at a time will identify if it is the ram or mobo slot, beyond that if not much benefit to running it a stic kat a time. Occasionally an error will kick off in single stick mode that didnt show in multi-stick.

That's what I thought. So pretty much we're back to verifier.