Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: Randomly occuring "Memory Management" BSODs?

19 Jun 2013   #11

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

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

My System SpecsSystem Spec
.

23 Jun 2013   #12

Windows 7 Home Premium x64
 
 

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



Quote   Quote: Originally Posted by x BlueRobot View Post
Code:
BugCheck 1A, {41790, 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 )
Code:
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:

Code:
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:
information   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: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:
information   Information
My System SpecsSystem Spec
23 Jun 2013   #13

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

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

RAM - Test with Memtest86+
My System SpecsSystem Spec
.


23 Jun 2013   #14

Windows 7 Home Premium x64
 
 

Quote   Quote: Originally Posted by VistaKing View Post
Looking at the picture that BSOD is a memory issue . Test your memory

RAM - Test with Memtest86+
Already did that (see post Randomly occuring "Memory Management" BSODs?). Seven passes and 17 hours with no errors.
My System SpecsSystem Spec
23 Jun 2013   #15

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Code:
BugCheck 1A, {41790, 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:Find your hard-drive manufacturer and run their tests.

Additional Tests:Post a screenshot of Crystal Disk Info summary:
Quote   Quote: Originally Posted by writhziden
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:Use this command with Disk Check:

Code:
chkdsk C: /f /r
Scan for any missing, modified or corrupted protected Windows files with:
My System SpecsSystem Spec
23 Jun 2013   #16

Windows 7 Home Premium x64
 
 

Ok, will do.

Thanks for the help :-)

// PelleK63
My System SpecsSystem Spec
23 Jun 2013   #17

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Welcome, feel free to post back if you have any questions or need any help
My System SpecsSystem Spec
25 Jun 2013   #18

Windows 7 Home Premium x64
 
 

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?

Quote   Quote: Originally Posted by x BlueRobot View Post
Code:
BugCheck 1A, {41790, 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:Find your hard-drive manufacturer and run their tests.



Additional Tests:Post a screenshot of Crystal Disk Info summary:
Quote   Quote: Originally Posted by writhziden
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:Use this command with Disk Check:

Code:
chkdsk C: /f /r


Scan for any missing, modified or corrupted protected Windows files with:
My System SpecsSystem Spec
25 Jun 2013   #19

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

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.
My System SpecsSystem Spec
25 Jun 2013   #20

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
Reply

 Randomly occuring "Memory Management" BSODs?





Thread Tools



Similar help and support threads for2: Randomly occuring "Memory Management" BSODs?
Thread Forum
Recently having this BSOD called "Memory Management" BSOD Help and Support
BSOD Randomly Occuring MEMORY MANAGEMENT BSOD Help and Support
Random BSODS (mostly "memory management"), often on startup BSOD Help and Support
Solved BSODs occuring randomly and increasingly more frequent. BSOD Help and Support
Random "Bad Pool Header" and "System Service Exception" BSODs BSOD Help and Support
Randomly occuring 7f BSoDs BSOD Help and Support
"Random" sproadic BSODs - Memory or video? BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:52 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33