Help my unmanageble problem: Multiple BSOD

[pankozin]

Hello. Resently i have changed motherboard Asus M5A78LUSB3 with fx 6xxx CPU to Asus P8P67 LE with i5 2500 CPU, all other components remained (they are 2 DIMM G Skill RipjawsX F3-10666CL7-4GBXH, AMD Radeon HD 5800 Series). Actually, it was a swap, i took p8 motherboard with CPU from one pc into another. So after i done it, i reinstalled windows and started to get regular BSODs.
So here is link to minidump files.
http://www.ex.ua/576564233170

If somebody can read them, plz help me to track the issue, coz i cant understand wich driver or hardware is causing this... I think it might be hard drive, but i dont know which (coz i start to get blue screens on the rise (etc firs day 1, second 3, third 5) and apps are failing or FC more and more often each BSOD i got)...
Btw, i tried to set another RAM stick, but got BSOD again... so its probably HDD, but i dont now, is it driver fail or HDD is broken (but it worked fine for 1y on another motherboard)
Also, i added full sys specs to my link
Thank you^_^

 

[daveybrat]

Here's a link to a free program that will read your Windows dump files and give you more info about the blue screens.

http://www.majorgeeks.com/files/details/bluescreenview.html

 

[mikeymikec]

OS version? Clean install for the new board?

Let us know more about the BSODs when you've used the suggested utility.

 

[Ketchup]

Here is what WhoCrashed reports on your minidumps:


#1
crash dump file: C:\WINDOWS\Minidump\110514-20576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x15CFDA, 0x2, 0x15CED9)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



and #2
crash dump file: C:\WINDOWS\Minidump\110414-40154-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFA8002FDC61B, 0x0, 0xFFFFF80002CBF7AF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


My question would be where are you obtaining the drivers you are using?

 

[pankozin]

Here is what WhoCrashed reports on your minidumps:


#1
crash dump file: C:\WINDOWS\Minidump\110514-20576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x15CFDA, 0x2, 0x15CED9)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



and #2
crash dump file: C:\WINDOWS\Minidump\110414-40154-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFA8002FDC61B, 0x0, 0xFFFFF80002CBF7AF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


My question would be where are you obtaining the drivers you are using?

Thanks for reply. http://www.asus.com/ru/Motherboards/P8P67_LE/ - drivers are from here. Strange thing, this motherboard was working OK in previous setup with other HDDs videocard and system box! but when i swapped, BSOD appered. BTW i changed memory stick to kingston red 2x4GB, still getting BSODs.

Upd. I reinstalled Win 4 times, coz BSODs, and one of them i used DriverUpdater, but it didnt really help... So i think, if the only thing changed was HDDs in this setup, mb its them causing the prob? Mb i need to throw them away??? anyway, i have SSD for replacement... But there are 2 HDDs, which one i need to throw?? or both....

I updated the link in the first post with screenshots of sys specs and minidumps
Better to post it again for sure
LINK

 

[pankozin]

OS version? Clean install for the new board?

Let us know more about the BSODs when you've used the suggested utility.

I used the utility, but i cant understand the data its providing. So i gave the link to minidump. I done clean install AFTER i inserted a new MB with a CPU, and this MB was working FINE on previous setup... I tried G-skill X-series 2x4gb DRAM, Kingston HypreX Red 2x4GB DRAM, Kingston HypreX Blue 2x8GB DRAM.... Still im feel blue daba dee daba dau (i meant blue screen, if somebody didnt hear this gay song)

 

[sm625]

Make sure your RAM sticks are in the correct positions accordign to the manual. Reset your bios settings and then use XMP for the RAM.

 

[pankozin]

Make sure your RAM sticks are in the correct positions accordign to the manual. Reset your bios settings and then use XMP for the RAM.

Hi. Using XMP already, checked the connectors, cleaned them. It was my first move, when i faced firs BSOD.... As u see, no effect...

thanks for interest, tho:wub:

BTW, I got 75% of BSODs when was downloading smth, and 60% of this 75% i got when trying to download BF4 from origin. just for lulz

 

[Ketchup]

What types of peripherals are you connecting to that PC?

You may want to look in the event viewer and see if it points to any drivers that reporting problems.

Edit: And to take it one step further, what are you getting installed before seeing a blue screen.

Edit 2: you answered my question. See if you can find a better driver for your NIC.

 

[Ketchup]

I was noticing that this board has a navy blue SATA connector that is connected to the Amedia controller. I would recommend not using this one, as the board seems to have plenty of ports coming from the Intel controller.

 

[pankozin]

What types of peripherals are you connecting to that PC?

You may want to look in the event viewer and see if it points to any drivers that reporting problems.

Edit: And to take it one step further, what are you getting installed before seeing a blue screen.

Edit 2: you answered my question. See if you can find a better driver for your NIC.

What is event viewer? )

i just installed drivers from asus and then win updates... Thats all.. I was getting BSODs on every stages of setting up windows. Once i got it when i was downloading win updates... Once when installing them. Once i got two in a row after driver update via DriverUpdater.

 

[pankozin]

I was noticing that this board has a navy blue SATA connector that is connected to the Amedia controller. I would recommend not using this one, as the board seems to have plenty of ports coming from the Intel controller.

