BSOD when booting windows,almost every cold boot.

[deathwing911]

alright thanks , will keep ya in-touch.

 

[deathwing911]

alright it just crash , its a BSOD with 0000003b or (0x00000003) error in it , theres a dump (hope you will find the problem).Thanks

 

[zigzag3143]

alright it just crash , its a BSOD with 0000003b or (0x00000003) error in it , theres a dump (hope you will find the problem).Thanks

The most recent is inconclusive because verifier was not enabled. The generic answer for that code is this:

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.


Other than this We cant be more specific until we get a verified DMP.

 

[deathwing911]

the thing is had verifier on and running while the crash occurred. sorry i dont quite understand what iv done wrong :S.(you said have verifier on while the crash occured so that it can been dump in the minidumnp and deactivate it so i can relog and give ya the mimidump after) and i did .You sure its the very only way to verify the drivers problem ? sorry im a bit confused:S.

 

[deathwing911]

do you have an alternative software or utility i can use instead so we can check the drivers , because it seems that the verifier dont get the bad driver (or even report it in the dumps) so maybe an alternative can be made like i said software or something, thanks .

 

[zigzag3143]

do you have an alternative software or utility i can use instead so we can check the drivers , because it seems that the verifier dont get the bad driver (or even report it in the dumps) so maybe an alternative can be made like i said software or something, thanks .

There really isnt an alternative. These snips show how it should look

cmd
View attachment 195791


Verifier
View attachment 195792



All
View attachment 195793


Then finish.


Since this is every driver on the system it may take a while and it may crash.

 

[deathwing911]

yes it was exactly how to describe it , and at the exact order. its very strange .

 

[zigzag3143]

yes it was exactly how to describe it , and at the exact order. its very strange .

So you ran "all" drivers checked in verifier for 36 hours and it found nothing? What do you get when you type verifier /query in a cmd prompt?

 

[deathwing911]

all bunch of drivers names and descriptions is that good ?

EDIT: i have replace RAM and motherboard And i see no more issue.was better that way , thanks anyway for the help guys i very appreciate it !