Solved Random BSOD(s)

[CustomBuilt]

Hi all,

I have been getting random BSOD since the begining of the year. My hard drive eventually took a dump (I assume due in part of the many BSOD) and got a replacement one. Thought my problem went away because I got a fresh install. Got the new drive in I would say the begining of the month and it ran fine for about 2-3 days, then I started to get BSOD or freezes, streaks across dual monitors, etc. Thought the streaks were due to my graphics cards, tested each one individually and ran dxdiag on them, updated drivers, it says that there is nothing wrong. Everytime I get a BSOD it says probable cause is different. I ran memtest86 overnight and it failed on test#3. I plan for the next couple of nights to test a pair of sticks and cycle through to find a possible problem.

Also I should let you know that I took one card out to rule out any Crossfire issues that may be involved and took out 2 sticks, so I only got 8GB of RAM.

My machine specs are:
Windows 7 Professional x64
AMD PhenomII x6 1055T
16GB (4x4) GSKILL GDDR3 9-9-9-24
x2 ATI Radeon 5770 1GB
WD 320GB 7200RPM

I run everything stock and do not overclock anything. When I got the replacement drive, I reset the motherboard to the defaults and not now or ever have I updated the motherboard's bios.

I have debugged all of my dumps and googled them with no luck. I luckily came across this forum and it seems like an excellent place to seek help. The install of my OS was done at the beginning of the month, so about 2 weeks.

Attached are my dumps and dxdiag... anything would help!

Thank you all so much!

 

[Wallonn7]

Hi CustomBuilt and welcome to SF!
I hope that your stay here to honor the first impression you had! You did not mention the psu you use on your computer ... I ask that you add this information and wait for someone from the BSOD Team will help you soon!
Good luck and keep us informed!

 

[CustomBuilt]

Thank you for the introduction! I am glad to be here and hope that as I learn I can spread that knowledge back into the community.

To answer your question about my PSU. It is a Roswell 1000w PSU.

If there is anything else I may have forgotten (my apologies) or should incluse please let me know!

Thanks again!

 

[Wallonn7]

Thank you for the introduction! I am glad to be here and hope that as I learn I can spread that knowledge back into the community.

That's what we hope too!

To answer your question about my PSU. It is a Roswell 1000w PSU.

The better the description, the faster the solution! Thanks for the info!

If there is anything else I may have forgotten (my apologies) or should incluse please let me know!Thanks again!

Relax ... you are welcome, remember?!

 

[Wallonn7]

Delete

What do you mean?!

 

[CustomBuilt]

Since I am new... I do not know how to delete a post...

I clicked on the edit/delete button and did not find a way to delete. I am actually browsing right now to find a way to delete it.

 

[Wallonn7]

Since I am new... I do not know how to delete a post...

I clicked on the edit/delete button and did not find a way to delete. I am actually browsing right now to find a way to delete it.

That's the way!!

 

[CustomBuilt]

Interesting.. I don't have that option.

 

[Wallonn7]

Interesting.. I don't have that option.

Try to complement the "delete" with something like: "this is to delete this post". Click "Save" and repeat the process for deleting.

 

[CustomBuilt]

No go....

I guess that post was meant to live and not to be tossed into bit heaven.

 

[Wallonn7]

No go....

I guess that post was meant to live and not to be tossed into bit heaven.

Take a second look... it is not there anymore!!

 

[Jonathan_King]

