Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Ok I am all kind of lost here. Not sure I am posting in the right place but never had this problem until Win 7 so I'll start here.
For about a week now I have been getting random BSODs. Not being the brightest when it comes to software issues I tried relentlesly to research using the data on the blue screen itself and gave up. Finally loaded windows debugging tools to read the minidump.
I originally suspected a memory issue as that is almost all google would tell me about what I saw on the blue screen. I have run memtest at least 4 different ocassions for far too many hours. Funny it never crashes then. I got no errors. I have updated every drive I have or pulled the hardware if I could not find a win 7 driver for it. I had one old program that said it was not compatible, Music Match, I uninstalled it.
I don't have to be doing anything intensive to get a crash. It has happened while just typing a letter.
Back to Windbg, I won't post the whole thing unless asked to. I don't fully understand this program but these seem of interest:
SYSTEM_SERVICE_EXCEPTION (3b)
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: iexplore.exe
FOLLOWUP_NAME: Pool_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!ExDeferredFreePool+242Thanks for any help
Likely
Edit:: I have run hard drive diagnostics from manufacturer ( WD ), both drives passed.The only new hardware is a psu after old one died a while back, new one is about 2 1/2 weeks in service now.
I want to go like my grandfather did. Peacefully in his sleep. Not screaming at the top of my lungs like the passengers in his car.(\__/)
(='.'=)
(")_(")

FOLLOWUP_NAME: Pool_corruption
Bad driver corrupted the the pool. Sadly, this is one of the hardest problems to track down. Your best bet would be to use the Driver Verifier to stick random drivers into the special pool. Just don't do all of the drivers at once; you'll cripple your system's performance.

Okay I am trying the verifier now.
Likely
I want to go like my grandfather did. Peacefully in his sleep. Not screaming at the top of my lungs like the passengers in his car.
(\__/)
(='.'=)
(")_(")

Good luck! Microsoft's drivers should be safer than third party. I've also had problems with video drivers.

Since starting the verifier I have gotten the BSOD 3 times with
IRQL NOT LESS OR EQUAL each time.
That's new. I am checking all that is not microsoft incuding video drivers.
LikelyI want to go like my grandfather did. Peacefully in his sleep. Not screaming at the top of my lungs like the passengers in his car.
(\__/)
(='.'=)
(")_(")

Little lost. What am I looking for?
LikelyI want to go like my grandfather did. Peacefully in his sleep. Not screaming at the top of my lungs like the passengers in his car.
(\__/)
(='.'=)
(")_(")

Well, whatever is now giving you those IRQ_NOT_LESS_OR_EQUAL, I'd assume.
But a quick rundown, since information seems to be lacking:
1 - Create custom settings
2 - Select individual settings
3 - Select "Special pool" and/or "Pool tracking"
4 - Select driver names from a list
5 - Pick some drivers. The MS/standard drivers should be okay.
6 - Finish and reboot
7 - Use your PC like normal, and wait for a BSOD 0xC1 or 0xC4
8 - Windbg should now know the faulty driver
9 - If the bad driver was found, run the command "verifier /reset" to disable the special pool / pool checking. If not, repeat with a different set of drivers. Hey, I said pool corruption was a pain to track down.

Sorry I should have stated I knew nothing of the verifier.
1 - Create custom settings Check
2 - Select individual settings Check
3 - Select "Special pool" and/or "Pool tracking" At this point I had selected all but low resources simulation, this has now been changed.
4 - Select driver names from a list
5 - Pick some drivers. The MS/standard drivers should be okay. I have selected all none microsoft drivers in this list. Not that many, 6 I think
6 - Finish and reboot Check
7 - Use your PC like normal, and wait for a BSOD 0xC1 or 0xC4
8 - Windbg should now know the faulty driver
9 - If the bad driver was found, run the command "verifier /reset" to disableSo basicaly I am now looking for another crash?
I got the "IRQ_NOT_LESS_OR_EQUAL" once more at that point I lost my mouse. after reinstalling that no BSOD since. Should I clear or delete previous minidumps?
LikelyI want to go like my grandfather did. Peacefully in his sleep. Not screaming at the top of my lungs like the passengers in his car.
(\__/)
(='.'=)
(")_(")

At this point I had selected all but low resources simulation, this has now been changed.
That's the standard Verifier setup. The only problem would be a performance impact. If the performance hit doesn't bother you, feel free to keep them on.So basicaly I am now looking for another crash?
Pretty much, unless you think the mouse drivers were the problem. If so, feel free to use the /reset switch.

The performance hit doesn't seem bad yet. I think the mouse may have had something to do with the IRQ_NOT_LESS_OR_EQUAL becuase that seemed to be coming fairly steady and has not reocurred since the reinstall. The Pool Corruption however I am still worried about. It has not crashed yet again but those were very random sometimes hours apart sometimes as much as a day and a half so for a good while I am going to let the verifier run unless that would cause me another problem and from what I have read it shouldn't.
The only settings I have selected now are what you recomended.
Seems odd but when doing any maintenance or running a program designed to try and find the problem I don't seem to have a problem.
Likely
I want to go like my grandfather did. Peacefully in his sleep. Not screaming at the top of my lungs like the passengers in his car.
(\__/)
(='.'=)
(")_(")

Seems odd but when doing any maintenance or running a program designed to try and find the problem I don't seem to have a problem.
Sometimes, when you're really, really lucky, the Verifier alters the timing of the drivers just enough that everything behaves.Normally this happens because the driver developer didn't spend enough time testing the drivers without using testing tools.
EDIT: If you have 85 minutes to kill, there's a good lecture by Mark Russinovich on Windows crash dumps.

![]() |
![]() |
![]() |
| Login or Register to Reply | |
| Login | Register |
| Ads by Google |