Win7 x64- Multiple startup BSODs (1, reboot, then another, reboot...)

This is quite possibly the strangest error sequence I've come across in all my years working with computers.

My system has issues. Unfortunately. Possibly more than one. But I do know that for about the last month, up until this morning, any attempt to turn on my system would require the user to boot into Windows, wait ~15 seconds for a hard, BSOD-inducing crash (with MEMORY_MANAGEMENT as the cause a majority of the time), wait for the system to reboot and reach the Windows boot animation, suffer yet another hard, BSOD-inducing crash (with no minidump this time, however, since it hadn't fully loaded Windows yet), and then finally reboot once more, after which the system would seem to function perfectly. My one change this morning? I removed one stick of my RAM.

Now, normally this would seem to be pretty cut and dried, but I had similar problems with this setup earlier in the year. I exchanged my RAM twice, then my motherboard, then my RAM again, which is leading me to believe that it might well be a CPU issue (note that my system is not currently being overclocked). But my Windbg skills aren't what they used to be, and I'm currently running on a spotty 3G internet connection, so my options for diagnosis are a tad limited.

Current system specifics:
i3-530 (stock)
2x2GB OCZ PC3 12800 (OCZ3OB1600LV4GK) Obsidian Series
Gigabyte P55-UD3L
Radeon HD 4850 512MB

Thoughts, O gurus of 7?

Minidump archive is attached.

adg1034 said:

This is quite possibly the strangest error sequence I've come across in all my years working with computers.

My system has issues. Unfortunately. Possibly more than one. But I do know that for about the last month, up until this morning, any attempt to turn on my system would require the user to boot into Windows, wait ~15 seconds for a hard, BSOD-inducing crash (with MEMORY_MANAGEMENT as the cause a majority of the time), wait for the system to reboot and reach the Windows boot animation, suffer yet another hard, BSOD-inducing crash (with no minidump this time, however, since it hadn't fully loaded Windows yet), and then finally reboot once more, after which the system would seem to function perfectly. My one change this morning? I removed one stick of my RAM.

Now, normally this would seem to be pretty cut and dried, but I had similar problems with this setup earlier in the year. I exchanged my RAM twice, then my motherboard, then my RAM again, which is leading me to believe that it might well be a CPU issue (note that my system is not currently being overclocked). But my Windbg skills aren't what they used to be, and I'm currently running on a spotty 3G internet connection, so my options for diagnosis are a tad limited.

Current system specifics:
i3-530 (stock)
2x2GB OCZ PC3 12800 (OCZ3OB1600LV4GK) Obsidian Series
Gigabyte P55-UD3L
Radeon HD 4850 512MB

Thoughts, O gurus of 7?

Minidump archive is attached.

No DMPS included

try this way

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the appropriate section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Gah. I /swear/ I uploaded them.

Let's try this again.

Disable Ready Boost if you are using it

One BSOD was caused by cmudaxp.sys, this is an old XP driver which needs to be updated
Driver update

This was likely caused by the following module: rdyboost.sys
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFF7E, 0x2, 0x0, 0xFFFFF88001BA47BB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

This was likely caused by the following module: cmudaxp.sys
Bugcheck code: 0xD1 (0xFFFFF88004440D50, 0x5, 0x8, 0xFFFFF88004440D50)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

adg1034 said:

Gah. I /swear/ I uploaded them.

Let's try this again.

Bugchecks: 0a (19), 24 (5), 3b (7), and eight more.

0a--Since this is the most frequent Lets look at it first.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

This is basically a driver corrupting memory or the memory itself.

I would
1-run memtest
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.

2-Update old drivers


old drivers needing update

Code:

                       
pnetmdm64.sys        fffff880`044a0000    fffff880`044a9000    0x00009000    0x45ef00bf    3/7/2007 14:13:19                        
jswpslwfx.sys        fffff880`02f2f000    fffff880`02f3c000    0x0000d000    0x482c1062    5/15/2008 06:28:50                        
GizmoDrv.SYS        fffff880`02e00000    fffff880`02e0b000    0x0000b000    0x482fbd72    5/18/2008 01:24:02                        
000.fcl        fffff880`02800000    fffff880`0282b000    0x0002b000    0x48dcdf7a    9/26/2008 09:11:22                        
cpuz132_x64.sys        fffff880`0489e000    fffff880`048a6000    0x00008000    0x49cc0d03    3/26/2009 19:17:23                        
spldr.sys        fffff880`01ba7000    fffff880`01baf000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`045f2000    fffff880`045ff000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`011ea000    fffff880`011f5000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
iaStor.sys        fffff880`010c5000    fffff880`011e1000    0x0011c000    0x4a287aa4    6/4/2009 21:53:40                        
MpFilter.sys        fffff880`013b1000    fffff880`013dd000    0x0002c000    0x4a306cf1    6/10/2009 22:33:21                        
MpNWMon.sys        fffff880`07713000    fffff880`07723000    0x00010000    0x4a306cf3    6/10/2009 22:33:23

3-Run driver verifier to find which driver is causing them
Beyond that, please run Verifier with these settings:
[quote]
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 "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

Let us know if you need help with any of these,


Ken J