BSOD on idle, but not on load

[mybestshot]

Windows 7 64bit, OEM, all hardware 1 week old, first installation of Windows

My system runs stable on Furmark, prime95 blend and memtest for about 3 hours each, but somehow it BSODs randomly (about once every 4 hours) on idle, please help.

BTW, i couldnt include my crash dump in the .zip, as it's a whopping 95MB even after zipping. how does everyone keep crash dumps small in size?

 

[zigzag3143]

Windows 7 64bit, OEM, all hardware 1 week old, first installation of Windows

My system runs stable on Furmark, prime95 blend and memtest for about 3 hours each, but somehow it BSODs randomly (about once every 4 hours) on idle, please help.

BTW, i couldnt include my crash dump in the .zip, as it's a whopping 95MB even after zipping. how does everyone keep crash dumps small in size?

First configure as below to keep dmp size small. then only include the last 4-5. finally if necessary upload them to a site like rapidshare and place the link here.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[Jonathan_King]

For some reason Minidumps are not being created; the system is set to create small and large dumps, but only the large dump exists.

DebugInfoType=2

I found this error:

Event[195]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2011-04-14T00:47:34.732
  Event ID: 35
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: YANG-PC
  Description: 
Performance power management features on processor 3 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.

I see the BIOS is fairly recent:

BIOS Version/Date    American Megatrends Inc. 4.6.4, 17/2/2011

Download the latest BIOS here: BIOSTAR :: Download

Whether it's actually newer than your current one or not, flash it anyway. Perhaps something is corrupted as it is.

 

[mybestshot]

Thanks for all the help so far. I've taken in all your suggestions and taken steps to prepare myself in anticipation for the next BSOD, which sure enough, arrived when I was playing Civ 5.

I noticed in my temperature logs that leading up to the crash, my C3 (meaning the 4th processor core) temperatures were way higher than my other C2, C1 and C0 (the other 3 processor cores) temperatures, which could allude to a processor power management firmware error noted earlier. Nonetheless, my mobo drivers are definitely updated as I've downloaded them straight from the Biostar website just days ago...

Also, I have a suspicion that it could be the ATI graphic drivers causing problems, as forums are rife with discussion over how the recent 11.x version drivers are causing crashes for a few HD 5xxx cards and how some users are sticking with old 10.10e drivers, which catered exclusively for HD 5xxx series cards during that time.

Anyway I've reconfigured the setup to produce small size mini dumps, so the .zip attachment here comes with all the required parts.

Thanks for all the help, you people are great!

 

[Jonathan_King]

You could try uninstalling your ATI drivers and installing an earlier version; I doubt that's the problem though.

Try flashing the latest BIOS again: BIOSTAR :: TP67B+ :: BIOS

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Apr 14 01:05:22.186 2011 (UTC - 4:00)
System Uptime: 0 days 2:56:09.014
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSwitchContextWithCheck+175 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_dxgmms1!VidSchiSwitchContextWithCheck+175
SystemProductName = TP67B+
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]