Series of BSOD

[Nate96r]

Been having some serious problems with BSOD since I got my computer in December. I'm attaching my minidump files, if anyone could help me out and let me know what my problem is I'd really appreciate it.

I'm using Windows 7 64bit version 6.1 (build 7600). My graphics card is ATI Radeon 4890 with the latest drivers. If there's any other info you need let me know. Thank you all very much.

 

[zigzag3143]

Been having some serious problems with BSOD since I got my computer in December. I'm attaching my minidump files, if anyone could help me out and let me know what my problem is I'd really appreciate it.

I'm using Windows 7 64bit version 6.1 (build 7600). My graphics card is ATI Radeon 4890 with the latest drivers. If there's any other info you need let me know. Thank you all very much.

Twenty three BSOD's is going to take some time. In the mean time I am running the latest 5. Be right back

Ken

EDIT: The first five were a mixed bag. Several were inconclusive (probably crashed before the file could be written), the rest memory corruption.

While I am doing the rest of them for comparision I would download memtestx86, burn it to a cd, and run it for 5 passes at least to test the memory.

Ken

BugCheck 109, {a3a039d89977b603, b3b7465eebf5dec5, fffff88000d5c7d4, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d89968b664, b3b7465eebe6df26, fffff88000cd41b4, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff800030a2e9f, fffff88009610060, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+a7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff800030c570c, fffff88008c8ea60, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c000001d, fffff800030cbe35, fffff880083700a0, 0}
Probably caused by : memory_corruption

 

[zigzag3143]

Here are the rest. They confirm the others. There as so many different causes I have to think hardware. I would still start with the test of your memory.\

Let us know if you need help

Ken

