What's new Search

Recent content by Foresto

F
BSODs are back WIN 7 64bit

https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/15082-few-bsods-win-7-x64-3.html?highlight=#post129793 This was my last topic. I got a completly new motherboard from the warranty repairs and there were just a few driver bsod issues, but I fixed them and there was nothing for...
- Foresto
- Thread
- Nov 12, 2015
- Replies: 0
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Been long time since I wrote here, but the conclusion is - it was the motherboard. I ve sent it for repairs and they gave me a new one and since that there were no more problems.
- Foresto
- Post #47
- Sep 10, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Had another one in the meantime. Didnt remove the GPU yet, will do that tomorrow, but for now:
- Foresto
- Post #46
- Jul 17, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

This is pretty annoying. I didnt get anything for the past week, but then again I got 2 unrelated BSODs Files:
- Foresto
- Post #44
- Jul 15, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Got another BSOD related to the killer network drivers and I decided to follow the step 3 you gave me before and got rid of suite. Lets see if I get another BSOD related to that again.
- Foresto
- Post #43
- Jul 5, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Is there any way to track which hardware causes the problem? Do I need to just wait for more BSODs with more information to track this, cause if I wanted to warranty one of the pieces I actually need to know which causes the problems.
- Foresto
- Post #41
- Jul 3, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Crashed again. IRQL_NOT_LESS_OR_EQUAL with ntoskrnl and iusb3hc.sys
- Foresto
- Post #39
- Jul 2, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

No crashes till now. Was waiting at least 24h to check. Also, I followed this: 2. Try this workaround first, even though it doesn't particularly pertain to your issue specifically - MSI USA - Online Technical Support FAQ | and nothing crashed since, so maybe it was after all the network drivers.
- Foresto
- Post #37
- Jul 2, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Ran all the tests you told me to and everything went with PASSED.
- Foresto
- Post #35
- Jul 1, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Done the change and as soon as the screen went into "Welcome to Windows" I get bluescreen and pc restarts. Had to change back to AHCI to make it work again. Trying with the DOS one now.
- Foresto
- Post #33
- Jul 1, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Ran the DOS Seatools and it said "No hard drives detected". Gonna try the Windows one. As for firmware: EDIT: Seems like neither windows nor DOS is finding anything to scan.
- Foresto
- Post #31
- Jul 1, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

Im running an SSD and HDD. The system is installed on SSD and HDD is just data storage.
- Foresto
- Post #29
- Jul 1, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

https://drive.google.com/open?id=0Bxd8SJxAjOYNNllqUzU1QXE2Nms Here.
- Foresto
- Post #27
- Jul 1, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

I got a new one - NTFS_FILE_SYSTEM Dump:
- Foresto
- Post #24
- Jun 30, 2015
- Forum: BSOD Crashes, Kernel Debugging
F
[SOLVED] Few BSODs - WIN 7 x64

So basically the problems are caused by the killer network drivers and there is no solution to that currently? If thats the case, then I will just have to live with it till they decide to fix it. Thanks Patrick, I will inform you if I get any new BSOD.
- Foresto
- Post #22
- Jun 30, 2015
- Forum: BSOD Crashes, Kernel Debugging

Foresto