Windows 7: New MoBo, CPU, RAM, Memory-related BSODs ever since

apmanley · 08 Oct 2012

Hey everyone, I'm at my wit's end. I recently bought a new BioStar TZ77B motherboard, i5 3470, and 8 gigs of Patriot ram. I installed them with my hard drive and graphics card (Radeon HD5570, made by Sapphire). Ever since I have been having BSODs, almost all related to memory in some way (Page fault in not paged area, memory management, etc.)

I've run Memtest86+ for 10 hours with no errors found, so I don't believe it is a hardware malfunction RAM wise. WhoCrashed has said that all the errors are either a) Kernel errors, or b) a rogue driver. I've done 2 re-installations of Windows (I'm running 7 Ult. 64), yet the BSODs continue. As such I am lead to believe it is a driver. That said, I do not know which one. Any help would be greatly appreciated.

Thanks!

ICit2lol · 09 Oct 2012

Hello apmanley and welcome. Now from how I read your post you have renewed everything except the hard drive and the graphics card?

Now my next query is was the OS originally installed on the HDD while it was still used with the old mobo? Because if it was the OS (original) installation is tied to that old board. It is not tied to your HDD and when you fire up the new build then you should get a message to say the OS is not a genuine copy. .

Why it is blue screening I don't know but could possibly be connected in some way to this situation perhaps because of some corrupted items on your HDD.

I think personally you would have been better off buying a new drive and an OEM 7 of a version you like and then transferring your data from the old to the new drive. You would then have had in effect a new machine for the cost of a new drive and OEM and only need to have done that transferring.

apmanley · 09 Oct 2012

Thanks for the response. The HDD is less than a year old, and the graphics card is about a year and a half. I'm not sure why the windows would have been tied to my old Mobo as I had reinstalled it after connecting the HDD to the new system.

ICit2lol · 09 Oct 2012

So just so I have it right the OS is a new one and not the one you installed on the old mobo?

If it is the same disk (CD) and it was originally installed on the old mobo then it will be tied to the old mobo.

You can if you like contact Microsoft and explain that the old mobo you originally installed on is dead and you have had to renew the mobo. They might just let you reset the OS to be installed on the new mobo.

I did this just a month ago with a 32bit OS I had on a desktop mobo that died and I installed that OS to a laptop and then Microsoft took me through few steps to activate the OS onto the laptop mobo.

Britton30 · 09 Oct 2012

If your OS is an OEM version it is tied to the computer it is first installed in, usually forever.
If a retail version it can be reinstalled several times as long as it it not active on more than 1 machine.

Did you install all the BioStar drivers from you boards support page?

To help us help you would you please add your systems specs? Here's how: System Info - See Your System Specs
Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built.

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.
After doing this your specs will be available in each of your posts. Click on mine in the lower left to see how it should look.

Full instructions in the tutorial.

ICit2lol · 09 Oct 2012

Yep I agree Gary the OS I referred to was an OEM that I put onto a refurbish job. I guess I got lucky with M$.

But what I was thinking was if the COA can be ID'd via say Speccy or SIW do you think that apmnaley could download the same version 7 ISO fresh install the OS from that and then activate using that code from the Speccy search?

Britton30 · 09 Oct 2012

Yes that should work but the new board may not let it activate without a call to MS. It also should be checked against the code on the OEM sticker, if that applies.

apmanley · 09 Oct 2012

My apologies, I misunderstood your response.

This was not a preinstalled copy. So I do not believe OEM software would apply. I was able to finish applying all the windows updates from my last reinstall, and to the best of my knowledge, all the Biostar drivers have been applied (downloaded from: TZ77B :: Motherboard :: BIOSTAR). I updated the diagnostic tool (see attached) to account for the more recent updates, and more recent crashes.

Thanks.

Britton30 · 10 Oct 2012

Some hardware tests to run.

Graphics card:
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html#post866972

Hard drive(s), pick one for your HDD brand or use Seatools.
7 Free Hard Drive Testing Software Tools

For RAM, this will require memtest on a bootable CD or USB stick.
Memtest86+ - Advanced Memory Diagnostic Tool this should run for a minimum of 7 passes.

This may help, run the steps outlined in this tutorial, Option Two, and reboot the system:
SFC /SCANNOW Command - System File Checker
If that doesn't correct the issue, run it two or more times with a reboot between.
You may get this result:

Code:

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log
The system file repair changes will take effect after the next reboot.

Or a message that no integrity violations were found.
Or that Windows Resource Protection found errors it cannot repair, if so rerun the steps above.

Dave76 · 11 Oct 2012

Run the tests recommended by Britton30.

Your last crashes:

Code:

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
Probably caused by : memory_corruption ( nt!MiAddViewsForSection+11f )
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0xA_nt!MiAddViewsForSection+11f
-----------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Cause: Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsCommonClose+26f - inconclusive
-----------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
corrupted PFN for the page table - This bugcheck usually occurs for one of two reasons, the first reason being memory corruption. If there is a buggy driver in the system that is writing on memory that it does not own.
FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8
-----------------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
Probably caused by : afd.sys ( afd!AfdPoll32+272 )
PROCESS_NAME:  Agent.exe - Windows service, not likely the cause
FAILURE_BUCKET_ID:  X64_0x50_afd!AfdPoll32+272

These look like memory corruption.
Run the memtest86+, mentioned above, leave all RAM cards installed for the first test.
This may take a while, best to run overnight.
If you get any errors you can stop the test.
Continue with the individual RAM card testing as in the tutorial linked above.

With 8GB RAM you may need to make some memory setting adjustments in BIOS.
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Driver that need updating.
BIOS64.sys Sun Jun 08 2003 - Out of date - This is a BIOSTAR I/O driver file, Update from your motherboard support site.

From your System Events Log:

Code:

Event[3455]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2012-10-08T20:17:46.148
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Andrew-PC
  Description: 
ACPI thermal zone ACPI\ThermalZone\THRM has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 0K             
_AC1 = 0K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 399K             
_HOT = 0K             
_PSL - see event data.

There are a lot of these.
This indicates the CPU is ovrheating, check with CoreTemp linked above.

Code:

Event[4032]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-10-08T21:23:45.326
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Andrew-PC
  Description: 
The following boot-start or system-start driver(s) failed to load: 
BIOS
discache
spldr
Wanarpv6

Do you have any Utilities from Biostar?
If you do, un-install them for testing. These are known to cause system crashes.

Let us know if you have any questions.

Windows 7: New MoBo, CPU, RAM, Memory-related BSODs ever since

New MoBo, CPU, RAM, Memory-related BSODs ever since problems?