I'm going crazy with BSOD

[Capitan Harlock]

Hi guys, after i installed my new ssd 2 months ago with a fresh version of Windows 7 ,im getting so many BSOD that i can't figure it out, when i was using mainly my Xeon build i didn't get any and i have the same stuff connected .
I used bluescreenview and whocrashed but didn't help at all to find a solution .

this is what i got recently :

On Tue 08/08/2017 11:56:33 your computer crashed
crash dump file: C:\Windows\Minidump\080817-11044-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x109 (0xA3A039D8A809F607, 0xB3B7465EFA883431, 0x4C0000082, 0x7)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Mon 07/08/2017 21:44:29 your computer crashed
crash dump file: C:\Windows\Minidump\080717-11778-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0xD1 (0xFFFFF8004408D12A, 0xD, 0x8, 0xFFFFF8004408D12A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 06/08/2017 23:30:25 your computer crashed
crash dump file: C:\Windows\Minidump\080617-12074-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40)
Bugcheck code: 0x1A (0x403, 0xFFFFF680000830F0, 0x963000026C7D2867, 0xFFFFF6800027C72A)
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

If the only solution is try to reinstall windows il do it but is a pain to redownload all the games i'm playing on steam XD.

 

[CAPSLOCKSTUCK]

Try updating to W 10. You wont have to redownload your games and you can always go back to W7.

Might cure it.

 

[Capitan Harlock]

Try updating to W 10. You wont have to redownload your games and you can always go back to W7.

Might cure it.

I don't like windows 10 but if possible i would like to fix it in some way and don't format after 2 months.

 

[R00kie]

Get all your games on a secondary hard drive (I see you have many), and then re-install Windows. You can always add back the folder with the games into Steam as soon as you re-install it.

 

[Mussels]

all three mention memory management, i'ma hazard a guess that your RAM's not completely stable.

I had somewhat similar when OC'd at idle, despite passing all stress tests i could throw at the system. In my case i had to disable C3 and C6 power states to prevent the crashes, but you could have a totally different cause with similar symptoms.

 

[Vayra86]

Looks an awful lot like a corrupted Windows install to me, which is plausible since the problems started when you reinstalled on a new drive.

Reinstall Windows on same drive, if problem persists, look at the SSD itself, maybe its faulty. You can go to Win 10, but that doesnt help you narrow the problem down and might also not even fix it. Go 10 when you have fixed the issue

I do not suspect RAM because then the problem would have occurred before the SSD came in. You've got three kernel errors on the same .exe, this looks like a disk access/read issue or corrupted file.

 

[Capitan Harlock]

Ram is new a 16 gb kit from G Skill and before i was using a 16gb kit from Kingstone that is on my Xeon build.

all three mention memory management, i'ma hazard a guess that your RAM's not completely stable.

I had somewhat similar when OC'd at idle, despite passing all stress tests i could throw at the system. In my case i had to disable C3 and C6 power states to prevent the crashes, but you could have a totally different cause with similar symptoms.

I didn't hade problems with my OC before so if the problem is related to that what can cause it to be unstable?

 

[Vayra86]

Ram is new a 16 gb kit from G Skill and before i was using a 16gb kit from Kingstone that is on my Xeon build.

Then swap back the Kingston kit you were using and see if the issues go away. If they do, solved. If they don't, swap back to G Skill kit and try my suggestion to reinstall Windows.

Even if they both aren't a fix, you will be narrowing down the issue to fewer components - this is the most important thing to do or you'll be tossing the PC out the window in frustration eventually.

 

[Capitan Harlock]

Then swap back the Kingston kit you were using and see if the issues go away. If they do, solved. If they don't, swap back to G Skill kit and try my suggestion to reinstall Windows.

Even if they both aren't a fix, you will be narrowing down the issue to fewer components - this is the most important thing to do or you'll be tossing the PC out the window in frustration eventually.

I was using the Kingstone kit on my Xeon build and then on this Main, I got the G Skill because of XMP and higher frequency .

I think the main cause if windows because would be a problem if brand new ram is at fault after 1 month i got it.

 

[basco]

so you are running your 16gb g.skill kit at 2133mhz??
how you run it with 4 ? or only 3 sticks?
try whithout xmp and this kit is probably not designed for tripple channel socket 1366-so running it with more then 1866mhz will need some manual tuning

 

[Capitan Harlock]

so you are running your 16gb g.skill kit at 2133mhz??
how you run it with 4 ? or only 3 sticks?
try whithout xmp and this kit is probably not designed for tripple channel socket 1366-so running it with more then 1866mhz will need some manual tuning

I'm using it with my Main rig not the Xeon.

 

[Vayra86]

Start trying component swaps like we suggested so you can narrow down the issue without having to do time consuming reinstalls and/or RMAs for components.

 

[Kursah]

Have you ran any stress tests? OCCT, memtest, Asus ROG RealBench are what I use beyond actually gaming.

I agree with the above that you might have some memory issues going on, you might reset your BIOS/EFI, load optimized defaults, load XMP profiles, and see if that helps.

Also, you might consider running an OS repair rather than a re-install. Even an in-place upgrade of Windows 7 if all else fails, which is in essence re-installing Windows without killing your installed programs. Check the Windows OS Repair link in my sig for more info.

I would load up Crystal Disk Info and check your drive's health, and potential errors as well. That SSD might have issues even though it is new. Worth checking out at least.

 

[thebluebumblebee]

Could even be a bad SATA cable.

 

[Capitan Harlock]

