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

25 May 2011   #1

Windows 7 Ultimate x64

Hey i am new here. Just joined! I was wondering if anyone could help me solve some BSOD's i was having. Thanks in advanced!

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64
- the original installed OS on the system? I built this pc so there was no preinstalled OS
- an OEM or full retail version? Full Retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? I purchased the Hardware in April of 2009
- What is the age of OS installation (have you re-installed the OS?) I just reinstalled 2-3 hours ago.

CPU: AMD Atholon x2 5200+
Ram: G-Skill 4gb ddr2 800mhz
Hard Drive: Western Digital 320gb 7200rpm (I don't remember all of the specs.)
Motherboard: Asus m3a78-CM
PSU: 585w orion (i think)

My System SpecsSystem Spec
26 May 2011   #2

Windows 7 Ultimate x64

got more BSOD's new ones will post tomorrow. someone please reply because my computer restarts every 10-20 mins
My System SpecsSystem Spec
27 May 2011   #3

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64

One of your drivers caused this error, not much information was given.
An attempt was made to execute non-executable memory.

Enable driver verifier, follow the instructions in the below tutorial.

Driver Verifier - Enable and Disable

This will help find the driver.
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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.
Arg1: fffff880009e9180, Virtual address for the attempted execute.
Arg2: 80000000001a1963, PTE contents.
Arg3: fffff88006dd0920, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
PROCESS_NAME:  chrome.exe
TRAP_FRAME:  fffff88006dd0920 -- (.trap 0xfffff88006dd0920)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff96000370100 rbx=0000000000000000 rcx=fffff900c01ff00f
rdx=fffff900c06b1210 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880009e9180 rsp=fffff88006dd0ab8 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff96000166f98
r11=fffff900c1b3d520 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff880`009e9180 801f00          sbb     byte ptr [rdi],0 ds:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002943e9f to fffff800028c4f00
fffff880`06dd07b8 fffff800`02943e9f : 00000000`000000fc fffff880`009e9180 80000000`001a1963 fffff880`06dd0920 : nt!KeBugCheckEx
fffff880`06dd07c0 fffff800`028c2fee : 00000000`00000008 fffff900`c06b1210 00000000`00000000 fffff800`028cadda : nt! ?? ::FNODOBFM::`string'+0x42567
fffff880`06dd0920 fffff880`009e9180 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`06dd0ab8 fffffa80`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : 0xfffff880`009e9180
fffff880`06dd0ac0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`739c2450 : 0xfffffa80`00000000
nt! ?? ::FNODOBFM::`string'+42567
fffff800`02943e9f cc              int     3
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42567
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  ntkrnlmp.exe
FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+42567
Followup: MachineOwner
Run Disk Check

How to Run Disk Check in Windows 7
 Log Name: System
 Source: Microsoft-Windows-WER-SystemErrorReporting
 Date: 2011-05-25T17:56:53.000
 Event ID: 1001
 Task: N/A
 Level: Error
 Opcode: N/A
 Keyword: Classic
 User: N/A
 User Name: N/A
 Computer: JEFF-PC
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff880078bd088, 0xfffff880078bc8e0, 0xfffff800026e84f5). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052511-29140-01.
My System SpecsSystem Spec

06 Jun 2011   #4

Windows 7 Ultimate x64

i just did both of those things. what is my next step?
My System SpecsSystem Spec
06 Jun 2011   #5

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64

What were the results of the Disk Check?

Use your computer normally, driver verifier will stress your drivers and find the ones that are failing.
This will give you a BSoD, when this happens post the complete zip files again.

Run driver verifier for 24 hours, if you don't get any crashes then disable it and report here.
My System SpecsSystem Spec


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 01:45.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App