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

18 Apr 2013   #1

windows 7 pro x64

My computer has been giving me BSODs quite a bit recently and its really starting to make me so i am going to upload the the minidumps for you guys like it is said in the directions the computer in question is a custom built computer specs on it are

OS: Microsoft Windows 7 Professional 64-bit SP1
CPU: AMD Athlon II X4 640
MB: ECS GeForce6100PM-M2
Graphics card: 1024MB ATI Radeon HD 4650
HDDs: 2795GB Western Digital WDC WD30 EZRX-00MMMB0
466GB Western Digital WDC WD50 00AADS-00S9B

if any other info is needed just let me know any help would be greatly appreciated
now sometimes it will load just fine and be running for intermittent amounts of time then all of a sudden it goes to BSOD then others it wont even load and it will go to BSOD

My System SpecsSystem Spec
18 Apr 2013   #2

Microsoft Community Contributor Award Recipient


Hello Jeff and welcome to Seven Forums.

In going through your latest dump file dated 041813, it appears that several drivers have been flagged. They include nvmf6264.sys (nVidia nForce network driver); nvstor.sys (nVidia Storage Drivers); usbehci.sys (EHCI eUSB Miniport Driver); and amdppm.sys (Processor Device Driver.)

In an effort for full disclosure please be advised that I did condense the dump file to a more manageable size and included only the references to the flagged drivers.

Driver Reference Table - nvmf6264.sys

Driver Reference Table - nvstor.sys

Driver Reference Table - usbehci.sys

Driver Reference Table - amdppm.sys

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000







EXCEPTION_RECORD:  fffff80000b9c3a8 -- (.exr 0xfffff80000b9c3a8)
ExceptionAddress: fffff80002a85749 (nt!KiProcessExpiredTimerList+0x0000000000000129)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000b9c450 -- (.trap 0xfffff80000b9c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800730fd08 rbx=0000000000000000 rcx=bffffa800730fd08
rdx=fffffa8003f7fdc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a85749 rsp=fffff80000b9c5e0 rbp=fffffa8003f7f700
 r8=0000000000000024  r9=0000000000000000 r10=00000000000000f4
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff800`02a85749 48894108        mov     qword ptr [rcx+8],rax ds:bffffa80`0730fd10=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a725fe to fffff80002a7abd0

fffff800`00b9b488 fffff800`02a725fe : 00000000`00000036 fffffa80`077f1160 fffff800`00b9bc00 fffff800`02aa5a90 : nt!KeBugCheck
fffff800`00b9b490 fffff800`02aa575d : fffff800`02c89374 fffff800`02bc62b8 fffff800`02a05000 fffff800`00b9c3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b4c0 fffff800`02aa4535 : fffff800`02bca038 fffff800`00b9b538 fffff800`00b9c3a8 fffff800`02a05000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b4f0 fffff800`02ab54d1 : fffff800`00b9c3a8 fffff800`00b9bc00 fffff800`00000000 fffffa80`0730fd00 : nt!RtlDispatchException+0x415
fffff800`00b9bbd0 fffff800`02a7a282 : fffff800`00b9c3a8 fffffa80`03f7fb50 fffff800`00b9c450 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c270 fffff800`02a78b8a : 00000000`00000000 00000000`00000000 fffff880`040c4000 00000000`00000005 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c450 fffff800`02a85749 : fffffa80`05d2fef0 fffffa80`04f89400 fffffa80`04f89400 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c5e0 fffff800`02a855ce : 00000008`d54204e0 fffff800`00b9cc58 00000000`0003b5f4 fffff800`02bfa108 : nt!KiProcessExpiredTimerList+0x129
fffff800`00b9cc30 fffff800`02a853b7 : 00000002`999089c1 00000002`0003b5f4 00000002`99908908 00000000`000000f4 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a7290a : fffff800`02bf5e80 fffff800`02c03cc0 00000000`00000000 fffff880`04544db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


fffff800`02a725fe 90              nop


SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys

fffff800`00b9b6f8  fffff880`0459f3ae usbehci!EHCI_iEnableAsyncList+0x172

*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys

fffff800`00b9cc68  fffff880`044fc7f2 amdppm!C1Halt+0x2

Followup: MachineOwner
In addition to the usual housekeeping chores that are always recommended (such as running a full scan with your updated anti-virus suite, a second scan with the free Malwarebytes, checking all cables, plug-in modules, etc), I would also suggest going to the driver websites and see if you have the latest drivers. If you do, it's possible that an earlier version of the same driver may play nice wih your machine.

I'd also check for any other damaged or corrupt system files by running a system file checker scan from an elevated command prompt (option two.) If problems are found, run the scan 3 times and immediately reboot the computer after each scan.

SFC /SCANNOW Command - System File Checker
My System SpecsSystem Spec
18 Apr 2013   #3

windows 7 pro x64

how do i get updated drivers for these items?
My System SpecsSystem Spec

18 Apr 2013   #4

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit

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 20:50.
Twitter Facebook Google+