BSOD

Ganjamanyeah

New member
Local time
8:55 PM
Messages
12
Location
North Yorkshire
win 7 hp x64 retail, get BSOD not long after bootup, all help appreciated
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self Built
OS
Windows 7 Home Premium x64
CPU
Intel Core i7 4770K
Motherboard
MSI Z87-GD65 GAMING (MS-7845)
Memory
8GB DDR3 Xtreem-LV-2133 2x4GB
Graphics Card(s)
MSI GTX 770 2GB Gaming
Sound Card
ASUS Xonar DGX 5.1
Monitor(s) Displays
Acer G245 24 inch Full HD 120 Hz - edge10 EF240a 2ms
Screen Resolution
1920x1080p
Hard Drives
INTEL SSDSC2CT060A3 60GB
SAMSUNG 250GB 840 SERIES SSD
SAMSUNG F1 1TB
WDC 150 RAPTOR
PSU
Gigabyte Odin 800W
Case
Antec 302 Black Interior
Cooling
3Corsair AF120's,1x140AF,2SP case fans Coolit ALC CPU Cooler
Keyboard
Logitech G15
Mouse
Gigabyte lazer Gaming
Internet Speed
Virgin 120Mb Cable
Antivirus
Webroot Secure Anywhere Complete
Browser
OPERA-FIREFOX-CHROME-MAXTHON
A component, NVIDIA network adapter driver of Nvidia nForce is the cause
Update your nForce driver => Drivers - Download NVIDIA Drivers
If you don't know what your nForce chipset is, please download and install this free program: http://www.cpuid.com/softwares/cpu-z.html
Then, check the "Mainboard" tab to locate the chipset information.
Code:
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80076d7060, fffff80000b9c518, fffffa8009872470}

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


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: fffffa80076d7060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8009872470, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8009872470

DEVICE_OBJECT: fffffa80081df050

DRIVER_OBJECT: fffffa80082a7060

IMAGE_NAME:  nvmf6264.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4afb45e0

MODULE_NAME: nvmf6264

FAULTING_MODULE: fffff8800f04c000 nvmf6264

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d4cb52 to fffff80002ce0640

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d4cb52 : 00000000`0000009f 00000000`00000003 fffffa80`076d7060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02cec062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02cebf06 : fffffa80`09e2ca40 fffffa80`09e2ca40 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02cebdee : 00000001`7b1f2d00 fffff800`00b9cc58 00000000`00009f44 fffff800`02e55b08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02cebbd7 : 00000000`7f0c44c4 00000000`00009f44 00000000`7f0c44cf 00000000`00000044 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cd836a : fffff800`02e52e80 fffff800`02e60cc0 00000000`00000000 fffff880`01003500 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_nvmf6264.sys

BUCKET_ID:  X64_0x9F_IMAGE_nvmf6264.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: fffffa80076d7060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8009872470, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8009872470

DEVICE_OBJECT: fffffa80081df050

DRIVER_OBJECT: fffffa80082a7060

IMAGE_NAME:  nvmf6264.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4afb45e0

MODULE_NAME: nvmf6264

FAULTING_MODULE: fffff8800f04c000 nvmf6264

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d4cb52 to fffff80002ce0640

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d4cb52 : 00000000`0000009f 00000000`00000003 fffffa80`076d7060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02cec062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`02cebf06 : fffffa80`09e2ca40 fffffa80`09e2ca40 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02cebdee : 00000001`7b1f2d00 fffff800`00b9cc58 00000000`00009f44 fffff800`02e55b08 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02cebbd7 : 00000000`7f0c44c4 00000000`00009f44 00000000`7f0c44cf 00000000`00000044 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02cd836a : fffff800`02e52e80 fffff800`02e60cc0 00000000`00000000 fffff880`01003500 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_nvmf6264.sys

BUCKET_ID:  X64_0x9F_IMAGE_nvmf6264.sys

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

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
Windows 10 Pro x64, Arch Linux
CPU
Intel Core 2 Quad Q8200 OC'd 3.08GHz
Motherboard
Asus Rampage formula LGA775
Memory
8GB DDR2 900Mhz
Graphics Card(s)
MSI GT730 2GB GDDR5 (Kepler)
Sound Card
Supreme FX2
Monitor(s) Displays
Samsung LS22F350 LED
Screen Resolution
1080P
Hard Drives
Kingston SSDNow UV400 120GB, 500GB Hitachi, 2TB Samsung, 500GB Seagate FreeAgent, 640GB Samsung, 160GB Toshiba (Arch)
PSU
AeroCool 500W Bronze
Cooling
Cooler Master V6 + 3X fans
Keyboard
Prolink keyboard
Mouse
Logitech M705
Internet Speed
1MiB/s
Browser
Chrome Beta
Back
Top