Sign in with
Sign up | Sign in
Your question

Random BSODs problem

Last response: in Systems
Share
July 25, 2012 4:19:53 PM

Hello, I've been getting several BSODs on my computer that I've recently built on random occasions and reasons. I tried to run memtest v3.5b and it suddenly stopped at the end of the first pass and said "unexpected interrupt- cpu0 halted" or something like that. Memtest86 for some reason also got the brand of my cpu wrong and said that L2 and L3 cache is unknown. I'm not sure if this even matters, but I still want to know why exactly this happened and what I should do next to solve this issue. I also tried to reinstall my display driver, but according to the minidump files the display driver doesn't really have much to do with it. This is what it says in the minidump files from the bluescreens that I got so far.

==================================================
Dump File : 071312-28080-01.dmp
Crash Time : 7/13/2012 8:15:05 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000099
Parameter 2 : fffff8a0`0c2127c0
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+1acb0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071312-28080-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 297,512
==================================================

==================================================
Dump File : 072412-19390-01.dmp
Crash Time : 7/24/2012 11:54:39 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`0000000d
Parameter 2 : fffffa80`07521790
Parameter 3 : 00000000`6873534b
Parameter 4 : fffffa80`0b2e3b30
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+5f99
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\072412-19390-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 293,008
==================================================
==================================================
Dump File : 070912-15412-01.dmp
Crash Time : 7/9/2012 7:42:46 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`000007f0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`0309c8c5
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070912-15412-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 294,248
==================================================

Also here are my specs. Please reply to this thread if you know of any way to fix this issue. Thank you.

Intel core i5-2400 CPU @ 3.10GHz
MSI Z77A-GD65 Intel Z77 Socket Motherboard
8GB of ram
GTX 560 TI 2GB
850W Corsair PSU

More about : random bsods problem

July 25, 2012 4:30:04 PM

Given that memtest86+ basically crashes and burns, and has problems identifying your CPU correctly, you may well have a defective CPU.

However, just to be sure, take out all but one memory module and then see if things improve. If you get the error still, be sure to swap in a different memory module and try again just in case that was the bad module. If the errors still occur then try moving the memory module to a different slot and try again. If it is still giving you the same error, then I would have to say it seems to be pointing at either the motherboard or CPU. I would personally lean a bit more towards CPU, but you cannot rule out the motherboard just yet. So if you get to this level, you'll have to decide which is less of a pain to RMA.
m
0
l
July 25, 2012 5:58:30 PM

alright, ill try that, but could it be possible that this version of memtest is simply not compatible with my cpu?
m
0
l
Related resources
July 25, 2012 6:45:43 PM

The latest version of memtest86+ appears to be 4.20, so yes, that is a possibility. Be sure to update your copy of memtest86+ (not memtest86) and then go through and run tests again.
m
0
l
July 27, 2012 10:07:11 AM

alright, I've done two memtests for about 6 passes each and both tests showed errors. This problem appears to be related to the memory so I'll be RMAing it soon. Before I could do that though I want to know if there is a way To find out whether this is actually a problem related to the motherboard itself and not the memory. Is there a way to test the motherboard out to know for sure where the problem is coming from? Unfortunately I do not have another computer to test my memory on so I probably won't be able to do that even if I ask a few of my friends to test it on theirs. Is there any other way to figure out the source of this problem??
m
0
l
July 27, 2012 4:10:05 PM

You will need to test each module individually and assuming at least one of them tests good, then you can put that module in each slot on the motherboard. If it keeps testing good, then the motherboard is fine. It's a slow, laborious, and tedious process, but it's really the only way.
m
0
l
!