New
#31
Wait until you get an actual BSOD and give me that mini dump
I had 2 1E errors and three other bsod that were essencially instant. I recorded one with a camera and there arent enought lines for it to be a stop message.
the two 1E stop codes both had 0x0000000000000 (dont now how many zeroes) for everything else
In event viewer a few things caught my attention. Under error there were 2 kernel tracking errors and under informative there were 4 kernal processor power (errors?) within the last hour
"0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors..." http://www.aumha.org/a/stop.htm under 1E
it didnt save them, i checked the minidump folder and it was empty. I made sure it was still the default and it is. I ran dumpchk from the command line and it must not come with win7. The most recent minidump in event viewer was from the 10th
essentially the dump file wouldve looked like this
1E (0x0000000000, 0x0000000000, 0x0000000000, 0x000000000)
I only know what you give me.
Now we both have the same imformation
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Based upon everything that you gave me that I can use, this is what I have.
It comes back to drivers use this:
Enable the Driver Verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
I do not think it is BIOS, if it were, if you try to flash and you do not have expertise in the area, it can become worthless.
Last edited by richc46; 14 Sep 2010 at 19:48.
ya ive only used the bios to switch what boots first. and im sure you can do that with a button....
verifier is running with the two drives
So far no blue screen. Under the driver specific counter for jgogo and atipcie they both read zero. I tried it with a diffrent driver and its counting all of the pooled pages and things but these two arent arent. I dont know if its because those two only are in use on boot, but verifier is working and says the two drivers are loaded.
I saw several forums that says you should rename the jgogo file to anything else so it wont get loaded and apparently since there is little to no info on the actual driver most people seem to think it unimportant. Im going to try that and see wat happens in the morning
Didnt work... did a new stop error of
19 - BAD POOL HEADERS
0000000000000022, FFFFFA8005BEEEE00, 00000000000000000,0000000000000000
i was wondering if there was a way to show which drivers and system files are being loaded while the computer is booting. that way if it keep stopping on a certain one then that would likely be the cause