BSOD issues (included dmp files)

watts · 16 May 2010

I'm getting frequent BSOD's. Upping the voltage on my memory seems to help some, but it will still crash. I've run memtest86+ on both standard voltage and upped voltage with no errors after 12 passes.

I've attached the minidump files.
Originally I thought it as the graphics card since it used to give me gray screens (radeon 5770.) But I recently removed the video card and am running the onboard graphics card ati radeon HD 3300.

Any help greatly appreciated.

zigzag3143 · 16 May 2010

watts said:

I'm getting frequent BSOD's. Upping the voltage on my memory seems to help some, but it will still crash. I've run memtest86+ on both standard voltage and upped voltage with no errors after 12 passes.

I've attached the minidump files.
Originally I thought it as the graphics card since it used to give me gray screens (radeon 5770.) But I recently removed the video card and am running the onboard graphics card ati radeon HD 3300.

Any help greatly appreciated.

with so many different causes it has to be hardware. use these to find out what it means and what to try.https://www.sevenforums.com/crash-loc...-what-try.html

Let us know if you need help

Ken

Code:

BugCheck BE, {fffff8800167dfa0, 4062121, fffff88008b5de90, a}
Probably caused by : hardware ( tcpip!IppFragmentPackets+21b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff89feb1f5d78, 0, fffff80003346584, 5}
Probably caused by : ntkrnlmp.exe ( nt!PsImpersonateClient+44 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff960001363f5, fffff880080711c0, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f7d665, 2, 8, fffff80002f7d665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f7d665, 2, 8, fffff80002f7d665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {5668d22, 2, 1, fffffa8004444010}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff880049c92ef, fffff880057f7ab8, fffff880057f7320}
Probably caused by : RtHDMIVX.sys ( RtHDMIVX+22ef )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : csc.sys ( csc!CscPqEnumContinue+fce )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002fdb665, 2, 8, fffff80002fdb665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f74665, 2, 8, fffff80002f74665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck DE, {2, fffff8a0028d7c20, ffbff8a0028d7c21, 10eb448c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d2a0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f7c665, 2, 8, fffff80002f7c665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f7f665, 2, 8, fffff80002f7f665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f74665, 2, 8, fffff80002f74665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck BE, {fffff8800167efa0, 4062121, fffff88007d3e460, a}
Probably caused by : hardware ( tcpip!IppFragmentPackets+21b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f76665, 2, 8, fffff80002f76665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f8d665, 2, 8, fffff80002f8d665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002f7c665, 2, 8, fffff80002f7c665}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 34, {50830, fffff88002dcb688, fffff88002dcaef0, fffff800030d9efc}
Probably caused by : ntkrnlmp.exe ( nt!ExTryAcquireSpinLockExclusiveAtDpcLevel+4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff80002fcef65, 2, 8, fffff80002fcef65}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

System uptime

Code:

System Uptime: 0 days 0:11:53.540
System Uptime: 0 days 0:26:49.301
System Uptime: 0 days 0:00:26.488
System Uptime: 0 days 1:13:18.292
System Uptime: 0 days 0:31:38.980
System Uptime: 0 days 0:40:37.724
System Uptime: 0 days 2:45:29.172
System Uptime: 0 days 14:09:10.072
System Uptime: 0 days 0:10:55.348
System Uptime: 0 days 1:19:29.637
System Uptime: 0 days 2:14:36.306
System Uptime: 0 days 0:03:57.714
System Uptime: 0 days 1:13:16.121
System Uptime: 0 days 0:08:34.549
System Uptime: 0 days 7:48:45.605
System Uptime: 0 days 3:09:56.523
System Uptime: 0 days 4:14:21.172
System Uptime: 0 days 4:35:22.267
System Uptime: 0 days 2:09:58.000
System Uptime: 0 days 0:57:20.592