Bsod problem

[soerenkk]

You have one and only minidump in your folder.

Well,this minidump points to nvidia crash.

So,

[FONT=&quot]Download and install [/FONT][FONT=&quot][FONT=&quot]Driver Sweeper[/FONT][/FONT][FONT=&quot]

Download the most recent software\driver for your [/FONT][FONT=&quot][FONT=&quot]NVIDIA [/FONT][/FONT][FONT=&quot]

Uninstall nvidia software\driver,restart in safe mode,run driver sweeper,choose only NVIDIA-Display and clean,restart in normal mode.

Install the new nvidia software\driver,restart.

Update [/FONT][FONT=&quot][FONT=&quot]DirectX [/FONT][/FONT][FONT=&quot]


Run the [/FONT][FONT=&quot][FONT=&quot]nvidia-video-card-test[/FONT] [/FONT][FONT=&quot]post here the results.[/FONT][FONT=&quot]

[/FONT]Run http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Leave it to run overnight.


Finish and post back.

Done it, when I then tried to view the result, then my gfx crashed. I used most of the day yesterday to fix all my problems with my pc. The thing is that my pc have been making BSOD's so often lately, at first I suspected an error in my installation, but after viewing the logs of my BSOD's I've found out it was driver problems. Yesterday I solved one of them (with solved I mean that that error haven't occured ever since), I'm here talking about the "mv91xx.sys".

My problem now it the files mentioned by the thread starter (according to the "BlueScreenView" tool). I have tried the thing you posted (that I quoted above), I didn't help

I made a subdomain on my web site with some info that may be meaningful to you, those files can be found here -> http://sevenforums.soerenkk.dk/

I really hope you can help me out since I'm getting really pissed about my pc is crashing more than 5 times in less than 2 hours. If you need more information, feel free to ask for it, and I will do my best to give it to you.

Regards
Søren K. K.

 

[Arc]

soerenkk, it seems to be your first post, in another person's thread. As it is against the BSOD posting instructions, and Panais is not available ATM, we made your post a new thread. Continue here.

If you are having BSODs, post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[soerenkk]

Follow up

soerenkk, it seems to be your first post, in another person's thread. As it is against the BSOD posting instructions, and Panais is not available ATM, we made your post a new thread. Continue here.

If you are having BSODs, post it following the Blue Screen of Death (BSOD) Posting Instructions.

Sorry if I broke any rule(s), I'm new.

I created the think you mentioned, and uploaded it to my server, for you to review.

I posted it in there since that thread was about the same files, thought it might had a connection, but however thanks for correcting me.

And again: If any other information is needed, or I did something wrong (again), please tell me.

Thank you on beforehand.

Regards
Søren K. K.

 

[Arc]

And again: If any other information is needed, or I did something wrong (again), please tell me.

Thank you on beforehand.

Regards
Søren K. K.

The only information is needed, you execute the Blue Screen of Death (BSOD) Posting Instructions..

 

[soerenkk]

Answer

And again: If any other information is needed, or I did something wrong (again), please tell me.

Thank you on beforehand.

Regards
Søren K. K.

The only information is needed, you execute the Blue Screen of Death (BSOD) Posting Instructions..

I did, it is on the link I provided (http://sevenforums.soerenkk.dk/)

 

[Arc]

It is a stop ox116, a Display/ Graphics related BSOD.

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cb3b240, fffff88004b63198, ffffffffc00000b5, a}

Unable to load image \SystemRoot\system32\DRIVERS\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 : nvlddmkm.sys ( nvlddmkm+139198 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cb3b240, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004b63198, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+139198
fffff880`04b63198 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0424d4f8 fffff880`05531000 : 00000000`00000116 fffffa80`0cb3b240 fffff880`04b63198 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`0424d500 fffff880`05530ddb : fffff880`04b63198 fffffa80`0cb3b240 fffffa80`0f547960 fffffa80`0f867010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0424d540 fffff880`04525f07 : fffffa80`0cb3b240 00000000`c00000b5 fffffa80`0f547960 fffffa80`0f867010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`0424d570 fffff880`04553d5a : fffffa80`ffffffff 00000000`00056099 fffff880`0424d6c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0424d650 fffff880`04539bb1 : fffffa80`0fa0e000 ffffffff`feced300 00000000`00000006 fffffa80`0fa0e000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0424d690 fffff880`0453704c : 00000000`000022e6 fffff8a0`0de44690 fffffa80`0fa0e000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`0424d790 fffff880`045348af : 00000000`00000000 fffffa80`117050c0 00000000`0000001f fffffa80`11c35248 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`0424d7d0 fffff880`0454e65d : 00000000`00000000 fffff8a0`02c6bd80 fffffa80`00000001 fffffa80`1162b400 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`0424d9a0 fffff880`0454e398 : fffff800`00b96080 fffff880`0454dd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0424db90 fffff880`0454de96 : 00000000`00000000 fffffa80`12590a40 00000000`00000080 fffffa80`0f867010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0424dbc0 fffff800`0336634a : 00000000`0165557c fffffa80`0f54ab50 fffffa80`0c761040 fffffa80`0f54ab50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0424dc00 fffff800`030b6946 : fffff800`03241e80 fffffa80`0f54ab50 fffff800`0324fcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0424dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+139198
fffff880`04b63198 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+139198

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04a2a000 fffff880`054d2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Feb 10 04:43:08 2013 (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try to roll the driver back to an earlier version that worked smooth to you.
Device Manager - Roll Back Driver

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Stop overclocking your CPU and GPU.

Dismantle the computer, clean the inside carefully. Specially clean the fan grills and air vents.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Also, follow the guide http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

A question ... exactly when you have installed the Service pack 1?

Marvell MV91xx AHCI/RAID driver is also causing BSODs there.

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

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff88002a33080, 0, 0, fffff88001164ee1}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=mv91xx.sys"]mv91xx.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=mv91xx.sys"]mv91xx.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=mv91xx.sys"]mv91xx.sys[/URL] ( mv91xx+2fee1 )

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