I noticed that too, so i disabled marvell controller. Anyway i [lugged two HDDs into 6g SATA ports, coz i read tht this MB has problems with 3g SATA ports...

Upd. I disabled all unused onboard devices in BIOS. moreover, i updated the bios, then i catched a common bug with ME BIOS section, and reflashed ME with MEREFL command under MS-DOS using FTK8 tool.

 

[Ketchup]

So, you are getting BSOD's for day one. Might want to try swapping hard drive and/or it's cable. I might also guess RAM, but it sounds like you may have ruled that out.

 

[pankozin]

So, you are getting BSOD's for day one. Might want to try swapping hard drive and/or it's cable. I might also guess RAM, but it sounds like you may have ruled that out.

Btw, catched another strange bug on this MB. i inserted creative sound card, and it was no sound from it (just abit super quite sound on the threshold of my perception.) this card was working ok on 3 other PC setus.. So i manually set permissions to USER category in registry to folder MMDevices, and it worked... Mb its not related, but i never seen such weird bug before... and only on this MotherofGodBoard...

As for HHDs, i tried to swap them, and have installed original SATA 6G cables, but it was useless.
As for RAM, i runned memtest for 2 hours on each stick, and guess what...

Upd, mb the best choice is to plug this Motherboard to a trash can and left it there.

 

[mikeymikec]

I'm wondering whether we should try more basic techniques; memtest86 has already been tried, perhaps half an hour with Prime95? What are the system temps like when idle and under load?

BSODs 1 & 2 could point at RAM but I understand you've swapped out the RAM on multiple occasions so RAM itself seems unlikely, but perhaps it's how the system is communicating with the RAM that is the problem.

 

[pankozin]

I'm wondering whether we should try more basic techniques; memtest86 has already been tried, perhaps half an hour with Prime95? What are the system temps like when idle and under load?

BSODs 1 & 2 could point at RAM but I understand you've swapped out the RAM on multiple occasions so RAM itself seems unlikely, but perhaps it's how the system is communicating with the RAM that is the problem.

Hello. Ok, i will try Prime95. Temp is quite normal 36-40 idle and 50-65 under load (some games). Btw, i noticed main power cable was mb not properly plugged, - when I accidentally touched it, my soundcard did make strange noises (like clapping), like it was voltage drop. So I plugged the cable once again, and soundcard was quite ok after this.:whiste:

 

[mikeymikec]

Hello. Ok, i will try Prime95. Temp is quite normal 36-40 idle and 50-65 under load (some games). Btw, i noticed main power cable was mb not properly plugged, - when I accidentally touched it, my soundcard did make strange noises (like clapping), like it was voltage drop. So I plugged the cable once again, and soundcard was quite ok after this.:whiste:

Yep, temps sound fine. The cable is a bit worrying, it would be nice if that was the cause of your overall problems

 

[sm625]

Strange thing, this motherboard was working OK in previous setup with other HDDs videocard and system box!

Either you damaged the board in transit, or it "doesnt like" the way it is installed currently. Take the motherboard out of the case and place it on a nonconductive surface. Will it run stable when the pieces are sprawled all about your desk? If not, then you probably damaged it, perhaps via ESD.

 

[pankozin]

Either you damaged the board in transit, or it "doesnt like" the way it is installed currently. Take the motherboard out of the case and place it on a nonconductive surface. Will it run stable when the pieces are sprawled all about your desk? If not, then you probably damaged it, perhaps via ESD.

Im reflecting on such probability. When i mounted the board for the first time, it couldnt boot, coz one of the screws (lower right) was screwed into nothing (coz holder with screw-thread was absent, mb its just fall off, coz pc case is old) and was messing the grounding. So i just removed the screw, and it was ok.
Another thing, during mounting i just took the board with power module (didnt disconnect the cables out of the board) out of one PC and placed it into another. I putted the board with the module on the edge of the case, and when was messing to dismount old board, I accidentally pushed the power module of the new one, and it felld from the pc, dragging the connected main cable with it. As the height of the lying on its side case isn’t much, the cable just slightly yanked the socked. So… mb it was the problem, im not sure tho

 

[pankozin]

Yep, temps sound fine. The cable is a bit worrying, it would be nice if that was the cause of your overall problems

Hm, i have catched no BSODs from yesterday evrening (after reattaching the cable). Mb it was the case.... Sounds kinda to easy, but it is Spart... i mean PC.:biggrin:

UPD.
http://www.pcadvisor.co.uk/how-to/pc...-power-supply/
"Dust build-up can also reduce the life of the PSU. Symptoms are usually intermittent, and include unexpected reboots, startup failures, USB device failures, and hard-disk or memory errors. These issues often mysteriously fix themselves, only to return later."

So mb it was memory error due to power cable issue?????

 

[mikeymikec]

If the supply of power isn't smooth, the components aren't going to like it. Admittedly I would have thought you would have experienced far greater and more obvious instability issues with your current situation, but for example bad caps are another way for components to get a unstable supply of power, and depending where those caps are, you get different results. For example, on one occasion I saw bad caps near the IDE ports, and the system would POST but not if anything was connected to the IDE channels.

 

[pankozin]

If the supply of power isn't smooth, the components aren't going to like it. Admittedly I would have thought you would have experienced far greater and more obvious instability issues with your current situation, but for example bad caps are another way for components to get a unstable supply of power, and depending where those caps are, you get different results. For example, on one occasion I saw bad caps near the IDE ports, and the system would POST but not if anything was connected to the IDE channels.

All caps are ok, I think (they were "tested" on previous setups). But bottom right cap is missing, coz there is no screw-thread on MB platform. I just can’t do nothing with this but buying new PC case with a new platform... As I described, this bottom right cap opening, if the cap is inserted, is causing PC boot failure (it just won’t boot, or works for half a second and shuts down).

 

[mikeymikec]

I only mentioned bad caps as an example of what might happen when an erratic flow of power reaches system components.

 

[silicon]

All caps are ok, I think (they were "tested" on previous setups). But bottom right cap is missing, coz there is no screw-thread on MB platform. I just can’t do nothing with this but buying new PC case with a new platform... As I described, this bottom right cap opening, if the cap is inserted, is causing PC boot failure (it just won’t boot, or works for half a second and shuts down).

can you post a picture of this missing cap at the bottom right?