• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

what is and how to use verifier.exe

Well i have many topics in here about my stupid BSOD problems

so ive decided to try this verifier thing out, i want to try it on NVENET.sys cause thats one of the files the BSOD has noted.

anyone use it before, what will it tell me?
 
Originally posted by: tightflks
Well i have many topics in here about my stupid BSOD problems

so ive decided to try this verifier thing out, i want to try it on NVENET.sys cause thats one of the files the BSOD has noted.

anyone use it before, what will it tell me?


Sure. It will test all / selected drivers and tell you (via the fact that you get a BSOD) whether the driver is any good or not. I tested it with my S3/(some old S3 8MB graphics card) drivers for XP and immediately BSOD's the box. Fortunately, I hadn't logged in yet, so I did a LKG and I was fine.

If you have a more specific question, just ask.
 
Originally posted by: tightflks
micorcode?

ie update the BIOS to the latest version, he means, perhaps ?? .... a few CPUs having microcode under...18 or so... have an issue....
 
Yeah, the microcode is normally associated with the processor, and you update that by flashing the BIOS.

Based on the dump we looked at earlier of yours, I recommended doing this and updating the drivers for the on-board devices (the nforce stuff).
 
its been updated, and i updated drivers, and used a bunch of different sets and still got it

i think it was due to overheating

cause when i opened up the case to clean it, there was thick layer of dust on top of the heat sink

so when i started up the computer, i forgot to plug the fans in, and it just shutdown, and i noticed when i looked into the event viewer, the error in the save dump ws the same code as the errors i moslty recieved

makes sense, i got the eorrors when ripping dvds (takes a lo of cpu), and installing xp which i hope takes a lot of xp, but dont explain why it happen over night, mayeb it just got hot

so hopefully cpu over heating is the problem
 
Back
Top