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

Random BSoD's - Memmory management most of the times


  • Please log in to reply
23 replies to this topic

#1 bg_sanata

bg_sanata

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 04 March 2017 - 07:58 AM

Hello guys,
 
I have very annoying issue with my new system and it’s huge pain to troubleshoot it. I would appreciate a lot all the help with this since I’m running out of ideas what could be the issue.

Widows 10 x64
Fresh installation (try it 3 times already Home/Pro)
Brand new CPU/RAM/MOBO/VGA and CPU cooler
 
CPU: i5-6600k
VGA: MSI 1060 3GB
MOBO: Asrock 170Z Extreme4 (latest bios)
PSU: Chieftec 750W (4-5 years old)
RAM: 2x16GB Kingston HyperX Fury
1 SSD for OS + 1HDD
 
Sysnative BSOD Dump + System File Collection App –added

 
Issue: BSoD’s - Memory_management; IRQL; Critical processes... 2-3 times per dey + many crashes on different running applications (Mozilla and games since the system is unstable to use it for work at that point).
 
History: After my old VGA died I decide it's time to buy a new system or at least to replace most of it. After the system was assembled and new OS was installed a lot of different issues crashes start happening. SO I re-assembled it once more with another version of Win10 – HOME. Same… so the OS was reinstalled for 3td time with my current version. Unfortunately the system was crashing every 30-60min. skipping all my struggle here with different troubleshooting stuff and here is what I know so far.
 
The CPU was replaced once so it’s highly unlikely to be the root cause. VGA – didn’t sound like that. SSD was perfectly working before on the exact same OS (different hardware but still…). RAM was tested by other person and he didn’t found an issue with it. SO my concerns are – MOBO, PSU or failing Driver.
PSU was ok with the old hardware, never had issues with it. Driver….don’t think so. My best bet was an issue with the MOBO so I returned it to the vendor. They tested it and returned it back to me saying it’s perfectly fine ???
 
Tested:
RAM modules was tested on all slots 1 by 1 as well as dual channel with memtest64

  • Single module never give errors. Reduce the number of BSoD’s but they still occur.
  • Dual channel sometimes don’t have error sometimes is reaching the counter limit of the test (not sure if thus are false errors or now). I was suspecting it’s an issue with the dual channel but as I mention sometimes the test is finishing with no errors.

CPU was replaced once already by the vendor since they was thinking it’s the memory controller
MOBO was tested by the vendor
SSD (OS drive) – tested by me and no issues are found in here.
BIOS – an interesting thing is that if I keep the LLC voltage management to Level 3-4 the number of BSoD’s are reduced but still occur. I don’t think any difference if the RAM or the Memory are slightly clocked or set on fixed voltage.
 
Another interesting thing is that if I Turn of the PC from the grid for a day or reset the CMOS there are no BSoD’s for maybe a week. This is a bit random behavior so cannot be very specific on this.

Was also thinking it could be warping of the CPU at some point but keeping the case horizontal didn’t changed anything.
 
The longest time with no issues was after I was testing the RAM modules. It was running for 1-2weeks without BSoD after that. 1 week the PC was off and when I start it again – BsoD after 2 hours L
 
Another problem for me is that the Vendor is not able to reproduce the issue so I cannot ask them to replace parts.
 