BugCheck 109, {a3a039d89977b603, b3b7465eebf5dec5, fffff88000d5c7d4, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d89968b664, b3b7465eebe6df26, fffff88000cd41b4, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff800030a2e9f, fffff88009610060, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+a7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff96034370158, 0, fffff96000189172, 2}
Probably caused by : win32k.sys ( win32k!GreGetDeviceCaps+402 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff80003067bb7, fffff88006846180, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d89603d5c1, b3b7465ee881ff1b, fffff88000ca6658, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_EndpointFromHandle+6 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41284, 103c3001, 0, fffff70001080000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 7F, {8, 80050031, 6f8, fffff80003397a4f}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {d114710e, 2, 1, fffff88003c76539}
Probably caused by : hardware ( USBPORT!USBPORT_IsrDpc+23d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff800031f18ed, fffff88008c8d700, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+51d )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff800030f04c9, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6c9 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck C2, {7, 1097, 4c004c, fffff8a00ada5520}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+1f830 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d8969b692c, b3b7465ee9197bc6, fffff88000c58d60, 1}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {fffff8008330b930, 2, 0, fffff800030d9b65}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+485 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff8000347ffb9, fffff88007bb7090, 0}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {fffffa80147168af, 2, 0, fffff8000310ba74}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff800030d1139, fffff88006f33f70, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+2b9 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClasspPrepareMcnIrp+bd )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff88004823d6e, fffff88002140818, fffff88002140070}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsPagingOperationPending+42 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {48d8, 2, 0, fffff80003146d2b}
Probably caused by : ntkrnlmp.exe ( nt

 

[Nate96r]

Thanks for the replies. I ran memtestx86 last night for 13 passes and it showed no errors. Going to try a hard drive test I got from Seagate tonight and see if anything shows up there.

If that shows nothing, do you have any other ideas on what the problem could be, or any more tests I could run to diagnose further? Only thing I can think of is the video card or motherboard are bad. Do you know of a way to specifically test them?

Wish I could figure this out, these blue screens are driving me crazy! It's weird too, I can go like 4-5 days with everything being fine, then all of a sudden my computer will freeze or get the BSOD and it will keep happening over and over again.

 

[Nate96r]

Ok the hard drive test passed and did sfc/scannow and it didn't find any integrity violations. Any ideas on what I should do next? If you need any more info let me know. Thanks.

Edit: Just did a FurMark grapics stability test and it seemed to run fine.

 

[Nate96r]

PC froze on me 5 more times today, 4 while watching a video in Firefox, so then tried to watch it in Internet Explorer and froze again.

After the 5 crashes I decided to try and do another stress test on my graphics card to see if it would lock up, and it didn't. So I'm really not sure what that means. My PC can run intense graphics but not a small video in Firefox...

Here's my last 2 dumps. Any help would be greatly appreciated!

 

[ickymay]

Been having some serious problems with BSOD since I got my computer in December. I'm attaching my minidump files, if anyone could help me out and let me know what my problem is I'd really appreciate it.

I'm using Windows 7 64bit version 6.1 (build 7600). My graphics card is ATI Radeon 4890 with the latest drivers. If there's any other info you need let me know. Thank you all very much.

was this bought as a pre built computer or self made ?

has it ever worked without issue ?

what is the exact make and model of ram ?

what audio card are you using ?

all of your dumps point at memory errors and it is perfectly possible that memtest86 isn't detecting a ram problem ?

try taking out all but one of your ram sticks (as long as this doesn't void warrenty?) and see if your system stabilizes

 

[Nate96r]

Alright trying to figure out how to separately quote your questions, but I'm not a big forum user and it's not working so here are the answers with no quotes lol.

I bought the computer from CyberPower's website, by picking the stuff I wanted. They put it together and mailed to me.

It has never worked right, I got a BSOD the first or second day I got it.

The RAM is made by Super-Talent. I have 2 2GB sticks. One in slot 1 and one in slot 3, (which is how Gigabyte wants you to do it). The exact make and model:
2GB/128x8 CL9
DDR3-1333
W1333UB2GV

I'm just using the onboard audio, so whatever is on the motherboard.

Ok so I took out one of the RAM sticks and tried to run a few videos that usually cause me to crash, and I didn't crash. So I tried the other stick and it worked fine again. I tried slots 1 and 3 with just one stick and everything works. So it seems the RAM sticks are fine, but when I have them working together it causes my PC to become unstable.

I was hoping one of my sticks were bad so I could just get a new one and problem solved. But I'm not sure what to do if they both work, just not together. Any ideas?

 

[Nate96r]

Well just crashed with one stick in, trying just the other stick till it crashes I guess.

 

[ickymay]

Well just crashed with one stick in, trying just the other stick till it crashes I guess.

It suggest a ram mismatch and I would be looking at sending the system back RMA as it has never worked properly ?

 

[Nate96r]

It would cost $60 to send it back, then $60 again to return it after they fix it. Really don't want to go through all that.

One RAM stick might be bad. I'm still stable with just the working one in. Hopefully this keeps up and I can RMA just one of the RAM sticks.

Would you happen to know if my RAM is compatible with my motherboard?

 

[ickymay]

It would cost $60 to send it back, then $60 again to return it after they fix it. Really don't want to go through all that.

One RAM stick might be bad. I'm still stable with just the working one in. Hopefully this keeps up and I can RMA just one of the RAM sticks.

Would you happen to know if my RAM is compatible with my motherboard?

well your motherboard spec page should show a list of compatible ram but before you check you also need to know which revision number your board is , either rev 1.0 or rev 2.0 ?

Unfortunately I cannot find the memory support list on their newly designed website

I would seriously pursue your original pc supplier and tell them how specific all these BSOD are and ask them why it should incur you a cost as they have sold you a system that has never worked !

If it was a car it would be on recall at their expense so how is your computer different ?

 

[Nate96r]

It's Rev 1.0

he BGOD stopped with just RAM stick in, but it still occasionally locks up, and I have to force a restart.

I'm not really sure what else to do. Do you think the RAM isn't compatible with my motherboard? That's the only thing I can think of.

Like I said I can't send the whole system back, I need my PC and not worth all the hassle and money. But if I knew for sure it was the RAM I could either buy some new sticks or return what I got for some new ones. Just don't want to go there if I don't even know if that's the problem.

 

[ickymay]

It's Rev 1.0

he BGOD stopped with just RAM stick in, but it still occasionally locks up, and I have to force a restart.

I'm not really sure what else to do. Do you think the RAM isn't compatible with my motherboard? That's the only thing I can think of.

Like I said I can't send the whole system back, I need my PC and not worth all the hassle and money. But if I knew for sure it was the RAM I could either buy some new sticks or return what I got for some new ones. Just don't want to go there if I don't even know if that's the problem.

have you updated your bios ??

If yes and your running the latest version then with the .dmp files and symptoms you have described everything strongly suggests your ram is either faulty or a bad match but it could be a motherboard fault such as the memory controller which is in the northbridge chipset or as a less likely option another fault we haven't yet discovered ?

In your situation I would get in touch with "Cyberpower" and tell them what's happening and ask them if they can replace the ram for something off the compatible list or if they will replace the whole machine ?

super talent 2GB/128x8 CL9, DDR3-1333, W1333UB2GV is NOT on the compatible list for your motherboard View attachment 76556 so you have a strong case for a badly built system ?

I believe if you talk to them they will help as they are fully aware that supporting a product with no cost to yourself is your right as a buyer and you may be pleasantly surprised , just be firm but polite and let them offer you a solution ?