BSOD Memory_Management and random crash without BSOD

[snowboi]

View attachment 272276Hi,

I have been having alot of issues with BSOD and i went to reformat my PC thinking it will solve everything. But it didnt, now its have BSOD MEMORY_MANAGEMENT and alot of random auto shutdowns. I cant update my windows when the windows update is trying to update anything relate to NET.framwork. i've attached the minidump files. please help me.

 

[x BlueRobot]

Please follow - http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[snowboi]

can anyone help me?

 

[x BlueRobot]

Read Post #2 please, you haven't uploaded all the necessary files to help you with.

 

[snowboi]

Read Post #2 please, you haven't uploaded all the necessary files to help you with.

ive attached the zip file already. sorry about that.

 

[x BlueRobot]

You appear to have only 121 updates installed, I currently have 205 updates on my system, please check and install all Important and Optional Windows Updates:

1. Start rb:
2. Type: Windows Update
3. Check for Updates/Install all Updates
4. Reboot (if prompted)

Remove:

0: kd> [COLOR="SeaGreen"]lmvm iaStor[/COLOR]
start             end                 module name
fffff880`01015000 fffff880`013b9000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        [COLOR="Red"]Thu Feb 02 00:15:24 2012[/COLOR] (4F29D59C)
    CheckSum:         0008B2F8
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please remove the Intel Rapid Storage driver, is a very well known cause for BSODs for Windows 7 and Windows 8, follow these steps to allow Windows to install it's own driver:

1. Start rb:
2. Type: Device Manager
3. Expand: Disk Drives
4. Remove Intel Rapid Storage
5. Reboot

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

 

[snowboi]

You appear to have only 121 updates installed, I currently have 205 updates on my system, please check and install all Important and Optional Windows Updates:

1. Start rb:
2. Type: Windows Update
3. Check for Updates/Install all Updates
4. Reboot (if prompted)

Remove:

0: kd> [COLOR="SeaGreen"]lmvm iaStor[/COLOR]
start             end                 module name
fffff880`01015000 fffff880`013b9000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        [COLOR="Red"]Thu Feb 02 00:15:24 2012[/COLOR] (4F29D59C)
    CheckSum:         0008B2F8
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please remove the Intel Rapid Storage driver, is a very well known cause for BSODs for Windows 7 and Windows 8, follow these steps to allow Windows to install it's own driver:

1. Start rb:
2. Type: Device Manager
3. Expand: Disk Drives
4. Remove Intel Rapid Storage
5. Reboot

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

I've done everything but it still has memory_management BSOD . but this time round it has two other BSOD. the system_service_exception and "clock interrupt was not received on a secondary processor within the allocated time interval"

i've uploaded the new files.

EDIT: I just gotton another BSOD this time its page_fault_in_nonpaged_area when im playing BF3

i have already reupload the files. sorry for the problems.
Thanks.

 

[x BlueRobot]

[COLOR="red"]BugCheck 50[/COLOR], {fffff87fc4a4b120, 1, fffff80002ea2f8d, 5}


Could not read faulting driver name
Probably caused by : [COLOR="red"]hardware [/COLOR]( nt!NtYieldExecution+1d )

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Most of the BSODs seem to all point towards a illegal page fault, which is usually caused by drivers, please follow these steps:

Update:

1: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`05a13000 fffff880`06586000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Fri Mar 29 02:27:04 2013[/COLOR] (5154FBF8)
    CheckSum:         00B25604
    ImageSize:        00B73000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

• http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

However, the BSOD seems to point to a unknown possible hardware error, and since the graphics card drivers are blamed, although most likely the latest version, then I would also suggest running a test on the graphics card:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Warning

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components

Use the following program to monitor your hardware temperatures during the stress test:

• CPUID HWMonitor

 

[snowboi]

[COLOR="red"]BugCheck 50[/COLOR], {fffff87fc4a4b120, 1, fffff80002ea2f8d, 5}


Could not read faulting driver name
Probably caused by : [COLOR="red"]hardware [/COLOR]( nt!NtYieldExecution+1d )

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Most of the BSODs seem to all point towards a illegal page fault, which is usually caused by drivers, please follow these steps:

Update:

1: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`05a13000 fffff880`06586000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="Red"]Fri Mar 29 02:27:04 2013[/COLOR] (5154FBF8)
    CheckSum:         00B25604
    ImageSize:        00B73000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

• http://www.sevenforums.com/graphic-cards/1810-latest-amd-catalyst-video-driver-windows-7-a.html

However, the BSOD seems to point to a unknown possible hardware error, and since the graphics card drivers are blamed, although most likely the latest version, then I would also suggest running a test on the graphics card:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Warning

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components

Use the following program to monitor your hardware temperatures during the stress test:

• CPUID HWMonitor

how long should i keep the hardware test running? if there isnt any artifacts or temperature level out i just keep it running?

