Sign-in / Sign-up
Your question

BSOD's and Hyper Transport sync errors

Tags:
  • RAM
  • hyper transport sync flood error
  • CPUs
  • Blue Screen
Last response: in CPUs
April 22, 2013 10:16:25 PM

I have an MSI 785GM-P45 mobo with AMD Phenom II x2 560 processor. I've got 12Gigs of ram (2x2Gigs) and (2x4gigs) and AMD Raedon HD7770 Graphics card with 1GB GDDR5. I have 2 HDD's 1 DVD write/rewrite, 1 Blu Ray, 550 Watts PSU.

The issue is for a while I've been getting random BSOD's most having the error msg. Page Fault in NonPaged Area. I was also getting Hyper Transport Sync Flood errors. I Mainly do heavy graphics editing and lots of internet activity (several browser tabs open in two, sometimes three different browsers) and open text editors.

At the time I was getting the Hyper transport I had three sticks of ram. Nothing is oc (now or then) so I thought maybe its because I'm not in dual mode so I got another stick and changed my CPU NB settings to 2200 and put my HT at 1800. I haven't had another Hyper Transport error and I hadn't had any BSOD's for two days (since I put in the Ram) but just now while using both IE and FF (testing websites) I had a page Fault in NonPaged Area crash.

I also did a clean install of Windows 8 pro before installing the ram. Maybe I need to add a fan because I hear my cpu fan running sometimes rather loudly (at least it seems loud to me).

The WhoCrashed report is below. Any help with this would be great. Very Appreciated
----------------------------------------------------------------------
On Tue 4/23/2013 4:14:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042213-50903-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0x50 (0xFFFFFA0020118C6E, 0x8, 0xFFFFFA0020118C6E, 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.



On Tue 4/23/2013 4:14:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA0020118C6E, 0x8, 0xFFFFFA0020118C6E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.



On Sat 4/20/2013 8:02:57 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042013-33602-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x52DA21)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008C714F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


More about : bsod hyper transport sync errors

a b à CPUs
April 23, 2013 4:58:56 AM

PAGE_FAULT BSOD's can be tied to either general system instability, or bad RAM.

WHEA_UNCORRECTABLE_ERROR, however, generally points to an unstable system. I've seen it generated due to bad OC's, overheating, an underpowered PSU, or simply a bad motherboard.

I'm gussing your RAM setup is to blame; non-matched RAM has always been a little finicky, and depending on the timings of each set, I could see these types of problems being generated. So for the sake of testing, remove the 2 2GB sticks and see if the situation improves.
m
0
l