[Rajiv Soler]

Have you solved your problem?   An update would be appreciated.

 

Thanks.

Actually I was away for the last 10-12 days regarding work . So i could not update on the issue !!  I did a complete re installation of MY os and all drivers and all games , Everything and it still persists !! But on the day of re installation I had zero issues but after a day it came back !! I re installed mY display driver once more it didnt give me issues for 1 day and started again !!

[Advertisements]

Thanks for the update.

Please upload the latest dmp files.

 

Did you clear the CMOS before the reinstall?

Have you made any alterations to windows default setting, like altering the Page File settings?

Is there a specific time or action when the crashes occur?

Download the manufacturers disc tool for your brand HDD, > http://www.tacktech....ay.cfm?ttid=287

[iammykyl]

Thanks for the update.

Please upload the latest dmp files.

 

Did you clear the CMOS before the reinstall?

Have you made any alterations to windows default setting, like altering the Page File settings?

Is there a specific time or action when the crashes occur?

Download the manufacturers disc tool for your brand HDD, > http://www.tacktech....ay.cfm?ttid=287

[Rajiv Soler]

Thanks for the update.

Please upload the latest dmp files.

 

Did you clear the CMOS before the reinstall?

Have you made any alterations to windows default setting, like altering the Page File settings?

Is there a specific time or action when the crashes occur?

Download the manufacturers disc tool for your brand HDD, > http://www.tacktech....ay.cfm?ttid=287

Is this the dump file you are looking for ?!

Attached Files

•  051315-18392-01.rar   31.92KB   241 downloads

[phillpower2]

Nvidia drivers and DirectX both get a mention, from your crash dump;

 

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+144bc8

 

fffff880`02d1a448  fffff880`052f5280 nvlddmkm+0xe3280

fffff880`02d1a450  fffff880`05d77027 dxgmms1!VidSchiSubmitRenderCommand+0xc0b

 

Suggested fixes from an old thread that I found;

 

There have been a number of issues reported experiencing Blue Screen Of Death (BSOD) crash on Vista and Windows 7 related to dxgmms1.sys and nvlddmkm.sys files. There are few solutions available and all of them are not 100% guarantee to fix your problem :-\

Solution 1

Try installing Windows hot-fix http://support.microsoft.com/kb/974431

Solution 2

nvidia drivers may cause BSOD, try running the straight up vista/windows 7 drivers

Solution 3

There might be a bad memory or other piece of hardware. Run the built-in Memory Diagnostic or other diagnostic tools to find any potential problems.

Solution 4

1. Disable C1E in BIOS
2. Disable any boost in BIOS (standard only)
3. Run driver sweeper in safe mode to uninstall display drivers
4. Reboot
5. Install newest video drivers and update directx

[Rajiv Soler]

 

Nvidia drivers and DirectX both get a mention, from your crash dump;

 

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+144bc8

 

fffff880`02d1a448  fffff880`052f5280 nvlddmkm+0xe3280

fffff880`02d1a450  fffff880`05d77027 dxgmms1!VidSchiSubmitRenderCommand+0xc0b

 

Suggested fixes from an old thread that I found;

 

There have been a number of issues reported experiencing Blue Screen Of Death (BSOD) crash on Vista and Windows 7 related to dxgmms1.sys and nvlddmkm.sys files. There are few solutions available and all of them are not 100% guarantee to fix your problem :-\

Solution 1

Try installing Windows hot-fix http://support.microsoft.com/kb/974431

Solution 2

nvidia drivers may cause BSOD, try running the straight up vista/windows 7 drivers

Solution 3

There might be a bad memory or other piece of hardware. Run the built-in Memory Diagnostic or other diagnostic tools to find any potential problems.

Solution 4

1. Disable C1E in BIOS
2. Disable any boost in BIOS (standard only)
3. Run driver sweeper in safe mode to uninstall display drivers
4. Reboot
5. Install newest video drivers and update directx

 

So its driver issue ?! 
When you mean bad memory or other piece of hardware could it be My PSU or GPU or Ram or HDD or all of these ?!

[Rajiv Soler]

I could not find the c1E option in my bios set up !!

[phillpower2]

So its driver issue 

 

 

Not necessarily, as said it could be hardware or a combination of both.

 

When you mean bad memory or other piece of hardware could it be My PSU or GPU or Ram or HDD or all of these ?!

 

 

Answer as above.

 

I could not find the c1E option in my bios set up !!

 

 

No worries as it is not always an option.

 

Have you done all of the other suggestions, I ask as you should only do one at a time and then test the computer to see how it behaves.

 

 

Tip

If you have something to add while waiting for a reply use the edit tab – bottom right of the dialogue input box and this will ensure that no information that you provide is overlooked (this can happen if your topic has more than one page)  

[Rajiv Soler]

