Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD while running Windows Experience Index


  • Please log in to reply
3 replies to this topic

#1 karaoke99

karaoke99

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:20 AM

Posted 26 January 2013 - 11:44 AM

I upgraded my hardware myself (new motherboard, CPU and RAM) and had to reinstall the operating system. I have a student copy of the upgrade version of Windows 7 Ultimate 64-bit. I had to slipstream Windows XP to get SP3 on it in order to use the Win7 upgrade, but I got it working alright.

A couple of times since I finished installing Win7 64-bit last night, I have had the computer lock up on me while in the middle of downloading stuff (Guild Wars 2 files, Windows critical updates, etc.) forcing me into performing a hard reboot. Also, I get the blue screen of death while running the Windows Experience Index. I am hoping they are related. That's where you fine people come in, if you would be so kind.

Here is the minidump data from WinDBG if it will help. Please let me know if you can help and if you need anything else from me. Thanks.
_______________________

Microsoft ® Windows Debugger Version 6.2.9200.16384 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\New folder\012613-14929-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17118.amd64fre.win7_gdr.120830-0334
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c50e70
Debug session time: Sat Jan 26 09:31:51.879 2013 (UTC - 6:00)
System Uptime: 0 days 0:02:46.362
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {fffff8a009f21e20, c3300003caa26963, fffff88002790940, 2}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+41997 )

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

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

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a009f21e20, Virtual address for the attempted execute.
Arg2: c3300003caa26963, PTE contents.
Arg3: fffff88002790940, (reserved)
Arg4: 0000000000000002, (reserved)

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xFC

PROCESS_NAME: WinSAT.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88002790940 -- (.trap 0xfffff88002790940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002790af8 rbx=0000000000000000 rcx=fffff8800a897b40
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8a009f21e20 rsp=fffff88002790ad8 rbp=fffff8a009a7b950
r8=fffff8a009f24000 r9=0000000000000008 r10=fffffa800cdb3200
r11=00000000001f0003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff8a0`09f21e20 3190150d80fa xor dword ptr [rax-57FF2EBh],edx ds:fffff87f`fcf9180d=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002b038af to fffff80002a845c0

STACK_TEXT:
fffff880`027907d8 fffff800`02b038af : 00000000`000000fc fffff8a0`09f21e20 c3300003`caa26963 fffff880`02790940 : nt!KeBugCheckEx
fffff880`027907e0 fffff800`02a826ae : 00000000`00000008 fffff8a0`09f21e20 00000000`00000000 fffff800`02d7c362 : nt! ?? ::FNODOBFM::`string'+0x41997
fffff880`02790940 fffff8a0`09f21e20 : fffff8a0`09a7b920 fffffa80`116ebaa0 fffff800`02d749d6 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`02790ad8 fffff8a0`09a7b920 : fffffa80`116ebaa0 fffff800`02d749d6 00000000`00000000 fffff800`02d749e2 : 0xfffff8a0`09f21e20
fffff880`02790ae0 fffffa80`116ebaa0 : fffff800`02d749d6 00000000`00000000 fffff800`02d749e2 fffff8a0`09f21e20 : 0xfffff8a0`09a7b920
fffff880`02790ae8 fffff800`02d749d6 : 00000000`00000000 fffff800`02d749e2 fffff8a0`09f21e20 fffffa80`0d159030 : 0xfffffa80`116ebaa0
fffff880`02790af0 fffff880`02790ca0 : fffffa80`116ebaa0 fffff800`02d9e99f 00000000`00000000 00000000`00000002 : nt!ObReferenceObjectByHandleWithTag+0x356
fffff880`02790bc0 fffffa80`116ebaa0 : fffff800`02d9e99f 00000000`00000000 00000000`00000002 fffffa80`0cdb3200 : 0xfffff880`02790ca0
fffff880`02790bc8 fffff800`02d9e99f : 00000000`00000000 00000000`00000002 fffffa80`0cdb3200 fffff880`02790c01 : 0xfffffa80`116ebaa0
fffff880`02790bd0 fffff800`02a83813 : fffffa80`116ebaa0 fffffa80`0d159060 00000000`00000000 fffffa80`0d323710 : nt!NtClearEvent+0x3f
fffff880`02790c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+41997
fffff800`02b038af cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+41997

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 503f857d

FAILURE_BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+41997

BUCKET_ID: X64_0xFC_nt!_??_::FNODOBFM::_string_+41997

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

BC AdBot (Login to Remove)

 


#2 karaoke99

karaoke99
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:20 AM

Posted 26 January 2013 - 11:59 AM

Here is the WhoCrashed analysis if it helps. I am not sure what to make of it myself or what steps to take next:


System Information (local)
--------------------------------------------------------------------------------

computer name: HERZBRECHER
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX™-8320 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17158397952 total
VM: 2147352576, free: 1973522432




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 1/26/2013 3:31:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\New folder\012613-14929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xFC (0xFFFFF8A009F21E20, 0xC3300003CAA26963, 0xFFFFF88002790940, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 1/26/2013 3:31:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012613-14929-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xFC (0xFFFFF8A009F21E20, 0xC3300003CAA26963, 0xFFFFF88002790940, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 1/26/2013 3:31:51 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xFC (0xFFFFF8A009F21E20, 0xC3300003CAA26963, 0xFFFFF88002790940, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 1/26/2013 3:29:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012513-10405-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,752 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:01:20 AM

Posted 26 January 2013 - 12:43 PM

If you haven't installed SP1 this would be the first thing that I would do.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#4 karaoke99

karaoke99
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:03:20 AM

Posted 26 January 2013 - 12:56 PM

If you haven't installed SP1 this would be the first thing that I would do.


Thanks...that update wasn't showing up for me at the time, but it is there now. Will report back if anything else goes wonky.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users