It looks as if hardware is the cause from the looks of the dumps; I'd get that RAM replaced and go from there.

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed Mar 16 19:47:44.850 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:17.005
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  winlogon.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Mar 15 19:51:22.127 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:34.891
Probably caused by : ks.sys ( ks!ReadNodeNameValue+18f )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_ks!ReadNodeNameValue+18f
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Mar 13 18:26:51.027 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:15.791
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::AcquireDdiSync+d8 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_dxgkrnl!DXGADAPTER::AcquireDdiSync+d8
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Mar 13 18:21:04.248 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:17.011
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  services.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Mar 11 22:29:46.795 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:26.919
Probably caused by : ataport.SYS ( ataport!PortListRemoveRequest+22 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_ataport!PortListRemoveRequest+22
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar  5 18:00:05.519 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:18.862
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+5205 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::FNODOBFM::_string_+5205
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat Mar  5 16:10:47.860 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:00.202
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[zigzag3143]

Hi all,

I have been getting random BSOD since the begining of the year. My hard drive eventually took a dump (I assume due in part of the many BSOD) and got a replacement one. Thought my problem went away because I got a fresh install. Got the new drive in I would say the begining of the month and it ran fine for about 2-3 days, then I started to get BSOD or freezes, streaks across dual monitors, etc. Thought the streaks were due to my graphics cards, tested each one individually and ran dxdiag on them, updated drivers, it says that there is nothing wrong. Everytime I get a BSOD it says probable cause is different. I ran memtest86 overnight and it failed on test#3. I plan for the next couple of nights to test a pair of sticks and cycle through to find a possible problem.

Also I should let you know that I took one card out to rule out any Crossfire issues that may be involved and took out 2 sticks, so I only got 8GB of RAM.

My machine specs are:
Windows 7 Professional x64
AMD PhenomII x6 1055T
16GB (4x4) GSKILL GDDR3 9-9-9-24
x2 ATI Radeon 5770 1GB
WD 320GB 7200RPM

I run everything stock and do not overclock anything. When I got the replacement drive, I reset the motherboard to the defaults and not now or ever have I updated the motherboard's bios.

I have debugged all of my dumps and googled them with no luck. I luckily came across this forum and it seems like an excellent place to seek help. The install of my OS was done at the beginning of the month, so about 2 weeks.

Attached are my dumps and dxdiag... anything would help!

Thank you all so much!

BSOD causes are all over the map usually hardware I would test the ram first. Let us know the results

 

[CustomBuilt]

Thank you all for your help!

I will continue to test the RAM and keep you all updated.

 

[Wallonn7]

Thank you all for your help!

I will continue to test the RAM and keep you all updated.

You're welcome! And when you judge appropriate, click in the balance - the upper right of each post - to add reputation to those who help you!

 

[CustomBuilt]

Hi all!

Just wanted to give an update. I have ran memtest86 for the past 2 nights on my memory broken into 2 groups of 2(tested in the same slots). Both sets went through 5 passes successfully, ran all night from 10P.M. to 7A.M. with no errors. This is telling me that maybe the RAM is not bad, but perhaps a slot on my motherboard. When I ran memtest86 the first time with all my sticks in all 4 slots, I had a fail on test #3 a few hours in.

I did have another BSOD but I currently do not have access to the dump file. Will attach once I do so.

Thanks again.

 

[Jonathan_King]

The sheer amount of RAM you have may be the problem here. 16GB may need a voltage boost. Could you please post screenshots of the Memory and SPD tabs of CPU-Z?

CPUID - System & hardware benchmark, monitoring, reporting

 

[CustomBuilt]

Hi,

I was running 8GB of RAM and it seemed stable. I put the other 8 back in to get those screen shots for you. I had the voltage on auto in the BIOS and got a BSOD within 2 minutes. I upped the voltage from 1.5 to 1.6 (or thought I did even though images don't show it) and was able to get the screenshots. Got half way through posting this and comp froze, black screen, no BSOD. I took 1 stick out, so I am currently sitting at 12GB and will see how that fairs.

I think you may be onto something though!

I will attach those images along with the BSOD(s).

Thanks!

 

[Jonathan_King]

Try boosting the voltage to 1.65. I can't tell what RAM you have from the part number; do you have a link to your RAM? I am trying to find the maximum voltage those sticks can be run at.

 

[Wallonn7]

Try boosting the voltage to 1.65. I can't tell what RAM you have from the part number; do you have a link to your RAM? I am trying to find the maximum voltage those sticks can be run at.

G. Skill website says only that all ram modules were tested under 1.5 volts. Nothing else. Well, there are similar models and one has to be to our thread starter:

[ Ripjaws ] F3-10666CL9S-4GBRL (4Gx1)
G.SKILL-Products

[ Ripjaws ] F3-10666CL9D-8GBRL (4Gx2) / F3-10666CL9Q-16GBRL (4Gx4)
G.SKILL-Products


Hope it helps!