Solution 1:
This update is not applicable to your computer 
Solution 2:
Did a complete re install after using drive sweeper in safe mode to remove all video drivers 
Solution 3:
No issues found on several diagnostic softwares 
Solution 4: 
Didnt find the option 

And today it crashed when I was using Facebook(google chrome) and no other application !! 
Yesterday night it wasnt starting fr a pretty long time !! All the fans were running and all the lights were on but no display !! after few hours it worked on its own !! What can you make of that ?! And if i Did get a bsod it says some locale id 1033 and BSS Code 1000007e (not sure of the number of zeroes)

[iammykyl]

No issues found on several diagnostic softwares 

 

Did you run an extended HDD test using the manufacturers software?

Use another tool to see what is causing the freeze.

Run the Reliability Monitor, How to use, > http://www.makeuseof...bility-monitor

 

Re. PSU, could still be the problem, low 12v rail reading, see reply #7.

[Rajiv Soler]

I could not find the software i mean it wasnt there !! And i tried that paperclip method and my psu worked !!

[iammykyl]

The PSU paperclip test only shows that it is working but is under no load.   A proper test while the PSU is under load can only be done with a PSU load test.   A local PC repair shop may be able to do this for you, sometimes for free or a small fee, best bet is to ring around and enquire.

 

The Reliability Monitor may not be enable on you system, it is quite hard to find, instructions, > http://social.techne...collection.aspx

[Rajiv Soler]

The PSU paperclip test only shows that it is working but is under no loaf.   A proper test while the PSUY is unser load can only be done with a PSU load test.   A local PC repair shop may be able to do this for you, sometimes for free or a small fee, best bet is to ring around and enquire.

 

The Reliability Monitor may not be enable on you system, it is quite hard to find, instructions, > http://social.techne...collection.aspx

When i try to troubleshoot hardware !! it says change in hardware not detected !! 
And i get this in reliability monitor

Attached Thumbnails

• 

[iammykyl]

 

 

When i try to troubleshoot hardware !! it says change in hardware not detected !!

What program gives you that message.

 

many people get the "network streaming service stopped"   Thought to be a bug in Geforce experience. > http://www.geforce.c...orce-experience

Let's see if uninstalling will help.   Go to add/remove programs and uninstall Geforce  Experience.

 

Copy any dmp files from C:\Windows\Minidump onto the desktop.

Select the last dated one , right-click on it, and click on Send To> New Compressed (zipped) Folder. Please include in your next reply. 

[Rajiv Soler]

 

 

 

When i try to troubleshoot hardware !! it says change in hardware not detected !!

What program gives you that message.

 

many people get the "network streaming service stopped"   Thought to be a bug in Geforce experience. > http://www.geforce.c...orce-experience

Let's see if uninstalling will help.   Go to add/remove programs and uninstall Geforce  Experience.

 

Copy any dmp files from C:\Windows\Minidump onto the desktop.

Select the last dated one , right-click on it, and click on Send To> New Compressed (zipped) Folder. Please include in your next reply. 

 

I have a bluescreen viewer !! The crash is caused by NTFS.sys and ntoskrnl.exe !! those are the latest dump files !! And ve actually uploaded it in reply #18 !! I ve been getting bsod but suddenly it froze with a buzzing noise at literally 0 load today and no dump files were created !!

[phillpower2]

I have a bluescreen viewer !! The crash is caused by NTFS.sys and ntoskrnl.exe !! those are the latest dump files !! And ve actually uploaded it in reply #18 !! 

 

 

Not according to the crash dump that you uploaded in reply #18

 

Debug session time: Wed May 13 01:38:36.573 2015 (UTC - 4:00)

System Uptime: 0 days 0:51:01.900

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

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.

Some common problems are exception code 0x80000003.  This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG.  This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG.  This will let us see why this breakpoint is

happening.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff88005356bc8, The address that the exception occurred at

Arg3: fffff88002d1ad48, Exception Record Address

Arg4: fffff88002d1a5a0, Context Record Address

 

Debugging Details:

------------------

 

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

 

FAULTING_IP: 

nvlddmkm+144bc8

