BSOD usually while streaming using OBS, Bugcheck code: 0xD3, wdf01000

Hi there,

I've spent a lot of time trying to diagnose what's causing random BSOD and crashes on one of our PCs we use to stream to Twitch. Frankly I've wasted so much time already it's time to see if anyone can see something of value from these dump files. These are the latest dumps from a reformatted Windows 7 Home Premium SP1 x64, as many of the latest drivers I could find for graphics/mobo/etc, all windows updates, and removed the SSD we thought could have been causing the issue.

We have run stress tests and checks using Memtest86, prime95, furmark and so on. Even with both GPU and CPU at 100% it didn't crash or produce errors yet will crash at a random point and usually fairly quickly with streaming but other times when just playing a game. I believe this rules out the PSU, CPU, GPU, overheating, and memory but perhaps the hard drive is at fault? I couldn't seem to get WinDbg setup to tell me more information and WhoCrashed's information is pretty vague. BIOS is at the latest version for the motherboard too. If there's any more information that would help please let me know.

In the past the BSOD errors have been relating to IRQL, or mention "A clock interrupt was not received on a secondary processor within the allocated time interval", but with these recent dumps on the newly installed W7, the errors have changed again.

Attached is the output from DM Log Collector. Any help in narrowing down the source/s of these errors would be very helpful. It's possible it's hardware related but ideally I need to know which part so I don't waste more time and money.

Jam.

axe0 said:

Hi SirJam,

Welcome to the 7forums.

It seems the CPU is reporting an error with the internal timer.
What are the temps from your CPU when idle and under load?
If you are overclocking anything, revert back to stock while troubleshooting.
Please make sure your BIOS is set for default settings.

Code:

5: kd> !errrec fffffa801076c028
===============================================================================
Common Platform Error Record @ fffffa801076c028
-------------------------------------------------------------------------------
Record Id     : 01d0f904504c1063
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/27/2015 15:12:49 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa801076c0a8
Section       @ fffffa801076c180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa801076c0f0
Section       @ fffffa801076c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000005
CPU Id        : c3 06 03 00 00 08 10 05 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa801076c240

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

Error         : Internal timer (Proc 5 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x0000000000a0541e
  Misc.       : 0x0000000000a0541e

42C idle, while running Prime95 I believe temps plateaued around 70C or there abouts.

only 'overclock' is the XMP profile for the memory, and we've had crashes with or without that enabled. BIOS is pretty much at default other than very generic settings like HDD mode and the above profile.

axe0 said:

Please replace the thermal paste properly and clean the heatsink if not done already.

Could you expand on why you think it's overheating? As explained in my original post, we had multiple GPU and CPU stress tests running, some at the same time and neither of these caused any crashes or brought on any overheating messages from the motherboard even after 1-2 hours. While the CPU is using the stock cooler, ideally I really don't want to mess with cleaning off the thermal paste or changing the cooler unless 100% necessary. Were there no other errors? Are there any known bad windows updates that may be hindering rather than helping? It's more probable we have a dodgy processor and haven't nailed it down to that when I built the PC but would appreciate more suggestions.

Running Prime95 as I type this and it's hovering at 67-68 and the Tcase is 74.04C