System BSOD - Clock

[Arc]

There is no crash dumps.

View attachment 274930

I kinda expected the situation. You are doing something wrong there IMHO.

 

[x BlueRobot]

Ensure you have configured a Kernel Memory dump instead, if a Stop 0x101 is still occurring, a Minidump will not contain enough information - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

You will need to place the file into a zipped folder, and then upload to a file sharing site such as Dropbox or Skydrive. Make sure the folder is placed in the Public folder if using Skydrive. Post the link to the file afterwards.

Is Driver Verifier still running? Stop 0x101's with Driver Verifier running, indicate more of a hardware related issue.

Driver Verfier is still running and Kernal Memory dump has been setup up for months before this even started to happen. There is not file tho in the location on the C Root.

A Kernel Memory dump will only appear if the system had a BSOD, did you change to a Minidump configuration when the system started to first cause BSODs?

 

[ZMan]

Ensure you have configured a Kernel Memory dump instead, if a Stop 0x101 is still occurring, a Minidump will not contain enough information - http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

You will need to place the file into a zipped folder, and then upload to a file sharing site such as Dropbox or Skydrive. Make sure the folder is placed in the Public folder if using Skydrive. Post the link to the file afterwards.

Is Driver Verifier still running? Stop 0x101's with Driver Verifier running, indicate more of a hardware related issue.

Driver Verfier is still running and Kernal Memory dump has been setup up for months before this even started to happen. There is not file tho in the location on the C Root.

A Kernel Memory dump will only appear if the system had a BSOD, did you change to a Minidump configuration when the system started to first cause BSODs?

At first just the memory bump still waiting for it to crash again.

There is no crash dumps.

View attachment 274930

I kinda expected the situation. You are doing something wrong there IMHO.

It crash and what your seeing is what happen. I didn't see any files from the BSOD in the mini-dump I don't see any issues that is causing the problem. I show you the BSOD software I'm looking at in a screencap when I get home. But I'm fully aware on how to do it and I can read. I describe what it be doing above in my other post of what going on but has yet to get rid of the BSOD issues. Still waiting for a fail to happen.

 

[x BlueRobot]

If no dump files are still produced, then this may help - BSODs but no Dump Files? - Sysnative Forums

 

[ZMan]

As promise here is a screenshot. I will post next time the BSOD happens. Everything is still to record the fault when it does happen.

 

[x BlueRobot]

Thanks, and your settings look fine

 

[ZMan]

Okay it finally happen, I have the stats from BSOD and memory dump. Hopefully we finally figure out what is the real cause of my crashes. I attach the BSOD file and link to the dump as the upload was to big for allow limits of the board.

My Memory file --> https://dl.dropboxusercontent.com/u/1132201/Win7Memory.DMP

 

[x BlueRobot]

I'm downloading the file now

 

[x BlueRobot]

[COLOR="Red"]BugCheck 101[/COLOR], {19, 0, fffff8800336a180, 7}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

0: kd> [COLOR="SeaGreen"]lmvm intelppm[/COLOR]
start             end                 module name
fffff880`013e9000 fffff880`013ff000   intelppm   (no symbols)           
    Loaded symbol image file: intelppm.sys
    Image path: \SystemRoot\system32\DRIVERS\intelppm.sys
    Image name: intelppm.sys
    Timestamp:        [COLOR="Red"]Tue Jul 14 00:19:25 2009[/COLOR] (4A5BC0FD)
    CheckSum:         0000F4EC
    ImageSize:        00016000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel chipset driver seems to be very outdated and a potential cause, please update the driver from here -

• Intel® Driver Update Utility

0: kd> [COLOR="SeaGreen"]lmvm nvlddmkm[/COLOR]
start             end                 module name
fffff880`0586a000 fffff880`0634f000   nvlddmkm   (export symbols)       nvlddmkm.sys
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Fri Jun 21 10:06:16 2013[/COLOR] (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update to the latest WHQL version of your nVidia graphics card driver, updates are available from here -

• NVIDIA Driver Downloads - Advanced Search

Version: 320.49
Release Date for Desktops and Notebooks : July 1st 2013
In Device Manager: 9.18.13.2049

 

[ZMan]

I have to update them both when I get home today. What happens before the crash is if I'm listening to music it repeats a small part of the music for one second and then lock up, knowing it going to crash. So does this answer why is crashing? It's still the same problem as before in the BSOD error.

 

[x BlueRobot]

The locking up is caused by one of threads being processed becoming hung, which would explain why it may repeat itself and then crash.

 

[ZMan]

The locking up is caused by one of threads being processed becoming hung, which would explain why it may repeat itself and then crash.

Ahh I see, I update this evening when I get home.

 

[x BlueRobot]

Thanks

 

[ZMan]

Hey Arc any word on the BSOD problem?
Blue all of my stuff is up to date with what I have installed on my system.

So I guess what next? :S

 

[x BlueRobot]

Okay good, I'll wait until another BSOD occurs, hopefully it won't.

 

[ZMan]

Okay good, I'll wait until another BSOD occurs, hopefully it won't.

It should there was nothing to update. It was already updated to the latest release. Just because it's old. XD

 

[x BlueRobot]

Okay, we begin testing the hardware then:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Run the Small FFT's, Large FFT's and Blend test for 2-3 hours each, remember to check the temperature and do not let it exceed 80*C.

 

[ZMan]

Just had time to do it now. Everything passes.

 

[x BlueRobot]

Have you had any more BSODs?

 

[ZMan]

Sorry for being a while real life and all, my system did it again I rewrote the hard drive to see if anything was the issue there.