Help needed - BSOD (ntoskrnl.exe)

Test your RAM
RAM - Test with Memtest86+

Code:

BugCheck A, {58, 2, 0, fffff80003377a70}

Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+40 )

Hi, forgot to mention that i tested that system for stability already many times, but just to be sure am running memtest86+ again now, & it's just passed it's 4th errorless pass.. So i'm pretty sure it's not the ram.

rabor said:

K, starting to feel hopeless.. this morning another BSOD with another memory corruption indication..

After this BSOD I lost my dvd-drive- (Device cannot start - Code 10) & cpu turbo-boost driver (only a restore did solved these..). So because it supposed to be another memory-related error I ran another memtest, but my memory is still fine:



I also stress-tested the cpu, gpu & did the Samsung diag on my HDD, but all's fine there as well..

Tx.

Lets find out what is really causing these. Please run driver verifier

Beyond that, please run Verifier with these settings:

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


Ken J

Bump.. See previous post.

Bump..