Games AND entire computer crashing after installing new SSD???

[Benmanson97]

I installed my new SSD no problem. Installed windows 8.1 from the disk, then updated all drivers and software, then moved the music from my HDD to the SSD. I then formatted my HDD so I could make sure everything would work properly. I downloaded a couple games to the SSD, and played them. Went fine. I then realized I hadnt installed Samsung Magician yet, so I did. I had a vacation in mexico for a week, so I turned my comp off and left it alone. I get back, and now games are constantly crashing every 5-10 minutes. The games are installed on the SSD. The computer has also crashed 3 times just after startup, each with different error reports. One of them was KMODE something, but I unfortunately forgot the other reports it gave me. I can give you any other info you need, such as which games, whhat folders theyre stored in, etc etc. Thank you

 

[redgarl]

Bingo, you got your answer. I was searching for a culprit for my system for about 8 months until I buy a new SSD.. I never got another BSOD after that. SSD are a pain for that. You cannot detect pinpoint the issue easily.

 

[Benmanson97]

Bingo, you got your answer. I was searching for a culprit for my system for about 8 months until I buy a new SSD.. I never got another BSOD after that. SSD are a pain for that. You cannot detect pinpoint the issue easily.

I have no idea what you just said...

 

[burdenbound]

Grab a program called whocrashed, it's free and it will give you a meaningful message from your BSOD dump files.

 

[Benmanson97]

Grab a program called whocrashed, it's free and it will give you a meaningful message from your BSOD dump files.

On Mon 4/6/2015 4:51:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040615-3203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8037EFC9629, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 program generated an exception which the error handler did not catch.
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 Mon 4/6/2015 4:51:28 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8037EFC9629, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Mon 4/6/2015 5:47:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040515-7484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1509A0)
Bugcheck code: 0xA (0x58, 0x2, 0x0, 0xFFFFF8000D2529C7)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 4/6/2015 5:47:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040515-4984-01.dmp
This was probably caused by the following module: e22w8x64.sys (0xFFFFF801A49A34D0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF801A49A34D0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w8x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w8x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

[burdenbound]

Well that last message looks to be pretty helpful. I would make that change and take it from there, continue looking at the dump files as they come and eventually it will all be figured out. But since none of the crashes point to a hardware issue it might be a matter of installing/reinstalling drivers (maybe even the OS) to get it all sorted out.