I have uninstalled a faulty driver which leads to bugchecks with a new driver, though when I install the new driver it still bugchecks showing the old source code in !analyse -v in windbg. The new driver is definitely being installed though windbg is not recognising it, I have built it many times and checked time/date stamps to verify I am installing the new driver.
What is the reason for this?
Could it be due to symbols/pdb files?
The only time I get this behavior is when I have the wrong version of the
driver loaded…
Did you check the timestamp of the running driver with lmv?
-scott
OSR
@OSRDrivers
wrote in message news:xxxxx@windbg…
I have uninstalled a faulty driver which leads to bugchecks with a new
driver, though when I install the new driver it still bugchecks showing the
old source code in !analyse -v in windbg. The new driver is definitely being
installed though windbg is not recognising it, I have built it many times
and checked time/date stamps to verify I am installing the new driver.
What is the reason for this?
Could it be due to symbols/pdb files?
Each time I load the driver, I unregister and delete the driver on the virtual machine then copy the newly built driver onto the virtual machine verifying the time and date then I register and start the new driver. I have tried this around 10 times each time the same errors.
I cannot use lmv since as I get a bugcheck as soon as I start the service within osrloader.
There’s no real magic here. WinDbg locates your source code using path
information stored in the PDB. It locates your PDB via a path and GUID
stamped into the executable’s header (see !dh drivername). If you get a
crash and the source code pops up at the wrong line, the code has changed
since the binary loaded on the target was compiled.
lmv is a WinDbg command, you can run it even if the target machine crashes.
-scott
OSR
@OSRDrivers
wrote in message news:xxxxx@windbg…
Each time I load the driver, I unregister and delete the driver on the
virtual machine then copy the newly built driver onto the virtual machine
verifying the time and date then I register and start the new driver. I have
tried this around 10 times each time the same errors.
I cannot use lmv since as I get a bugcheck as soon as I start the service
within osrloader.
The timedatestamp of the driver file headers is correct so still unsure of problem. I’ll create a new project and copy over the files.
Thanks for the help scott.