Some random BSOD...

[Lebon14]

Hi guys.

I just got a VERY random BSOD. The other ones I got before were initialised by myself, so no blame here. But this one... it couldn't get the drive initiated to dump the minidump...

So here's what happened. I was playing some music with foobar2000 and the PC was sitting idle. I was playing my Nintendo DS at my PC desk while listening to music. Quite boring, eh. Then, I decided to check the net for something. I pop Firefox out and switch tab and the sytem hanged and BSODed after a moment.

Since, it wasn't dumping, I resetted. Upon rebooting, I got an error saying that an important part of booting was absent. Pressed Esc and checked the BIOS. My SSD was gone! I pressed the power button and became quite nervous. I grabbed my Win7 DVD then re-power on my PC. Checked the BIOS and the SSD came back. So, I quitted and booted normally. I ran the OCZ toolbox that I kept in case. Everything seemed normal from the SMART.

The error code was like 0x6...something forgot to write it down.

Do you guys have an idea what happened?

Thanks in advance

 

[wish]

Make sure your system is configured to generate minidump files.
Set MiniDump

 

[Lebon14]

Make sure your system is configured to generate minidump files.
Set MiniDump

You know what? The two BSOD I experienced from my mistake, they did generated minidumps but not the one I had today...

 

[reventon]

Hi,

Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Hopefully they can still tell us something.

Attach the .zip file to your next post in this thread.

 

[Lebon14]

Hmm... OK, sure... the file is attached.

- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes... first Windows that my SSD sees.
- an OEM or full retail version? Full retail.
- What is the age of system (hardware)? End of October 2010.
- What is the age of OS installation (have you re-installed the OS?) See age of hardware.

P.S If there's a mnidump, it's not the BSOD that happened last night... that's something else.

 

[JMH]

Hmm... OK, sure... the file is attached.

- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes... first Windows that my SSD sees.
- an OEM or full retail version? Full retail.
- What is the age of system (hardware)? End of October 2010.
- What is the age of OS installation (have you re-installed the OS?) See age of hardware.

P.S If there's a mnidump, it's not the BSOD that happened last night... that's something else.

HI Lebon14

This Crash was caused by your "ntune" nvidia (nvoclk64.sys) driver.

You should remove all the traces of this driver and re-install the newest version from their site.

Your current driver is dated
9/5/2007 1:26:33 PM and is in need of updating.


While you are updating you might as well do these as well

SSPORT.sys    8/12/2005 10:07:32 AM        fffff880`07d9a000    fffff880`07da2000    0x00008000    0x42fbda34                        
regi.sys    4/17/2007 2:19:10 AM        fffff880`07d5a000    fffff880`07d62000    0x00008000    0x462393ee                        
nvoclk64.sys    9/5/2007 1:26:33 PM    nvoclk64.sys+1ab7    fffff880`09383000    fffff880`09391000    0x0000e000    0x46de13d9                        
WinRing0x64.sys    7/27/2008 12:29:37 AM        fffff880`0937c000    fffff880`09383000    0x00007000    0x488b26c1

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


Let us know if you need assistance with this

JMH

 

[Lebon14]

nTune heh? I thought I removed everything from that thing!

SSPORT.sys : My printer, heh. Well, I DID download the latest one from the website last time...
regi.sys : InterVideo?!? WTH. I removed that!
Nvoclk64.sys : that thing might go along with nTune... so it's supposed to be removed... but oh wait! nTune is crap and didn't come with an uninstaller!
WinRing0x64.sys : Don't know what's supposed to be...

EDIT

Wait, you got the wrong BSOD. I said that the BSOD related to the minidump in there was another BSOD I got earlier this week while trying to see my GPU Usage. I installed nTune and upon starting, it gave me a BSOD. The BSOD I got last night... there's no record of it BECAUSE it couldn't access the SSD, since it SOMEHOW disappeared while the OS was running. Since the BSOD couldn't find the SSD to write the dump to... nothing was saved. that's why simple BSOD instruction won't work for that.

 

[zigzag3143]

Just a drive by, but when I was checking this out I was confused as well.

As far as I can see thats the only DMP you uploaded. I too thought you were referring to the one uploaded not the one not uploaded which you wanted a cause for.

Guess we will just have to wait for the next one.

 

[JMH]

nTune heh? I thought I removed everything from that thing!

SSPORT.sys : My printer, heh. Well, I DID download the latest one from the website last time...
regi.sys : InterVideo?!? WTH. I removed that!
Nvoclk64.sys : that thing might go along with nTune... so it's supposed to be removed... but oh wait! nTune is crap and didn't come with an uninstaller!
WinRing0x64.sys : Don't know what's supposed to be...

EDIT

Wait, you got the wrong BSOD. I said that the BSOD related to the minidump in there was another BSOD I got earlier this week while trying to see my GPU Usage. I installed nTune and upon starting, it gave me a BSOD. The BSOD I got last night... there's no record of it BECAUSE it couldn't access the SSD, since it SOMEHOW disappeared while the OS was running. Since the BSOD couldn't find the SSD to write the dump to... nothing was saved. that's why simple BSOD instruction won't work for that.

You post a DMP - we do the analysis!

JMH

 

[Lebon14]

^ But you asked me to do that, so I did it. But I did already say that during the BSOD, it was stuck at "Initiating drive..." If he couldn't initiate the SSD to write on the minidump and the error reports, did you think i had an exact minidump for that?

 

[Jonathan_King]

Hello Lebon!

I see this event log:

Event[623]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2010-12-06T03:35:53.000
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classique
  User: N/A
  User Name: N/A
  Computer: Lebon14-PC
  Description: 
Le fichier de vidage mémoire à l’emplacement C:\Windows\MEMORY.DMP a été supprimé car le volume du disque contient moins de 25 Go d’espace libre.

Translated into English (for me and others):

The memory dump file at C: \ Windows \ MEMORY.DMP was deleted because the volume of the disc contains less than 25 GB of free space.

It appears you only have 12.48 GB free space on your C drive.

Make sure that Windows is set to create a minidump, not a Full Kernel dump:

View attachment 122606

I also suggest you use this brand-new tutorial to clear up some disk space, if possible:

http://www.sevenforums.com/tutorials/129976-hard-disk-space-free-up-recover.html

 

[CarlTR6]

Lebon, there is no update for SSPORT.sys. It is some sort of a utility driver. Rename it to from .sys to .old, reboot and it will not load. Your printer will function fine without that driver.