PC is BSODing after buying new hardware, please help!

Toggle sidebar Toggle sidebar
Zaneisback

Zaneisback

Reputable
Jun 8, 2014
71
0
4,640
My PC has been BSODing for the past few months (Ever since I got a new graphics card and motherboard) and I have updated all of my drivers, updated my Motherboard's BIOS, and did a fresh install of Windows 8.1. The BSOD occurs sporadically and randomly and there is often a different error each time. I've gone a full month without a BSOD and then I got 5 in a day. Please help I don't want to think I bought $500 worth of junk.

Build:
Motherboard: MSI 970 gaming am3+(New Motherboard)
Graphics Card: MSI 760 4G/OC TF (New Card)
CPU: AMD FX-8350
2nd Graphics card (To output to another monitor): PNY GT-430
PSU- RS-750-ACAA-E3
Case- CM 690 II advanced
 
Sort by date Sort by votes
nirjhar mistry

nirjhar mistry

Honorable
Jan 14, 2014
94
0
10,640
What is the error code giving you exactly during BSOD or you may download this software from this link to view the exact driver which is responsible for that error. If you see it's due to BWCW8X64.sys driver then you have problem with killer lan driver.
 
Upvote 1 Downvote
Zaneisback

Zaneisback

Reputable
Jun 8, 2014
71
0
4,640

That does not seem to be the case and honestly I was hoping it would be. I've been ruling out hardware one by one, and now it's down to my graphics card, but I may be wrong. The files highlighted in red are:
hal.dll
ntoskrnl.exe and
ucx01000.sys

If you know what this might mean please tell me right away, but I really appreciate it man. (Also sorry for not replying to the thread I kind of fell off the face of the earth for a while.)


 
Upvote 0 Downvote
nirjhar mistry

nirjhar mistry

Honorable
Jan 14, 2014
94
0
10,640


ntoskrnl.exe seems to be a RAM issue and ucx01000.sys is definitely a USB driver issue .
Check your RAM first,RUN sfc/scannow or repair your computer for USB issues. Hope that'll help.
 
Upvote 0 Downvote
Zaneisback

Zaneisback

Reputable
Jun 8, 2014
71
0
4,640

I tried sfc/scannow and it said that it found no integrity violations. I was reading elsewhere that it may be a problem with the voltage regulator in my motherboard or powersupply. And I'm fairly certain it wasn't my RAM since there seemed to be no issue with my it when I last checked it with the memory diagnostics tool. On another note thank you again for the help, I'm learning a lot from this.

 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom