Multi-BSOD (Mainly "Modification of system code detected")

[SacredSkull]

• Windows 7 x64

• I have installed a number of times due to OS corruption from the ridiculous amount of BSODing
• Retail Version of Win7
• PC is almost 1 year - at least 7 months
• Running on this installation for around 3 months

Since this re-install, and a motherboard replacement, computer is slightly more stable.


For some time I have believed its the dodgy Generic PSU and am awaiting it arriving in the post. Will update accordingly.


Thanks As a programmer, I can see that quite an amount went into that information collection tool, and I am also impressed at the entire community working on other peoples dumps to help them, there is a ton of information to shift through in that collection tool!



Specs are at bottom of sig area:


|

\|/
*

 

[zigzag3143]

These crashes were caused by memory corruption/exception (possibly audiodg.sys).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

 

[SacredSkull]

I'm almost certain that is not a RAM problem. About a month ago I replaced the RAM, and as said, the frequency of the BSODs was less.

Before I replaced the mobo and RAM I was getting IRQL errors, BAD_POOL_HEADER, etc.

And no, I'm not using RAID.

Haven't tried Driver Verifier on this install, but on the last one, it didn't report anything, save the Peerblock driver, which automatically BSODs:

Windows Crash / BSOD - This is most commonly caused by people running with Driver Verifier turned on. This tool will intentionally crash your system if it detects a driver doing anything even potentially incorrect, and is primarily meant for driver developers. Workaround: You can check your Driver Verifier settings by doing Start -> Run -> verifier.exe. Driver Verifier should either be completely disabled, or at least not be monitoring PeerBlock's pbfilter.sys driver.

From KNOWN ISSUES . . . plus solutions to common problems

For now I'll redo Driver Verifier, see if that shows anything, then if needs be use memtest.

Thanks

 

[SacredSkull]

Wierd. I just disabled PeerBlock, as in renaming the program file dir (so it wouldn't load the driver) and I have absolutely NO BSODs. I would seriously like to have PeerBlock on this computer, so I am going to try either Peerblock Beta/Current Release to see if this changes anything.

Will update accordingly.