As I say it’s huge pain to troubleshoot this $%^(* and I’m super existed of all this so any help is highly appreciated.

Thank you in advance!


+ .7z with more crashes from windows / 1x mozilla / 1xbattlent / Prime95 test right after crash

https://drive.google.com/file/d/0Byzd8q9fBe44Rml4RmJ0Q0gya00/view?usp=sharing

 

ps. Sorry don't know why the SysnativeFileCollectionApp.zip wasn't attached. Here is a download link: https://drive.google.com/file/d/0Byzd8q9fBe44VklkX1R2UkhqOWs/view?usp=sharing

 

Perfmon output do not contain any errors. I was thinking to keep a running monitor for the memory and pagefile but no idea if this will be helpful at all.



 


Edited by bg_sanata, 04 March 2017 - 10:08 AM.
Merged posts - Hamluis.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,276 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:03:10 AM

Posted 04 March 2017 - 08:40 AM

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

 

Louis



#3 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 04 March 2017 - 03:45 PM

SysnativeFileCollectionApp -added to the original post



#4 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 06 March 2017 - 07:27 AM

Here is the performance monitor reports as well.

The Cisco VPN application was added yesterday. The report before that was all "green".

https://drive.google.com/file/d/0Byzd8q9fBe44UDhMczJKaVNkcUE/view?usp=sharing
 



#5 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:10 AM

Posted 06 March 2017 - 05:35 PM

3: kd> .bugcheck
Bugcheck code 0000001A
Arguments 00000000`00005002 ffffe180`10804310 00000000`000546fb 00005c6f`cffffffe
3: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffff9480`520c9468 fffff803`67596c92 : 00000000`0000001a 00000000`00005002 ffffe180`10804310 00000000`000546fb : nt!KeBugCheckEx
ffff9480`520c9470 fffff803`674a6533 : ffffbc80`00a4b9e0 00000000`00000000 00000000`00000001 fffff803`674e7885 : nt! ?? ::FNODOBFM::`string'+0x3b102
ffff9480`520c94d0 fffff803`674a39c6 : ffff808b`d5b51d00 fffff803`00000000 00007ffe`dbb40118 ffffcf05`131dac00 : nt!MiCompleteProtoPteFault+0xd83
ffff9480`520c95b0 fffff803`674acb72 : 00007ffe`dbb40118 ffffbc80`00a5de00 00000000`00000000 ffff808b`d5b51d00 : nt!MiResolveTransitionFault+0x546
ffff9480`520c9670 fffff803`674ab900 : ffff9480`520c9940 00007ffe`dbb40118 ffffcdbf`ff6dda00 ffff808b`d5b51d00 : nt!MiResolveProtoPteFault+0x642
ffff9480`520c9720 fffff803`674aa46a : ffff808b`d7bbd5f0 00000000`00000100 ffff808b`d7bbd5f0 ffff9480`520c9980 : nt!MiDispatchFault+0x3d0
ffff9480`520c9880 fffff803`67555cfc : ffff808b`d4530800 00000287`fbfc1698 ffff808b`d4530800 00000000`c0000034 : nt!MmAccessFault+0x67a
ffff9480`520c9a80 00007ffe`e80de429 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c (TrapFrame @ ffff9480`520c9a80)
000000ef`349fdc00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`e80de429
3: kd> .trap ffff9480`520c9a80
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00002b992ddfa232 rbx=0000000000000000 rcx=000000ef349fdce0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=00007ffee80de429 rsp=000000ef349fdc00 rbp=000000ef349fdc50
 r8=0000000000010118  r9=00007ffedbb30250 r10=0000000000000007
r11=00007ffedbb3a0f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
0033:00007ffe`e80de429 ??              ???

There was only memory dump. If you're using a disk cleanup utility, please stop. Please provide us with MEMORY.DMP:

 

:step1: Upload MEMORY.DMP

• Press and hold the Windows Key + R on your keyboard at the same time.
• In the Run box, type in %WinDir% and hit Enter on your keyboard.
• Find the file MEMORY.DMP and copy/paste it on to your Desktop.
• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to a trustworthy file-sharing service.
 


Edited by bwv848, 25 March 2017 - 09:23 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#6 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 07 March 2017 - 01:13 AM

Hello,

 

Thank you for looking at this.

I was moving the MEMORY.DMP and the small dump files outside Windows folder. You could find couple of them inside the Dumps.7z archive: https://drive.google.com/file/d/0Byzd8q9fBe44Rml4RmJ0Q0gya00/view?usp=sharing



#7 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:10 AM

Posted 07 March 2017 - 10:10 AM

0: kd> .bugcheck
Bugcheck code 0000001A
Arguments 00000000`00041792 fffffc80`38e1a918 00008000`00000000 00000000`00000000
ffff9e01`01a3b928  fffff804`9c46dd55*** ERROR: Module load completed but symbols could not be loaded for dump_iaStorA.sys
 dump_iaStorA+0x6dd55
0: kd> lmvm iaStorA
start             end                 module name
fffff804`9b530000 fffff804`9b9ff000   iaStorA    (deferred)             
    Image path: \SystemRoot\System32\drivers\iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Tue Sep 13 10:45:46 2016 (57D8111A)
    CheckSum:         000C550F
    ImageSize:        004CF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
*** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sys
 e1d65x64+0x13db5
0: kd> lmvm  e1d65x64
start             end                 module name
fffff804`9f320000 fffff804`9f3a6000   e1d65x64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\e1d65x64.sys
    Image name: e1d65x64.sys
    Timestamp:        Wed Oct 05 05:02:43 2016 (57F4C1B3)
    CheckSum:         00083539
    ImageSize:        00086000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0x19de3
0: kd> lmvm nvlddmkm
start             end                 module name
fffff804`9fa90000 fffff804`a08b8000   nvlddmkm   (deferred)             
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_0cc477a6fec64d8c\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Feb 09 17:20:40 2017 (589CEB38)
    CheckSum:         00DDCA08
    ImageSize:        00E28000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
There were some potential culprits in the "raw stack". Try updating them — download links are below respectively.

**DOWNLOAD LINK INTEL RAPID STORAGE TECHNOLOGY DRIVER**
**DOWNLOAD LINK INTEL NETWORKING DRIVER**

**DOWNLOAD LINK NVIDIA DRIVERS**

When updating your graphics drivers, please perform a Custom Installation. You should only install the Graphics Drivers and PhysX software. :exclame: DO NOT INSTALL ANY 3D DRIVERS!!!

 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#8 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 07 March 2017 - 12:39 PM

Hello,

 

Intel RST and NIC drivers are the same versions I currently have...anyway I reinstall them, maybe this solve some issue with a registry or whatever.
The NVidia driver is a bit older than the one I had but i install it anyway. Clean installation (old one was removed) without 3D drivers as suggested.

The system is currently running with only 1 memory module and when I'm back home I'll add the other once to check if it's more stable after drivers reinstall.
BSoD's are more frequent when memory is in dual channel.



#9 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 08 March 2017 - 11:31 AM

Reinstalling the drivers didn't solve the issue.

New BSoD - https://drive.google.com/file/d/0Byzd8q9fBe44em5veWFlTVU2MmM/view?usp=sharing

If this is a drivers issue, is it possible a memtest86+ test to run in errors (ran through bootable USB drive).

Also when I have both memory sticks on in dual channel i could reproduce an error in Prime95 while single stick is working fine.

 

https://drive.google.com/open?id=0Byzd8q9fBe44bGJ3R09MX2NiNkk

https://drive.google.com/open?id=0Byzd8q9fBe44SlE3ZmVvTEhIalU



#10 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 10 March 2017 - 03:31 AM

Hello,

 

I tried to run the Windows Driver verifier and this cause the attached BSoD: https://drive.google.com/file/d/0Byzd8q9fBe44aW40MU9EM0EzU1k/view?usp=sharing

This was done on single mode memory (no dual channel), which make me think the issue is either with CPU memory controller or the MOBO. First one seems a bit less likely since the CPU was already replaced by the vendor once.

The bad think is that I need a solid proof to RMA the MOBO since they already tested it and told me there is no issues with it. - I don't trust t thus guys and their test. I had t explain them like 10 times what the issue is even there was like 20-30GB BSoD dumps for them.

Thank you for all the time you're spending digging those dump files!



#11 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:10 AM

Posted 12 March 2017 - 09:24 PM

