System Freezes and Then Shuts Down

[limerickred]

Hi, first post here so hopefully someone can help me out.

I recently built my first HTPC and on the odd occasion the system has frozen while watching a movie and then shut down after about 20 or 30 seconds.

It has become more frequent in the last few days and tonight it happened twice while watching a blu ray so need to figure out if I can get it sorted.

Tonight I was watching the BD using TotalMedia Theatre 5 in Windows Media Centre but it has also happened while using Cyberlink PowerDVD 10 and also while wathcing movie files using the WMC player so I cant pin it down to one program and take it from there.

I have attached the zipped files as requested and all the system details are in my profile but if theres anything else needed I will post as necessary.

Windows 7 Home Premium x64 OEM
Corsair 60GB SSD
Seagate 2TB Barracuda
Gigabyte H55N-USB3
Intel Core i3 540
LiteOn DS-4E1S BD Drive

Cheers in advance.

 

[JMH]

Hi, first post here so hopefully someone can help me out.

I recently built my first HTPC and on the odd occasion the system has frozen while watching a movie and then shut down after about 20 or 30 seconds.

It has become more frequent in the last few days and tonight it happened twice while watching a blu ray so need to figure out if I can get it sorted.

Tonight I was watching the BD using TotalMedia Theatre 5 in Windows Media Centre but it has also happened while using Cyberlink PowerDVD 10 and also while wathcing movie files using the WMC player so I cant pin it down to one program and take it from there.

I have attached the zipped files as requested and all the system details are in my profile but if theres anything else needed I will post as necessary.

Windows 7 Home Premium x64 OEM
Corsair 60GB SSD
Seagate 2TB Barracuda
Gigabyte H55N-USB3
Intel Core i3 540
LiteOn DS-4E1S BD Drive

Cheers in advance.

Limerick hi and welcome


The one minidump uploaded was caused by your Rt64win7.sys (NDIS 6.20 64-bit Driver from Realtek Corporation). A simple re-install with the newest version should help the problem.

Let us know if you need further assistance.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\JMH\Desktop\Windows_NT6_BSOD_jcgriff2\030211-9625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e5ce50
Debug session time: Tue Mar  1 22:57:51.714 2011 (GMT-4)
System Uptime: 0 days 8:44:20.135
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003f15a20, fffff80000ba2748, fffffa8008d6c680}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8003f15a20, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa8008d6c680, The blocked IRP

Debugging Details:
------------------

 

[limerickred]

Thanks for the reply JMH.

Will try that and let you know how I get on.

 

[limerickred]

Ok to follow up I updated the driver but had the same issue just minutes ago. After watching a second MKV file in a row I was in the WMC menu when it froze completely and shut down.

I have attached the new reports.

 

[limerickred]

System froze and shut down again tonight while watching a blu ray using PowerDVD 10.

Any help in solving this would be greatly appreciated.

Cheers.

 

[zigzag3143]

Ok to follow up I updated the driver but had the same issue just minutes ago. After watching a second MKV file in a row I was in the WMC menu when it froze completely and shut down.

I have attached the new reports.

It is still being blamed on the Realtek driver but there are other things that might be contributing and they are:

AVG. remove and replace with Microsoft security essentials

AVG - Download tools

http://www.microsoft.com/security_essentials/


Codec packs if installed are frequently a cause.



You can also run driver verifier to determine what is causing the crash

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\030211-9625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c1f000 PsLoadedModuleList = 0xfffff800`02e5ce50
Debug session time: Tue Mar  1 22:57:51.714 2011 (GMT-4)
System Uptime: 0 days 8:44:20.135
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003f15a20, fffff80000ba2748, fffffa8008d6c680}

Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8003f15a20, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa8008d6c680, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8008d6c680

DEVICE_OBJECT: fffffa80066c0050

DRIVER_OBJECT: fffffa80068a46d0

IMAGE_NAME:  Rt64win7.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b8fb8dc

MODULE_NAME: Rt64win7

FAULTING_MODULE: fffff88002f99000 Rt64win7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cfe273 to fffff80002c8f740

STACK_TEXT:  
fffff800`00ba26f8 fffff800`02cfe273 : 00000000`0000009f 00000000`00000003 fffffa80`03f15a20 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`02c9b29e : fffff800`00ba2848 fffff800`00ba2848 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00ba27a0 fffff800`02c9add6 : fffffa80`0717c148 fffffa80`0717c148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00ba2810 fffff800`02c9b4be : 00000049`3fb3aa88 fffff800`00ba2e88 00000000`001ec596 fffff800`02e0d548 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`02c9acb7 : fffff800`02e09ec4 fffffa80`001ec596 fffffa80`066caa28 00000000`00000096 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`02c95865 : 00000000`00000000 fffffa80`03873b60 00000000`00000000 fffff880`054cc588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02c9567c : fffffa80`06b4f000 fffff800`03206895 fffff800`0322b460 fffff880`0262fb40 : nt!KxRetireDpcList+0x5
fffff880`0262fa80 fffff800`02cd9113 : fffff800`02c8bc60 fffff800`02c8bccc 00000000`c0000001 fffff880`0262fb40 : nt!KiDispatchInterruptContinue
fffff880`0262fab0 fffff800`02c8bccc : 00000000`c0000001 fffff880`0262fb40 00000000`00000000 fffffa80`06b4f000 : nt!KiDpcInterruptBypass+0x13
fffff880`0262fac0 fffff880`02fa8e82 : 00000000`00000000 00830000`05000000 00000000`000080ba fffff880`0262fa98 : nt!KiInterruptDispatchNoLock+0x1fc
fffff880`0262fc50 00000000`00000000 : 00830000`05000000 00000000`000080ba fffff880`0262fa98 00000000`00000000 : Rt64win7+0xfe82


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys

Followup: MachineOwner
---------

0: kd> lmvm Rt64win7
start             end                 module name
fffff880`02f99000 fffff880`02ff0000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Mar 04 08:42:52 2010 (4B8FB8DC)
    CheckSum:         000611C5
    ImageSize:        00057000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Other things to investigate. Heat, power, and system conflicts.

 

[limerickred]

Thanks for the reply Zigzag. Ill try out these over the weekend and see how I get on.