fffff880`05356bc8 ff9008010000    call    qword ptr [rax+108h]

 

EXCEPTION_RECORD:  fffff88002d1ad48 -- (.exr 0xfffff88002d1ad48)

ExceptionAddress: fffff88005356bc8 (nvlddmkm+0x0000000000144bc8)

   ExceptionCode: c0000005 (Access violation)

  ExceptionFlags: 00000000

NumberParameters: 2

   Parameter[0]: 0000000000000000

   Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

 

CONTEXT:  fffff88002d1a5a0 -- (.cxr 0xfffff88002d1a5a0)

rax=fffff88005733b18 rbx=fffffa8005d61000 rcx=fffffa8005c49000

rdx=0000000073420000 rsi=fffffa8005152000 rdi=0000000000000000

rip=fffff88005356bc8 rsp=fffff88002d1af80 rbp=fffff88002d1b0a0

 r8=0000000000420000  r9=0000000000000004 r10=0000000000000000

r11=fffff880056fe18f r12=fffffa8005c49000 r13=0000000000000000

r14=fffffa8005d1f010 r15=fffff88002d1b4c0

iopl=0         nv up ei ng nz na pe nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282

nvlddmkm+0x144bc8:

fffff880`05356bc8 ff9008010000    call    qword ptr [rax+108h] ds:002b:fffff880`05733c20=fffff88005362708

Resetting default scope

 

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

 

PROCESS_NAME:  System

 

CURRENT_IRQL:  0

 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

 

EXCEPTION_PARAMETER1:  0000000000000000

 

EXCEPTION_PARAMETER2:  ffffffffffffffff

 

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001eb0100

GetUlongFromAddress: unable to read from fffff80001eb01c0

 ffffffffffffffff 

 

FOLLOWUP_IP: 

nvlddmkm+144bc8

fffff880`05356bc8 ff9008010000    call    qword ptr [rax+108h]

 

BUGCHECK_STR:  0x7E

 

LAST_CONTROL_TRANSFER:  from fffffa8005c49000 to fffff88005356bc8

 

STACK_TEXT:  

fffff880`02d1af80 fffffa80`05c49000 : fffff880`02d1b0a0 fffffa80`05152000 fffff880`052fcd86 0000000f`ffffc938 : nvlddmkm+0x144bc8

fffff880`02d1af88 fffff880`02d1b0a0 : fffffa80`05152000 fffff880`052fcd86 0000000f`ffffc938 fffffa80`03f83ae8 : 0xfffffa80`05c49000

fffff880`02d1af90 fffffa80`05152000 : fffff880`052fcd86 0000000f`ffffc938 fffffa80`03f83ae8 000000ff`fffff56c : 0xfffff880`02d1b0a0

fffff880`02d1af98 fffff880`052fcd86 : 0000000f`ffffc938 fffffa80`03f83ae8 000000ff`fffff56c fffff880`052fcd86 : 0xfffffa80`05152000

fffff880`02d1afa0 0000000f`ffffc938 : fffffa80`03f83ae8 000000ff`fffff56c fffff880`052fcd86 000000ff`fffff56c : nvlddmkm+0xead86

fffff880`02d1afa8 fffffa80`03f83ae8 : 000000ff`fffff56c fffff880`052fcd86 000000ff`fffff56c fffff880`052fcca6 : 0xf`ffffc938

fffff880`02d1afb0 000000ff`fffff56c : fffff880`052fcd86 000000ff`fffff56c fffff880`052fcca6 0000000f`ffffc938 : 0xfffffa80`03f83ae8

fffff880`02d1afb8 fffff880`052fcd86 : 000000ff`fffff56c fffff880`052fcca6 0000000f`ffffc938 fffff880`052fdb27 : 0xff`fffff56c

fffff880`02d1afc0 000000ff`fffff56c : fffff880`052fcca6 0000000f`ffffc938 fffff880`052fdb27 00000000`00000000 : nvlddmkm+0xead86

fffff880`02d1afc8 fffff880`052fcca6 : 0000000f`ffffc938 fffff880`052fdb27 00000000`00000000 00000000`00000001 : 0xff`fffff56c

fffff880`02d1afd0 0000000f`ffffc938 : fffff880`052fdb27 00000000`00000000 00000000`00000001 fffffa80`03f83ae8 : nvlddmkm+0xeaca6

fffff880`02d1afd8 fffff880`052fdb27 : 00000000`00000000 00000000`00000001 fffffa80`03f83ae8 00000000`00000001 : 0xf`ffffc938

fffff880`02d1afe0 00000000`00000000 : 00000000`00000001 fffffa80`03f83ae8 00000000`00000001 0000000f`fffd4004 : nvlddmkm+0xebb27

 

 

SYMBOL_STACK_INDEX:  0

 

SYMBOL_NAME:  nvlddmkm+144bc8

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: nvlddmkm

 

IMAGE_NAME:  nvlddmkm.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  55259065

 

STACK_COMMAND:  .cxr 0xfffff88002d1a5a0 ; kb

 

FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+144bc8

 

BUCKET_ID:  X64_0x7E_nvlddmkm+144bc8

 

Followup: MachineOwner

---------

 

Also of note from your crash dump was that the driver kbdhid.sys was failing to load, this may or may not be related but regardless either way it needs to be addressed, we need some further hardware and software information so please see below;

 

Download then run Speccy (free) and post the resultant url for us, details here,  this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s. 

 

JFYI: Reliability monitor is showing that something else is shutting down Windows prematurely rather than Windows itself crashing, that would explain the absence of any further crash dumps.