Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Memory Management BSOD issues


  • Please log in to reply

#1
Digi_Lutea

Digi_Lutea

    Member

  • Member
  • PipPip
  • 11 posts

I haven't had a BSOD since the last time I've posted here but now I'm having another issue.

 

I recently installed Spore on my computer and ever since then I've been having BSOD's almost every 2 days ever since then. I haven't played anything since i had the first BSOD in a while now but now I'm mostly getting these at night when I'm just watching livestreams and idling on twitter.

 

I was told that my memory could be dying but I'm not 100% sure. I'm hoping that this isn't the case but i want to make sure before I have to get a replacement. All the parts are over 4 yrs old now so it could be that but or it's just something I've done that i haven't noticed.

 

If there is any more info needed, please let me know

 

System info:

 

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Inspiron 1545 , Dell Inc., 0G848F
CPU: GenuineIntel Pentium® Dual-Core CPU T4400 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4253405184 total

 

 

Bluescreen view and WhoCrashedIt info included below

 

Bluescreen view

==================================================
Dump File         : 101614-24944-01.dmp
Crash Time        : 10/16/2014 2:56:50 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`0278f190
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\101614-24944-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 318,427
Dump File Time    : 10/16/2014 2:57:46 AM
==================================================

==================================================
Dump File         : 101414-23649-01.dmp
Crash Time        : 10/14/2014 4:11:00 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`0278f190
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver  : i8042prt.sys
Caused By Address : i8042prt.sys+fdff0190
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\101414-23649-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 318,363
Dump File Time    : 10/14/2014 4:11:53 AM
==================================================

==================================================
Dump File         : 101214-24897-01.dmp
Crash Time        : 10/12/2014 6:41:56 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041790
Parameter 2       : fffffa80`0278f190
Parameter 3       : 00000000`0000ffff
Parameter 4       : 00000000`00000000
Caused By Driver  : blbdrive.sys
Caused By Address : blbdrive.sys+fe518190
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+7efc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\101214-24897-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 318,427
Dump File Time    : 10/12/2014 6:42:43 PM
==================================================


WhoCrashed it

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 10/16/2014 6:56:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101614-24944-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800278F190, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 10/14/2014 8:11:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101414-23649-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800278F190, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/12/2014 10:41:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101214-24897-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800278F190, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

p4393897.gif

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

p4393911.gif

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

  • Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
    This will enter you into the Bios\Cmos area.
    Find the Advanced area and click Enter
    Look for Boot Sequence or Boot Options and highlight that click Enter
    Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
    Change the second drive to the C or Main Drive
    Once that is done then click F10 to Save and Exit
    You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.

The running program will look something like this depending on the size and number of ram modules installed:


main_menu.jpg

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

testarea_cu.jpg

The following image is the test results area:

p4393925.gif

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#3
Digi_Lutea

Digi_Lutea

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts

Thanks for the reply. I will do these when I get a chance this week and report back with the results


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP