New
#11
I am still getting the issue. 100% sure the RAM is seated properly it is dual channel and they are in color coded slots.
I am still getting the issue. 100% sure the RAM is seated properly it is dual channel and they are in color coded slots.
Could you make a photo of how the memory is seated, the dumps keep showing the same.
Please run CPU-Z | Softwares | CPUID, open it and make screenshots of the following tabsCode:[Memory Device (Type 17) - Length 27 - Handle 002ah] Physical Memory Array Handle 0029h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator A0 Bank Locator Bank0/1 Memory Type 02h - Unknown Type Detail 0000h - Speed 1600MHz Manufacturer Serial Number Asset Tag Number Part Number [Memory Device (Type 17) - Length 27 - Handle 002bh] Physical Memory Array Handle 0029h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size [Not Populated] Form Factor 09h - DIMM Device Set [None] Device Locator A1 Bank Locator Bank2/3 Memory Type 02h - Unknown Type Detail 0000h - Speed 1600MHz Manufacturer Serial Number Asset Tag Number Part Number [Memory Device (Type 17) - Length 27 - Handle 002ch] Physical Memory Array Handle 0029h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 09h - DIMM Device Set [None] Device Locator A2 Bank Locator Bank4/5 Memory Type 02h - Unknown Type Detail 0000h - Speed 1600MHz Manufacturer Serial Number Asset Tag Number Part Number [Memory Device (Type 17) - Length 27 - Handle 002dh] Physical Memory Array Handle 0029h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 09h - DIMM Device Set [None] Device Locator A3 Bank Locator Bank6/7 Memory Type 02h - Unknown Type Detail 0000h - Speed 1600MHz Manufacturer Serial Number Asset Tag Number Part Number
- CPU
- Mainboard
- Memory
- SPD*
- Graphics
*SPD shows the details of each module, you can show the details by choosing different slots in the left upper corner.
Please make screenshots of each module.
Please post each screenshot in your next reply/replies.
Hi there Axe0 sorry for late reply.
I recently got another blue screen recently. All the screenshots you asked for are attached and a new ZIP file from dm log collector.
Please take a look! Thanks!
Ok I did that and got irql_not_less_or_equal bsod, do you have an idea what the cause of this could be?
Thanks
Hi Velos,
I am currently analyzing the files, but it is appreciated if you would provide description about the BSODs, what happened & what you were doing. That makes troubleshooting much smoother as we may see a pattern in it to solve the BSODs.
What currently happens: you provide data, we analyse them and give you the probable cause (probable because it is never 100% certain until the provided suggestion has been tested). This is in many cases fine and works, but it doesn't always work. In some cases the root cause hides behind the causes that the dumps provide, in many cases this is due to unknown hardware failure, what can make it difficult to find the root cause. We need more information than all those files can provide in such situations and that is where the user comes in who needs to provide details about the situation so we can start troubleshooting with those information included and get to a solution we normally wouldn't come real quick because of missing information :)
That said I would like to provide a few suggestions and some possible causes
The suggestions:
- Please check your Corsair SSD for firmware updates.
- Please restore the settings in the BIOS to the optimal default settings.
Possible causes: Memory, hard drives.
I have gone through the event logs searching for BSOD events and the following BSOD error codes give the possible causes
- 0x101 4x
- 0x24 1x
- 0x1A 1x
- 0x50 1x
- 0x4E 1x
- The 0x101 is a bugcheck that is mainly caused by the BIOS, hardware and drivers.
- The 0x24 is a crash about the NTFS file system or the hard drive, it has causes as improper indexing, resident Anti-Virus programs, defrag programs and insufficient memory. Insufficient memory can be caused by memory leakage (drivers are mainly the cause of memory leakage) what makes it possible that the system thinks that a lot of memory is not enough simply because some drivers refuse to let go of memory.
- The 0x1A is a memory crash, unfortunately a memory crash knows a lot of different crashes but it includes the memory & hard drive
- The 0x50 is also sort of a memory crash, it has usual causes as defective hardware where the memory is particular, but als the NTFS file system & BIOS can be included for mentioning.
- The 0x4E is another memory crash, it is about page table entries corruption that can be due to memory & drivers where the memory is important currently.
What I would like to see in your next reply if you get another BSOD is a description of what happened and what you were doing :)
Hello,
Recently I have had two BSOD's over the past week.
The first was on the 7th of June. The blue screen happened when I was watching an episode from a show on VLC player, I had recently been playing a video game 5 minutes prior.
The second BSOD happened when I was downloading a game and watching an episode from a show on VLC player.
I watch alot of shows on my PC mostly everyday, so not sure if this is coincidence. The memory and drive I have are quite new, only 3 months old tops as I ordered them around the same time and I was getting BSOD's before..
I have attached new ZIP.
*I updated the firmware of my SSD which at first did not work until I changed it to AHCI in the BIOS.
Got another, watching video and downloading, skype and some other apps running in the background. The files being downloaded were not going on the SSD, neither was the show I am watching, they are on other hdd.
I recommend that you check Gigabyte for driver updates for everything and also check all your software for updates where possible. Your system is having a lot of drivers where most of them are likely outdated, this can eventually cause problems if not kept up to date.
The crashes are caused by the 802.11n Wireless LAN Card which is using very old drivers
Code:5: kd> lmvm netr28x Browse full module list start end module name fffff880`03ee0000 fffff880`03f7f000 netr28x T (no symbols) Loaded symbol image file: netr28x.sys Image path: \SystemRoot\system32\DRIVERS\netr28x.sys Image name: netr28x.sys Browse all global symbols functions data Timestamp: Thu Feb 26 04:02:09 2009 (49A60631) CheckSum: 000A3BDB ImageSize: 0009F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4