Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD help!

08 Aug 2010   #11

Windows 7 ulitmate x64

loved the help I got here but I hate to be here again.....after deleting the tuner drivers the blue screens continued so I formated the computer, after a clean install and installing just a few essentials Im back here again because I get the same exact result BSOD again any help greatly appreciated.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\kewljoe\Documents\BSOD\080610-16520-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Fri Aug  6 22:41:52.095 2010 (UTC - 5:00)
System Uptime: 0 days 0:18:45.875
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 101, {61, 0, fffff880009e7180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

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

An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arg1: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e7180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

Debugging Details:






fffff880`02f394c8 fffff800`02a27443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e7180 : nt!KeBugCheckEx
fffff880`02f394d0 fffff800`02a81cf7 : fffffa80`00000000 fffff800`00000001 00000000`00002711 fffff800`02baa4b1 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`02f39560 fffff800`02fef895 : fffff800`03014460 fffff880`02f39710 fffff800`03014460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`02f39660 fffff800`02a75af3 : 00000000`98e0d694 fffff800`02bf3e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`02f39690 fffff800`02aaec91 : 000067ee`00000000 fffff800`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`02f39820 fffff800`02a8752c : 00000000`00000000 00000000`0000009e 00000000`00000000 fffff800`02c08888 : nt!KxFlushEntireTb+0x91
fffff880`02f39860 fffff800`02a8d670 : 00000000`0000009e 00000000`00000001 00000000`00000000 00000000`0000009a : nt!KeFlushMultipleRangeTb+0x28c
fffff880`02f39930 fffff800`02afb99e : fffff800`02c05b40 fffff880`00000001 00000000`00000001 fffff880`02f39bb0 : nt!MiAgeWorkingSet+0x651
fffff880`02f39ae0 fffff800`02a8dde2 : 00000000`0000045d 00000000`00000000 fffffa80`00000000 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x49716
fffff880`02f39b80 fffff800`02a8e06f : 00000000`00000008 fffff880`02f39c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`02f39bd0 fffff800`02d1ea86 : fffffa80`03d0c040 00000000`00000080 fffffa80`03cedb30 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`02f39d40 fffff800`02a57b06 : fffff800`02bf3e80 fffffa80`03d0c040 fffff800`02c01c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02f39d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16



FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image




Followup: MachineOwner

My System SpecsSystem Spec
08 Aug 2010   #12

Windows 7 Ultimate 32 bit

My System SpecsSystem Spec
12 Aug 2010   #13

Windows 7 ulitmate x64

thanks for all the advice again, I think I got this beat a coupple of months ago I was doing some PC cleaning and I removed the heatsink from the CPU but I never got new compound so I thought Id go back to it later, later being I never did. Thanks to your recomendations I started looking at CPU temp and I remembered about the compound, bought it slapped it on and I was able to have a normal gaming session for 20mins w/ all details on high and no blue screens. (before it wouldnt even get to 5 mins) so again thanks!
My System SpecsSystem Spec

12 Aug 2010   #14

Windows 7 Ultimate 32 bit

Ah, heat will definitely do it. Good thinking and a good fix. Thank you for posting your results and letting us know. Glad to hear you are running smoothly. :)
My System SpecsSystem Spec

 BSOD help!

Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:26.
Twitter Facebook Google+