And the driver is very old.

fffff880`01135000 fffff880`011c1000   mv91xx   T (no symbols)           
    Loaded symbol image file: mv91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mv91xx.sys
[COLOR=Red]    Image name: mv91xx.sys
    Timestamp:        Fri Aug 27 15:19:22 2010[/COLOR] (4C778A22)
    CheckSum:         00050BB0
    ImageSize:        0008C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Better you stop using RAID And uninstall this one:

Start Menu\Programs\Marvell Storage Utility

Marvell's drivers are poorly coded, and often causes problems, whereas windows inbuilt storage controller drivers never fail.

Update the firmware of your Samsung 840 PRO Series SSD.

Update the BIOS, too.

BIOS-version/dato    American Megatrends Inc. 1305, [COLOR=Red]11-02-2011[/COLOR]

Get the BIOS update from the hardware manufacturer's website only.

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[soerenkk]

Thank you, I will try doing it when I get home.

The "Marvell MV91xx" thing I am aware of, think I fixed it Tuesday, and since then I have monitered the outcome of that.

The thing is that my pc have been making BSOD's ever since I got my SSD in it. I will try make a roll back on the gfx driver, but the "Marvell MV91xx" thing I have no clue to do with, the driver it have installed was the newest I could find.

Better you stop using RAID And uninstall this one:
Code:
Start Menu\Programs\Marvell Storage Utility

I will, I don't use the RAID anyways.

Update the firmware of your Samsung 840 PRO Series SSD.

Update the BIOS, too.

As far as I know it is the newest firmware and drivers for my SSD, but I'll look it up when I get home.

I am a bit nervous to update my BIOS since I don't know exactly how I do it, and because I know what the result will be if anything goes wrong.

I'll try do all the things you suggested when I get home.

For now: Thank you very much, for your help and time.

Regards
Søren K. K.

 

[Arc]

You are welcome. Let us know the results

 

[soerenkk]

Update

Well now I have done the things you told me to do.

First I removed the "Marvell Storage Utility" thing.

Then I fixed MSCONFIG.

Then I downgraded my GFX driver by 1 version.

Then I just upgraded my SSD's firmware.


Windows 7 SP 1 was installed: 19-02-2013 (d-m-Y).


So far I haven't had any BSOD, but I haven't had that much time to test it out and stress my system. Over the weekend I will look out for BSOD's and if no one occurs (I really hope so) then I go back in and mark this thread as [SOLVED].

So far: Thank you very much Arc for you time and guidance.

Regards
Søren K. K.

 

[Arc]

Now follow Drivers - Clean Left over Files after Uninstalling
If any leftover of Marvell is there, clean those. Report us the situation when you think, or if there is any further issue.

 

[soerenkk]

^^ Done

 

[Arc]

Now observe the situation ... put stress on the computer (but dont overstress) and see how it reacts. Let us know the situation.

 

[soerenkk]

Well I got at BSOD again (I guess it was the GFX card since my screen went black, and my GFX driver fan started to spin at max). I was browsing on youtube.

I uploaded an updated SF dump to the website.

 

[Arc]

Yes it is a graphics related crash.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 116[/COLOR], {fffffa80118294e0, fffff88005366adc, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\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 : nvlddmkm.sys ( nvlddmkm+929adc )

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

And you haven't updated the display driver.

fffff880`04a3d000 fffff880`054db000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]    Image name: nvlddmkm.sys
    Timestamp:        Sat Dec 29 12:17:52 2012[/COLOR] (50DE9218)
    CheckSum:         00A7F96C
    ImageSize:        00A9E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It is a must to update the display driver when you get a graphics related bsod. 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).

During install, go for advanced installation mode, check the "perform a clean install" button, and install the display driver and the PhysX only.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Try to run a Youtube video, when the progress bar started proceeding, right click on it.... select settings in the context menu. then uncheck it.
View attachment 259577

Can you play YouTube Videos freely now?

 

[soerenkk]

You told me to roll back my gfx driver, I did, but no versions were available so I installed the 2. newest.

Was that wrong?

 

[Arc]

Ah! I see. Try this version in this case.

• Download and install Driver Fusion.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• If it says the the free version of Driver Fusion cannot remove all the elements, stop there and follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Drivers > Beta and Legacy; search there with your cards particulars for GeForce 306.23 Driver, dated 13.9.2012 and install it.

Actually due to rollback the display driver version appeared that is not very stable, whereas 306.23 is the most stable one in the recent time.


Dont forget the GPU acceleration to stop.



Let us know the situation.

 

[soerenkk]

^^ Done, now I will give it a few days to see if it have fixed my problem. If it have I'll mark this thread as [SOLVED].

Thank you once again.

 

[Arc]

Best of luck mate

 

[soerenkk]

AND I crashed again, website have been updated with a new updated crash SF file.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80133ab010, fffff8800fdcc004, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\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 : nvlddmkm.sys ( nvlddmkm+ad6004 )

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

So it is the same crash again.
Now I will suggest you to use the onboard graphics and see what happens there with it. Does it still crash or not?