Edited by Ordo426, 11 August 2011 - 07:39 PM.
BSOD errors with no consistency
Started by
Ordo426
, Aug 11 2011 07:38 PM
#1
Posted 11 August 2011 - 07:38 PM
#2
Posted 12 August 2011 - 07:57 AM
Post your dumps and we'll take a look!
#3
Posted 12 August 2011 - 05:25 PM
I swear they were attached. Odd, anyway here they are.
EDIT: After removing some of my RAM, I found that the bluescreens occurred way less. I can 15-45 minutes without a bluescreen now and my computer's performance has increased with less memory. So it seems likely that I am getting bluescreens for a driver problem and for bad memory. Since I have removed the bad memory I have been getting 0x00000d1 stop messages with tcip.sys and driver_irql_not_less_or_equal. I thought I would mention this so that you could give those errors some special interest if you are looking at my minidump files.
EDIT: After removing some of my RAM, I found that the bluescreens occurred way less. I can 15-45 minutes without a bluescreen now and my computer's performance has increased with less memory. So it seems likely that I am getting bluescreens for a driver problem and for bad memory. Since I have removed the bad memory I have been getting 0x00000d1 stop messages with tcip.sys and driver_irql_not_less_or_equal. I thought I would mention this so that you could give those errors some special interest if you are looking at my minidump files.
Attached Files
Edited by Ordo426, 12 August 2011 - 08:41 PM.
#4
Posted 13 August 2011 - 01:39 PM
So I am seeing two causes in your dumps - as you have already pointed out.
1) Lots of faults in ntfs.sys and ntoskrnl.exe. With so many faults there and the variety of STOP errors, it does look like RAM. After removing the obviously bad stick of RAM, have you been able to run a memory test?
2) I also see 3 faults in tcpip.sys - all driver_irql_not_less_or_equal. Make sure your network drivers are up to date - your wired network card and your wireless card (if you have a wireless card).
1) Lots of faults in ntfs.sys and ntoskrnl.exe. With so many faults there and the variety of STOP errors, it does look like RAM. After removing the obviously bad stick of RAM, have you been able to run a memory test?
2) I also see 3 faults in tcpip.sys - all driver_irql_not_less_or_equal. Make sure your network drivers are up to date - your wired network card and your wireless card (if you have a wireless card).
#5
Posted 20 August 2011 - 03:21 PM
Yeah I have checked all my drivers and they are up-to-date. With the RAM, when I did Windows Memory Diagnostic, it would bluescreen in the middle of it, probably when it reached the error. I found out that the RAM was bad after doing swaps with the memory and check if a bluescreen occurs. I just took it out and my bluescreens have not occurred for a week. Bad news is that my memory died after one year, good news is that it may be under warranty and I can upgrade to more memory.
#6
Posted 20 August 2011 - 06:28 PM
Well then it looks like it might have been the network driver hitting that bad RAM. Let us know if you are still having issues after replacing your RAM!
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users