At this point, I honestly think your BSODs are hardware-related. Therefore, please start with these free hardware diagnostics —  run them ALL please and let us know the results.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#12 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 23 March 2017 - 03:30 PM

Hello,

 

I’m back with new MOBO and on the second day there is again a BSoD (super sad face, almost cry) + couple of “Access violation” crashes of applications.

 

Could you please take a look at the attached DUMPs and verify once more if there is no drivers issues?
Pretty much everything was heavy tested on hardware side, CPU and MOBO already changed.

https://drive.google.com/file/d/0Byzd8q9fBe44Wk5rQlMxOHU2elU/view?usp=sharing


Thank you in advance!



#13 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:10 AM

Posted 23 March 2017 - 04:10 PM

Please do this:

 

:step1: Check Disk

WARNING: It is recommended that you backup ALL your files. If CHKDSK finds and repairs a corrupted sector, you may lose your data.
 
• Open Start, and in the Search programs and files box, type cmd.
• Right-click on cmd, select Run as administrator, and accept any User Account Control prompts.
• In the Elevated Command Prompt enter the following:

chkdsk /F %SystemDrive%

• You should see this message:

The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

• Type Y and hit Enter on your keyboard.
• Restart your computer and CHKDSK will run.
 
Once CHKDSK is compete, we need the log:
 
• Open the Start Menu, and in the Search programs and files box, type powershell.exe.
• Right-click on powershell.exe, select Run as administrator, and accept any User Account Control prompts.
• Copy this command:

Get-WinEvent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file $Env:UserProfile\Desktop\CHKDSKResults.txt

Right-click in Powershell to paste the command and hit Enter on your keyboard.
• You will find CHKDSKResults.txt on your Desktop. Copy/paste the log in your next reply.


Edited by bwv848, 23 March 2017 - 04:10 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#14 bg_sanata

bg_sanata
  • Topic Starter

  • Members
  • 15 posts
  • OFFLINE
  •  

Posted 24 March 2017 - 01:16 AM

TimeCreated : 3/24/2017 8:01:19 AM
Message     :
              
              Checking file system on C:
              The type of the file system is NTFS.
              
              
              A disk check has been scheduled.
              Windows will now check the disk.                         
              
              Stage 1: Examining basic file system structure ...
                399360 file records processed.                                                        
              File verification completed.
                9257 large file records processed.                                   
                0 bad file records processed.                                     
              
              Stage 2: Examining file name linkage ...
                466770 index entries processed.                                                       
              Index verification completed.
                0 unindexed files scanned.                                        
                0 unindexed files recovered to lost and found.                    
              
              Stage 3: Examining security descriptors ...
              Cleaning up 852 unused index entries from index $SII of file 0x9.
              Cleaning up 852 unused index entries from index $SDH of file 0x9.
              Cleaning up 852 unused security descriptors.
              Security descriptor verification completed.
                33706 data files processed.                                           
              CHKDSK is verifying Usn Journal...
                40194912 USN bytes processed.                                                           
              Usn Journal verification completed.
              CHKDSK discovered free space marked as allocated in the volume bitmap.
              
              Windows has made corrections to the file system.
              No further action is required.
              
               116706303 KB total disk space.
                73901968 KB in 200325 files.
                  142724 KB in 33707 indexes.
                       0 KB in bad sectors.
                  512767 KB in use by the system.
                   65536 KB occupied by the log file.
                42148844 KB available on disk.
              
                    4096 bytes in each allocation unit.
                29176575 total allocation units on disk.
                10537211 allocation units available on disk.
              
              Internal Info:
              00 18 06 00 be 91 03 00 cd 2f 07 00 00 00 00 00  ........./......
              d4 00 00 00 56 01 00 00 00 00 00 00 00 00 00 00  ....V...........
              
              Windows has finished checking your disk.
              Please wait while your computer restarts.



#15 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:10 AM

Posted 25 March 2017 - 09:25 PM

Just a question... did you swap RAM sticks already?


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users