Have you ran any stress tests? OCCT, memtest, Asus ROG RealBench are what I use beyond actually gaming.

I agree with the above that you might have some memory issues going on, you might reset your BIOS/EFI, load optimized defaults, load XMP profiles, and see if that helps.

Also, you might consider running an OS repair rather than a re-install. Even an in-place upgrade of Windows 7 if all else fails, which is in essence re-installing Windows without killing your installed programs. Check the Windows OS Repair link in my sig for more info.

I would load up Crystal Disk Info and check your drive's health, and potential errors as well. That SSD might have issues even though it is new. Worth checking out at least.

Sata cables are new , I tried memtest and got no errors, i run some benchmarks and used the stress test of CPUZ and got no problems .
I disabled some stuff in the bios and got no problems so far, no i wanna try to do the update to windows 7 like Kursah have suggest and try real bench.

 

[Capitan Harlock]

I tryed the Update Windows 7 route but didn't want to do it because thinks i'm going to do an update from 64 to 32 bit when is crazy.
Crystal disk info says everythign was all right , only one hd i knew hade problems but i'm using it only for games and before was being used for games and didn't gave me problems even with that alert.
I fixed the alert with Crystal disk info and now will see if the problem was that.
When i launch Realbench i go past the first 2 tasks but when it starts open cl or heavy multitasking they crash so i can't do it .

 

[Solaris17]

I fixed the alert with Crystal disk info and now will see if the problem was that.

??

Error: CRITICAL_STRUCTURE_CORRUPTION

bruh. IF you have a bad drive you have a bad drive.

 

[Capitan Harlock]

??


bruh. IF you have a bad drive you have a bad drive.

I didn't get any BSOD after that drive got a warning and i was using it for games and stuff.

Now using Cristal disk info i modified a parameter and was saying was good but the drive is still in warning.

So the final thing do to is try to don't use that drive and see if i don't get BSOD .

Edit: i disabled and disconnected the hd with the warning but i got a BSOD so the main problem is another.

The last thing i need to do is reinstall windows.

 

[Capitan Harlock]

Guys, i formatted and i discovered that the cause of many BSOD could have been related to old intel chipset drivers that where not updated .
I hope now is all right .
If i get other BSOD i don't know where to look XD .

 

[Regeneration]

When do you get those BSODs? at idle, or during load?

Do you have C-states on or off? Sometimes, if you overclock by BCLK and C-States are enabled, the CPU gets insufficient voltage at idle/light load, you get such BSODs.

Those BSODs codes are either related to RAM or Vcore.

MemTest86 isn't a good tool to verify RAM OC stability. Use HCI MemTest or TPU MemTest64, run either of them for at least 8 hours.

0xD1, 0x1A, 0x109, are usually memory related BSODs, reconnect the memory sticks (maybe of them is not sitting well within the socket), check out the timings and voltage in the BIOS.

 

[Capitan Harlock]

When do you get those BSODs? at idle, or during load?

Do you have C-states on or off? Sometimes, if you overclock by BCLK and C-States are enabled, the CPU gets insufficient voltage at idle/light load, you get such BSODs.

Those BSODs codes are either related to RAM or Vcore.

MemTest86 isn't a good tool to verify RAM OC stability. Use HCI MemTest or TPU MemTest64, run either of them for at least 8 hours.

0xD1, 0x1A, 0x109, are usually memory related BSODs, reconnect the memory sticks (maybe of them is not sitting well within the socket), check out the timings and voltage in the BIOS.

I have already done all of that .
Even changed the dims from the slots and before formatting i was getting those BSOD.
Now after the new installation of the OS i got 2 BSOD that where related to old intel chipset drivers outdated that where giving me problems.
About when that happen well it was at random ,sometimes when i was playing games and sometimes when the pc was in idle .

 

[Regeneration]

1. Well, double check the RAM stability with HCI MemTest or TPU MemTest64. MemTest86 isn't stressful enough.

2. The last Chipset driver for X58 is 9.4.0.1017, and if you use AHCI, the last is RST 11.7.4.1001.

3. Check out IRQ assignment in the device manager, sometimes IRQ sharing trigger such BSODs.

 

[Capitan Harlock]

1. Well, double check the RAM stability with HCI MemTest or TPU MemTest64. MemTest86 isn't stressful enough.

2. The last Chipset driver for X58 is 9.4.0.1017, and if you use AHCI, the last is RST 11.7.4.1001.

3. Check out IRQ assignment in the device manager, sometimes IRQ sharing trigger such BSODs.

I have already done it with TPU Memtest too and the system where i have BSOD is my Main not my Xeon build.

For now seems that i have resolved by uninstalling a an antimalware that was doing stuff with Tcpip.sys .

Same with updating all the chipset drivers from intel that where older.

 

[DeathtoGnomes]

how old is that MB? Have you replaced the TIM on the south and north bridge recently? getting constant errors for memory regardless of what you do could mean the memory controller is fubar. if the memory is on the QVL, and memtest is ok, you could still have a bad mem stick. Does your memory have heat sinks on them?

 

[Capitan Harlock]

how old is that MB? Have you replaced the TIM on the south and north bridge recently? getting constant errors for memory regardless of what you do could mean the memory controller is fubar. if the memory is on the QVL, and memtest is ok, you could still have a bad mem stick. Does your memory have heat sinks on them?

Everything on my Main rig is new , ram is from June , everithing else was buyed new in December.
Yes both Kingstone and G Skill ram have heat sinks .
I'm using my Main X79 .