BSOD while web browsing and after restoring from Sleep mode

[koolkat77]

Okay..the reoccuring BSOD-s every 2/3 days point toward hardware problem. I'm afraid you will have to take the laptop back to the place you purchased it from. But lets see if driver verifier or a clean install of windows helps in anyway.

 

[generalerror]

Could it be related to some RAM mismatch issue? I think the RAM manufacturers and RAM sizes are not matched.

 

[koolkat77]

Please follow what's asked in this quote:

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.

How to Post a Screenshot in Seven Forums

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages (QPI/DRAM core voltage) are set at.

Before you remove any RAM:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
  
  Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)

 

[generalerror]

I ran the Driver Verifier for 24 hours or so, no BSOD. So I turned it off.
I was told by another technician that it may be related to my Samsung mobile, which was plugged in via USB at the time of the last BSOD and is mentioned in the crash report of the previous BSOD (?). I checked the device manager when the phone was plugged in, and saw exclamation marks next to the Samsung USB device and phone. Which means I need to update those drivers? or just stop plugging it into my system to avoid any future BSOD? I hope this is the cause...I would be much happier knowing it was this simple conflict, rather than some faulty internal hardware.

And just now I checked my nVidia settings randomly, and for some reason an error window appeared, saying it couldn't load them, because no nVidia card had been detected. I checked the device manager and the systeminfo.exe and only Intel HD Graphics 4000 was present, no GeForce. So I uninstalled the newest nVidia drivers (310.90, which I had installed 1 week ago), attempted to install the 306.23 (which failed, and it said there was no compatible device in this laptop), then tried to install the newest drivers again (310.90, which worked). And now the card is detected again and appears in the device manager. Can this somehow mean the card is faulty...and maybe it needs to be replaced? I'm starting to think I was sold a dud by this computer store.

And on top of all this, the laptop fan is now running noticeably louder than before. When I first got it, it was very quiet.. now it's the opposite, even when I have nothing running.

 

[Britton30]

Do you have an option in BIOS for Lucid Off/ON? Turn on if so. You should try the laptop maker's support page for the nVIDIA graphics driver package.

 

[generalerror]

I will check the BIOS.
Well...went around 5 days with no BSOD...then went into Cyberlink Powerdirector to do some HD video editing, and 30 minutes into that, BSOD occurred. I'm thinking either it's related to that program, because I believe some (if not all) of the previous crashes occurred when that program was running... or maybe the fact that this editing task is very memory/GPU intensive.. meaning hardware failure? I ran Furmark to test the video card and there appeared to be no problem. This is getting way out of hand. I've contacted the store interstate from which I bought this laptop.
The latest dump file is attached, along with all the previous crash dumps. Thanks again for helping me out, if I can solve this problem, I'll be over the moon.

 

[koolkat77]

Same error.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800e13fa10, fffff80000b9c3d8, fffffa80138e3c60}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : ACPI.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800e13fa10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80138e3c60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa800e12e940

DRIVER_OBJECT: fffffa800d31de70

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000ef2000 ACPI

IRP_ADDRESS:  fffffa80138e3c60

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c388 fffff800`02ee6992 : 00000000`0000009f 00000000`00000003 fffffa80`0e13fa10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02e8194c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02e817e6 : fffffa80`140842f8 fffffa80`140842f8 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02e816ce : 000001a0`c4ef104b fffff800`00b9cb18 00000000`00af15b0 fffff800`02ff6888 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02e814b7 : 00000061`72fb8bc4 00000061`00af15b0 00000061`72fb8b4c 00000000`000000b0 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e6e94a : fffff800`02ff2e80 fffff800`03000cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_ACPI.sys

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

Please enable driver verifier as requested on post #19

 

[generalerror]

I enabled driver verifier a few days ago and ran it for 24 hrs + , no BSOD occurred, and I turned it off. Should I turn it on again?
Was just web browsing now searching for a solution to this annoying problem, and another random BSOD occurred. The latest dump file is attached. I'm going crazy

 

[koolkat77]

I've checked this one earlier and posted the output.

Verifier is not giving BSOD-s which means hardware is your problem.
Probably time to use the warranty.

