Thread: BSOD on Windows Developer

Really is about time that driver got updated.

If it aint broke dont fix it!!!!!

Originally Posted by zigzag3143

If it aint broke dont fix it!!!!!

We seem to have a different philosophy 'If it aint broken try and try again to break it'

Originally Posted by nmsuk

We seem to have a different philosophy 'If it aint broken try and try again to break it'

I will second that. If it isnt broken you arent trying hard enough {grin}

You folks want a real dump file for the Consumer Preview to play with..

Since I know what is causing it, I thought it might be fun to test your Debugger.

Anyway, here it is.. I don't want to give away too much info, but the other data sources are not needed.

OK Saltgrass.

The jraid driver isn't the latest (or best) released. There was one mid '10 that caused a few problems. Which one I cannot say for certain.

And the Marvell stuff needs updating.

Now spill the beans and divulge what really happened

Yes Clark, clue us in.
Your dump file drove my debugger nuts, complaining about the symbols being incorrect. But Kev and I compared notes and noted a couple old driver AHCI /Raid Marvell drivers and the JMicron jraid.sys.

The cause is the basic Network adapter I have been having problems with (e1i63x64.sys).

I am still messing with it, because it seems the situation changes daily as to whether it will blue screen or not. My WinDbg listed it as the problem file, didn't even have to guess. Currently I am in a new install of the OS, but will get you a readout you can compare to what you are getting, after I reimage back to the prior install.

Of course, it might look different on this machine since it was created here....