BSODS while Streaming and playing Battlefield 3

[Deathbringerrr]

Hi guys this is driving me up a wall.. I have had BSODS for the past 2 months or so. I have done everything from memtests to chkdsks to driver verifier. I only get crashes when im streaming BF3. I was getting crashes while playing it but i updated my video drivers a few times the driver sweeper way and it started to work. now i cant stream and play at the same time. I have played Skyrim for 4 hours straight and get no bsods what so ever

Memtest comes back with no errors, and driver verifier crashes while streaming it but just artifacts and feezes and doesnt restart so its not making mindumps.
I have windbg x64 and i learned sorta kinda how to read and load drivers and analyze. but maybe you guys can help me figure this out.

I have also scanned my pc with Malwarebytes twice and i have MSE. everything comes back clean.

i have tried updating everything. Do you think its a bad video card. i uploaded the minidump.rar it includes all bsods and my dxdiag inside.
please someone help me. I finally set my stream the way i want it to go and Crysis 3 open beta is coming soon and i want to stream that.

Edit: sorry guys i read the rules before posting but thought the dxdiag and dumps would help i have now uploaded the right stuff. sorry.

 

[Deathbringerrr]

Bump. no one can help?

 

[ickymay]

my first suspect would be power Supply or Overheating, please add your full system specs in your profile here and make sure your make and model of PSU and Ram is there.

Also please monitor your temperatures and post them here, comparing idle with Stress tested.

 

[Deathbringerrr]

ASUS M4A785TD -M-EVO
AMD Phenom II x4 960T 3.0ghz
ATI MSI HD5670 OC Edition 1GB GDDR5
2x1GB 1600mhz PC12800 DDR3 Gskill OC Edition F3 -12800CL9 -1GBNQ/ 2x2GB Gskill Ripjaws 1600mhz Pc12800 DDR3 F3-12800CL9-2GBRL
DA Series Diablotek 400w PSU PSDA400 (Newegg - Newegg.com - Diablotek DA Series PSDA400 400W ATX12V Power Supply)

500Gb WD Blue Caviar 7200 rpm Sata II


Temps are normal ive checked this before my Graphics was getting 65-68C on max load i cleaned old thermal paste and dust and reapplied new thermal past and now its barely hitting 53C on max. Idle its about 44C. No overheating of anything in the pc, the side case is always open.

 

[Dsprague]

Please update your video card drivers from Here, please also check for any updates to your network drivers Here

I also notice you have a known blue screen causer in your drivers:

ASACPI    fffff880`045d5000    fffff880`045dd000    Sun Mar 27 22:30:36 2005 (42476c4c)    00003c77        ASACPI.sys

Its an ASUS driver for some of their bloat ware that comes with their mother boards, though I noticed you didn't have any of it installed, so I'm wondering if simply deleting the driver would be ok? Or you can check their download section Here to see if there are any updates for the driver.

 

[ickymay]

I seriously doubt your PSU is up to the job and if this was my build I would use at least a bronze certified 500W like a corsair but would prefer a 600w for some headroom.

I reckon you need at least 330w ish so as a guide check your required power usage with this calculator.

Mixing and matching Ram is not a great idea although you can sometimes get away with it and I also suggest try removing the 2x1Gb Gskill OC edition and see if you can still get the crashes ?

 

[Deathbringerrr]

I actually have a 600 w Diablotek(yeah im not buying those anymore) and when i plug it in and flip the switch at the back the computer stays on so i think thats fried. I have tried removing the 1gb sticks and still it happens. i just tried putting that 600 w in there and it still stays on even though the pc is shutdown. I had a lot of dust in the 400w psu so i blew that all out(might be overheating) I also have updated my video drivers like 6 times already with the driver sweeper solution, is there anything different about the new fusion sweeper as im using an old build of driver sweeper? I know mixing ram is a bad idea but i figured if they were the same freq and mhz and manufacturer then wth right? Ive used a different calculator like that before and it told me 330 like you said, but ill try this one. I think i might have to RMA that 600w Power supply since its going on the last year of its warranty. I used to have that asus garbage in my pc but i then removed it on the last windows install. Thats weird that its in there. Thank you guys. Ill post back with all the results.

 

