Randomly occuring "Memory Management" BSODs?

[PelleK63]

Hi,

Built me a new PC a couple of months ago with the general specs below;
OS; Windows 7 Home Premium x64
Motherboard; Asus P8Z77-V Pro
CPU; Intel Core i7-3770K CPU @ 3.50GHz
Memory; 2x 8GB Corsair XMS3 DDR3 PC12800/1600MHz CL11
Graphics card; Asus GeForce GTX 660 DirectCU II
Hard drives; 2 SSDs, 1 INTEL 60GB for the OS and another INTEL 160GB for other applications

I've been getting randomly occuring BSODs however, always with the cause "Memory Management". As for the timings of the BSODs, I've failed to discern any pattern. As far as I know, I've updated all drivers to the latest version.

I would appreciate any help and/or pointers as to the root of the problem. Packed SF Diag Tool attached.

Thanks,
PelleK63, Sweden

 

[VistaKing]

PelleK63


Test your memory . Look at the link below

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

   Tip

Take a look at Part 3 if any errors come up

 

[PelleK63]

PelleK63


Test your memory . Look at the link below

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

   Tip

Take a look at Part 3 if any errors come up

Ok.

I have run a stress test on the memory before (calculating prime numbers with prime95.exe) which came up with no errors. I will however run the memtest overnight later when I go to bed just to be sure.

Later.

 

[PelleK63]

Ran the memtest as requested for seven passes and close to 17 hours. No errors.

Guess that means the BSODs are software related then?

 

[VistaKing]

PelleK63,

I have asked x BlueRobot to take a look at your dmp files

 

[PelleK63]

Ok and thank you for your prompt replies

 

[VistaKing]

You're welcome .

 

[x BlueRobot]

Welcome to the forums PelleK63,

I'm just having a look now, I'll post the results in a few minutes.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41790[/COLOR], fffffa80052c82d0, ffff, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1d4cfc )

Usual causes:  Device driver, memory, kernel

This indicates that a severe memory management error has occurred, the first parameter (highlighted in blue) indicates that a page table page has become corrupt. The page table is used to store mappings between virtual and physical memory.

Remove:

Start Menu\Programs\Norton Internet Security
Start Menu\Programs\Norton

Norton is known to cause BSODs with Windows 7, please remove this program using the Norton Removal Tool, and then install and run full scans with these alternative products which have proven to work best with Windows 7, due to their lightweight nature on system resources and compatibility with the operating system.

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[PelleK63]

Ok.

Thanks you for both the welcome and the quick reply!

Funny ... I had a hunch that NIS could be the culprit, as that is about the only driver/program I haven't been able to verify that it isn't the problem.

Will do as you said and come back in ~two weeks if I have become free of the BSODs. If I'm not, I'll get back earlier

Thanks for your support

Regards, PelleK63

 

[x BlueRobot]

Welcome, I'm working on a thread which has problems caused by Norton at the moment so seems pretty common today

 

[PelleK63]

Hello again,

I followed the advice in the post below, but I'm afraid that the BSODs have not gone away as I've had two of them over the weekend. A more complete list of what I've done since the last post follows further down.

I've run the SF diagnostic tool again. Strange thing is that, unlike the earlier BSODs where I got the blue screen and the PC restarted automatically (with a dump file created), the PC now stops at the blue screen and does not restart. I've had to reset the comp to get it to reboot, and then it apparentely hasn't created a dump file? See also appended picture of the screen. I waited for half an hour before resetting.

What I did after the post below was;
1/ I removed the NIS with the Norton Removal Tool
2/ I installed the lightweight protection as suggested in your thread http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html
3/ I switched on the driver verifier as suggested in http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html and ran it for 24+ hours without problems.

Guess it's some other problem ... but the question remains what?

Help, please?

Regards, PelleK63, Sweden

[COLOR=red]BugCheck 1A[/COLOR], {[COLOR=blue]41790[/COLOR], fffffa80052c82d0, ffff, 0}
 
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1d4cfc )

Usual causes:  Device driver, memory, kernel

This indicates that a severe memory management error has occurred, the first parameter (highlighted in blue) indicates that a page table page has become corrupt. The page table is used to store mappings between virtual and physical memory.

Remove:

Start Menu\Programs\Norton Internet Security
Start Menu\Programs\Norton

Norton is known to cause BSODs with Windows 7, please remove this program using the Norton Removal Tool, and then install and run full scans with these alternative products which have proven to work best with Windows 7, due to their lightweight nature on system resources and compatibility with the operating system.


Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

   Information

Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[VistaKing]

Looking at the picture that BSOD is a memory issue . Test your memory

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

 

[PelleK63]

Looking at the picture that BSOD is a memory issue . Test your memory

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

Already did that (see post http://www.sevenforums.com/bsod-hel...ring-memory-management-bsods.html#post2439881). Seven passes and 17 hours with no errors.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {[COLOR="Blue"]41790[/COLOR], fffffa80052c82d0, ffff, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1d4cfc )

Okay, it seems to be more a hardware related issue now, most likely the hard-drive.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[PelleK63]

Ok, will do.

Thanks for the help

// PelleK63

 

[x BlueRobot]

Welcome, feel free to post back if you have any questions or need any help

 

[PelleK63]

Ok, all these HD tests took some time, but I've now;

1/ Run the manufacturer HD diagnostics for all drives. One SSD Firmware updated. No errors as shown in the appended picture
2/ Run the CrystalDiskInfo. No errors. Picture of the results attached.
3/ Scheduled and ran the chkdsk. No errors.
4/ Ran SFC /SCANNOW. According to the log file there were some faulty files. CBS Log attached.

In other words, it doesn't look that the error causing the BSODs is hardware related?

Observation; As I said in the last error report, I had two quick consecutive BSODs over the weekend of which none (unfortunately) produced any crash log. When I started this HD testing, I finally remembered to switch of the driver verifier (from the previous testing), after which I haven't had ant crash even though the PC has been running the HD tests almost 24/7. Could it be a driver issue?

[COLOR=red]BugCheck 1A[/COLOR], {[COLOR=blue]41790[/COLOR], fffffa80052c82d0, ffff, 0}
 
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1d4cfc )

Okay, it seems to be more a hardware related issue now, most likely the hard-drive.



Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.



Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[x BlueRobot]

Try running the same command three times with reboots in between, sometimes the command will need to run three separate times in order to repair any files.

If no files can be repaired by Windows itself, then I'll get someone to check your CBS.log.

If there were any driver related errors, then Driver Verifier would have created a BSOD.

 

[PelleK63]

Oh, the errors found with SFC /SCANNOW were repaired on the first run/reboot. I just ran the test a second time and there were no errors found.

Clarification concerning driver verifier - it could very well be that it was driver verifier that induced the last two BSODs. Problem is just that the PC never continued with a reboot from those BSODs. I had to physically reset the PC and then there were never any dump files created? Not any that the SF Diag tool found anyway.