OR consider a clean install before taking the laptop back.

http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

 

[generalerror]

My mistake, I uploaded the wrong dump. Here's the latest one.
I've reactivated driver verifier now too. And yes, looks like I'll be returning this laptop. Had enough

 

[generalerror]

Sigh. New nvidia driver has been released, I'll update it now and see how it goes from there

 

[koolkat77]

Nothing new........

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800e360a10, fffff80000b9c3d8, fffffa800db5ae10}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : ACPI.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800e360a10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800db5ae10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa800e3569d0

DRIVER_OBJECT: fffffa800d31a450

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000d7c000 ACPI

IRP_ADDRESS:  fffffa800db5ae10

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c388 fffff800`02eef992 : 00000000`0000009f 00000000`00000003 fffffa80`0e360a10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02e8a94c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02e8a7e6 : fffffa80`0d9f9b08 fffffa80`0d9f9b08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02e8a6ce : 00000007`d4359757 fffff800`00b9cb18 00000000`000349f7 fffff800`03000168 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02e8a4b7 : 00000001`d53465c6 00000001`000349f7 00000001`d5346524 00000000`000000f7 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e7794a : fffff800`02ffbe80 fffff800`03009cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_ACPI.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05a92000 fffff880`06530000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 12:47:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[generalerror]

In your opinion, is this pointing to a hardware failure? I've just updated the nVidia driver to the latest version. As I did before. Not expecting this update to do anything though.
I'm hesitant to return this laptop since I'll have to ship it back interstate. I will if I have to, but still hesitant. I wish it was a simple driver problem that could be fixed easily. But I guess it's looking less and less likely, right?

 

[Arc]

The display driver is problematic here ....

Irp is active with 4 stacks 2 is current (= 0xfffffa800db5af28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800e3569d0 00000000 fffff88005bbd084-fffffa80127047c0 Success Error Cancel pending
           \Driver\ACPI    nvlddmkm
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 fffffa80113de040 00000000 00000000-00000000    pending
           \Driver\nvlddmkm
            Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa801273ab40    

            Args: 00000000 00000000 00000000 00000000
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05a92000 fffff880`06530000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 12:17:52 2012 (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Apply the latest version of nVidia display driver.
You may download it directly, from our forum link http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).

The Atheros network driver is also failing.

fffff800`00b9c508  fffff880`0695b620Unable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 athrx+0x128620
fffff880`06833000 fffff880`06bbb000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: athrx.sys
    Image name: athrx.sys
    Timestamp:        Wed Feb 15 14:46:43 2012 (4F3B77FB)
    CheckSum:         00364FC6
    ImageSize:        00388000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from ATHEROS drivers for Microsoft Windows (Atheros?????)

Update Intel(R) USB 3.0 Host Controller Switch Driver too, form Intel download Center.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

Let us know the results.

 

[generalerror]

Thank you for your help Arc. I've updated the nVidia driver today to the latest version available (314.07), obtained via the nVidia Control Panel. Last week I updated to the latest driver (at that time, 310.90) and it didn't prevent the eventual BSODs, but I'm hoping that this one will solve the problem. Also turned off the USB Selective Suspend, as you recommended.

I've downloaded the Atheros drivers from the site, and they come in a folder. There's no executable file for installation. How do I install the new drivers? Is it a matter of copying and pasting?

According to the program DriverBoost, the USB 3.0 Controller driver is up to date.

Thank you again and I'll get back to you if the Blue Screen returns. Fingers crossed

 

[Arc]

Let u hope so. If there is any further issue, let us know.

 

[generalerror]

do you know how I can install the latest Atheros drivers? I downloaded them and I got a zipped folder full of .sys, .inf. and .cat files

 

[Arc]

do you know how I can install the latest Atheros drivers? I downloaded them and I got a zipped folder full of .sys, .inf. and .cat files

Follow it: http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html

 

[generalerror]

Done, hopefully this solves the problem

 

[Arc]

Done, hopefully this solves the problem

Good. Now get it .... USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver

Date: 01/08/2013

DriverBoost may not be the right.