EDIT: i ran the test, it doesnt seem to have any problems even when the temperature reaches 83 degrees. so i went to try playing bf3 again after letting it cool down. but then the BSOD "page_fault_in_nonfault_page" appeared even before i go into the game. so my PC restarted but then it went into another bluescreen for 7 times continuously after every restart. all the BSOD that i mention before appeared. i am now running in safe mode due to the BSOD loop.

ive uploaded the files for today.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff80002e7df9a, fffff8800884c2b0, 0}

Probably caused by : [COLOR="red"]hardware[/COLOR] ( win32k!DEVLOCKBLTOBJ::bLock+6b3 )

Usual causes:  System service, Device driver, graphics driver, memory

How long did you manage to run the test for? win32k.sys is commonly used for graphics-related function calls and communication with graphics drivers, therefore I feel there may still a graphics related cause.

What are temperatures of your graphics card under load (playing games) and idle (doing nothing)?

Post the temperature of your GPU in the two different situations using - http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[snowboi]

I ran the RAM test and there was no error. i also did the video card stress test and was able to run for more than 3 hours without any issues.

 

[x BlueRobot]

Okay good, how many passes did you run MemTest86+ for?

Could you post the temperature of your graphics card in the two situation stated in my last post please?

 

[snowboi]

I run the RAM test to at least 8 passes. i attached two pictures on the GPU temperature. i was play blacklight retribution max settings for the gaming temperature.

 

[x BlueRobot]

I don't see any overheating issues in my opinion, have you had any other BSODs recently?

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

 

[snowboi]

i just gotten another BSOD while playing Firefall. i have done the disk check and have no errors.

 

[x BlueRobot]

What about the other diagnostics?

[COLOR=Red]BugCheck 3B[/COLOR], {[COLOR=SeaGreen]c0000005[/COLOR], fffff880018d9f7c, fffff8800ce576f0, 0}

Probably caused by : ndis.sys ( ndis!memcpy+21c )

Usual causes:  System service, Device driver, graphics driver, memory

The function call memcpy, is used to transfer data between different buffers, I'm guessing in order to do so, it will need to cause the thread to wait and create a context switch for the waiting thread, so activity can resume normally. However, threads can't be scheduled to wait at IRQL Level 2, since the scheduler is also disabled.

CONTEXT:  fffff8800ce576f0 -- ([COLOR=SeaGreen].cxr 0xfffff8800ce576f0[/COLOR])
rax=0000000005f5e100 rbx=0000000000000008 rcx=0000000000000020
rdx=fffffffffad9d238 rsi=0000000000000020 rdi=0000000000000000
rip=fffff880018d9f7c rsp=fffff8800ce580d8 rbp=0000000000000270
 r8=0000000000000000  r9=0000000000000000 r10=fffff880018d6000
r11=fffffa800c923b78 r12=0000000000000278 r13=0000000000000000
r14=0000000000000000 r15=fffffa800c923b78
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
[COLOR=Red]ndis!memcpy+0x21c:[/COLOR]
fffff880`018d9f7c c3              [COLOR=Blue]ret[/COLOR]

If I'm right, the ret is return, and the memcpy returns the destination address, which seems to be a non-paged pool address.

3: kd> [COLOR=SeaGreen]!irql[/COLOR]
Debugger saved IRQL for processor 0x3 -- 2 (DISPATCH_LEVEL)

3: kd> [COLOR=SeaGreen]lmvm e1c62x64[/COLOR]
start             end                 module name
fffff880`05000000 fffff880`05081000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        [COLOR=Red]Fri Mar 16 03:57:28 2012[/COLOR] (4F62BA28)
    CheckSum:         000895BE
    ImageSize:        00081000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel(R) 82579V Gigabit Network Connection driver seems to be a possible cause, please update the driver from here - https://downloadcenter.intel.com/default.aspx

 

[snowboi]

i havent got any BSOD anymore but will still try to see if it happens. thanks for helping me with this problem

 

[x BlueRobot]

Welcome. and that's good to know

 

[snowboi]

Im having blue screens again. i was having problem with .net framework updates from Windows Update. so i asked for help here in this forum and i was asked to use a program to clean up the .net framwork and reinstall it. so i did what i was told to but just when i was installing .net framwork 4.5, my computer shows a BSOD before the installation is done.and then when the reboot is done another BSOD appear.

Edit: ive manage to install .net framwork 4.5 successfully. but then whenever i try to update it using windows update, it will go into BSOD.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff8000306bf8b, fffff880073a7440, 0}

Probably caused by : [COLOR="Red"]hardware[/COLOR] ( win32k!RFONTOBJ::wpgdGetLinkMetricsPlus+408 )

Usual causes:  System service, Device driver, graphics driver, memory

3: kd> [COLOR="SeaGreen"]lmvm iaStor[/COLOR]
start             end                 module name
fffff880`0101c000 fffff880`013c0000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        [COLOR="Red"]Thu Feb 02 00:15:24 2012[/COLOR] (4F29D59C)
    CheckSum:         0008B2F8
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Have you ran any hard-drive diagnostics?