[x BlueRobot]

[COLOR="Red"]WHEA_UNCORRECTABLE_ERROR (124)[/COLOR]
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, [COLOR="Blue"]Machine Check Exception[/COLOR]
Arg2: fffffa80061ad8f8, [COLOR="SeaGreen"]Address of the WHEA_ERROR_RECORD structure.[/COLOR]
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80061ada08
Section       @ fffffa80061adb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR="Red"]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)[/COLOR]
  Status      : 0xfa00000000070f0f

The address of the WHEA strucuture points to an error regarding the FSB, although the error was produced by MCE, which means the CPU detected a hardware error and then reported it to the operating system, resulting in a Stop 0x124 bugcheck.

It is best to stress test the CPU for confirmation:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Enable "Round off checking" before the test (see first post below tutorial).

If the test produces no errors, it is best to use these steps:

• http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

All the hardware seeming to be running stable and tests reporting no errors, could mean a bad motherboard.

 

[Deathbringerrr]

In the event viewer it always says my hdd has a bad sector. ive run chkdsk mutliple times and repaired it. Could this be an issue? Im thinking it is. I will run Prime95 and report back results.

 

[x BlueRobot]

If the bad sector has been repaired, then it would have been a soft bad sector, however, we can test the hard-drive after seeing the Prime95 results.

 

[Deathbringerrr]

Im sorry its saying bad block... I havent got a chance to run prime 95 yet ive been busy so ill do that today sometime.

 

[x BlueRobot]

Event Log:

[COLOR="SeaGreen"]Event[7977][/COLOR]:
  Log Name: System
  Source: [COLOR="blue"]Disk[/COLOR]
  Date: 2012-12-03T00:44:13.416
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DeathMachine
  Description: 
[COLOR="red"]The device, \Device\Harddisk0\DR0, has a bad block[/COLOR].

[COLOR="seagreen"]Event[7978]:[/COLOR]
  Log Name: System
  Source: [COLOR="Blue"]Ntfs[/COLOR]
  Date: 2012-12-03T00:46:09.886
  Event ID: 130
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DeathMachine
  Description: 
[COLOR="Red"]The file system structure on volume C: has now been repaired[/COLOR].

Your file system became corrupted for some reason (hard bad sectors?) and then was repaired by Windows successfully, it is best to such circumstances to test the hard-drive instead.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

:info: Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[Deathbringerrr]

I actually did the chkdsk /f/r last night and it fixed two files one was in the windowsxs(whic is side by side config if im not mistaken) it was a natural llanguage file. .and it fixed a file in my skyrim directory.. When i run sfc/scannow it always tells me it cant fix some files and that winsxs file is in the logs for sfc. I wonder if this hdd is causing all my problems corrupting system files and what not. im about to run prime95 here in a bit.I havent checked to see if i get bluescreens while streaming yet. I also updated my chipset driver.

 

[x BlueRobot]

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Sometimes you will need to run the command 3 times with reboots in order to repair the files, you could also try using it at boot.

A failing hard-drive could start to cause problems, please run the hard-drive tests as specified in my post; you may postpone the testing with Prime95 for now.

 

[Deathbringerrr]

Im sorry i have been really busy lately with family stuff,but I have found the cause of my issue. When i put my new thermal paste on my Processor, i didnt seat it down all the way properly, which i thought it was,because on my mother board the arm for the processor doesnt stand all the way up. I have to hold it up. I did this and it seated itself the right way,there were also a few bent pins i had to credit card back in place. No Bsods. Stupid me! I guess next time i will quality check my work a little better. Thank you for your help! You guys are the best forum so far for problem solving and help. I also reseated my GPU since the Last bsods were Dxgmms1.sys and graphic related drivers. Either one has helped me. Im guessing it was cpu though.

 

[x BlueRobot]

That's good to know, you may leave this thread open for about a week, and then mark it has solved