BSOD when booting windows,almost every cold boot.

ok the verifier is running and i have check all the non microsoft drivers and i t has not crash yet so what i need to do now ?
PS : for the driver list ,where is the dump file of the verifier ?

deathwing911 said:

ok the verifier is running and i have check all the non microsoft drivers and i t has not crash yet so what i need to do now ?

Wait.!! I have seen it take 36 hours or more. When it finds the driver it is supposed to, and will, crash. Upload that DMP file.

sorry for noob question but where will the dump file be when it crash ?
or it is just the same diump as the sf .

deathwing911 said:

sorry for noob question but where will the dump file be when it crash ?
or it is just the same diump as the sf .

If configured as below it should be in c:\windows\minidump


We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

here you go ken :

deathwing911 said:

here you go ken :

Driver verifier does not seem to be enabled when these crashes occurred. Are you sure you are following the instructions carefully?


It is also possible verifier did not catch the bad driver, which sometimes happens. Keep verifier running.

ok , it has not crash yet this is a dump of a previous crash . But the verifier is up and still running ill try to make it crash today when im gonna cold boot it ( because its the only time it crash).

deathwing911 said:

ok , it has not crash yet this is a dump of a previous crash . But the verifier is up and still running ill try to make it crash today when im gonna cold boot it ( because its the only time it crash).

No new dmp. Where did you put it?

theres no new dumps , because this morning when i cold boot it , strangely it dint crash at all :O. So i cant provide ya the crash info "yet".(its like uncheck microsoft driver verifier did something dunno).But it will surly crash sometimes soon, it will be too good to be true lol .Ill keep ya inform for further dumps files when it crash.

deathwing911 said:

theres no new dumps , because this morning when i cold boot it , strangely it dint crash at all :O. So i cant provide ya the crash info "yet".(its like uncheck microsoft driver verifier did something dunno).But it will surly crash sometimes soon, it will be too good to be true lol .Ill keep ya inform for further dumps files when it crash.

We are both here if it does crash