Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Windows 7 64bit


  • Please log in to reply
4 replies to this topic

#1 mkillinger

mkillinger

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:51 AM

Posted 10 August 2016 - 11:59 AM

Home made computer prelim mini dump through Blue Screen View based on another article it is pointing to bad Ram see mini dump and article to validate my next steps? But I see in another thread on here that voltage could be issue, if that were tru it should have started over 2.5 weeks ago as WOW and World of tanks were both being played, have a fan on cpu, two exhaust fan on top and fan for psu.

 

 

bugcheck 0x0000001a means MEMORY_MANAGEMENT. The important information come from the parameter 1.

0x41790 means this:

A page table page has been corrupted. On a 64 bit version of Windows, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit version of Windows, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs.

According to Microsoft, this is mostly caused by RAM (Hardware) issues:

The 41790 code is part of our an internal memory manager code but the bugcheck in my experience has almost always indicated hardware issues (RAM errors).

So, run a memory test tool (memtest86+ or the internal Windows tool). Also check the RAM timings with CPU-Z and look that the values from the SPD tab match to the data in the memory tab. If you have a command rate (CR) of 1, go to the BIOS and set it to 2. This can also trigger such BSODs

 

==================================================
Dump File         : 080816-8127-01.dmp
Crash Time        : 8/8/2016 10:07:29 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`00162a15
Parameter 3       : 00000000`00000002
Parameter 4       : 00000000`00163994
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\080816-8127-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 384,360
Dump File Time    : 8/8/2016 10:09:25 PM
==================================================

==================================================
Dump File         : 080816-6396-01.dmp
Crash Time        : 8/8/2016 8:05:08 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`058d2680
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\080816-6396-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 344,000
Dump File Time    : 8/8/2016 8:05:58 PM
==================================================

==================================================
Dump File         : 080816-5990-01.dmp
Crash Time        : 8/8/2016 7:57:37 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`0006ac43
Parameter 3       : 00000000`00000001
Parameter 4       : 00000000`0006aec3
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\080816-5990-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 354,416
Dump File Time    : 8/8/2016 7:59:44 PM
==================================================

==================================================
Dump File         : 080716-5959-01.dmp
Crash Time        : 8/7/2016 5:31:12 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`001ec014
Parameter 3       : 00000000`00000002
Parameter 4       : 00000000`0038968d
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+1a82
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\080716-5959-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 392,400
Dump File Time    : 8/7/2016 5:41:19 PM
==================================================

==================================================
Dump File         : 080716-6193-01.dmp
Crash Time        : 8/7/2016 3:10:38 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`05dd5ab0
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.23455 (win7sp1_ldr.160516-0600)
Processor         : x64
Crash Address     : ntoskrnl.exe+6f400
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\080716-6193-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 390,032
Dump File Time    : 8/7/2016 3:16:31 PM
==================================================

 



BC AdBot (Login to Remove)

 


#2 axe0

axe0

  • Malware Study Hall Junior
  • 258 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Netherlands
  • Local time:12:51 PM

Posted 11 August 2016 - 03:55 AM

http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/


Kind regards,
Axe0

#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:51 AM

Posted 11 August 2016 - 05:07 AM

A MEMORY_MANAGEMENT error does NOT mean bad memory/problems with memory.

It means that a function in the Memory Manager had problems.

This can be caused by bad RAM, but is much more commonly caused by corruptions in the structures that the Memory Manager uses to manage memory.

 

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

 

 

While waiting for a reply, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#4 mkillinger

mkillinger
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:51 AM

Posted 16 August 2016 - 03:30 PM

Sorry for the delay in responding, I have diagnosed my issue. I ran Memtest86+ on my computer with a multitude of errors I then systematically swapped rails no change, removed one from rail 2 no change took rail two ram module and put into rail one and low and behold stability.

 

Retested suspect mem back in rail one nothing but errors.

 

Replace set with new Viper Set, benchmarked graphics and ran my games and file updates with no BSOD.



#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:06:51 AM

Posted 17 August 2016 - 06:58 PM

Nice work!  Thanks for letting us know.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users