Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bsod

30 Jun 2009   #11
Dzomlija

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by BlackRaven View Post
just had another bluescreen

Code:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xfffff683ff7e1620, 0x0000000000000000, 0x0000000000000000, 0xfffff80002c6bb1c).
im pretty sure i only installed one driver and it was the (whql) videocard driver. but the verifier bluescreens the pc even if i tell it to only monitor microsoft drivers.
STOP 0x0A:
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

The third parameter in the most recent (0x0A), has a value of 0x00, which indicates thats memory was being read when the error happened.




I'd say most assuredly that this is a driver problem, as all the STOP codes you have experienced so far points in that general direction.


My System SpecsSystem Spec
.
30 Jun 2009   #12
BlackRaven

Windows 7 64 bit
 
 

Quote   Quote: Originally Posted by Dzomlija View Post
STOP 0x0A:
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

The third parameter in the most recent (0x0A), has a value of 0x00, which indicates thats memory was being read when the error happened.




I'd say most assuredly that this is a driver problem, as all the STOP codes you have experienced so far points in that general direction.
the special pool error message was / is generated by the driver verifier. i found new drivers for my sound card, but the driver verifier still bluescreens the pc upon shutting down. i tried uninstalling the videocard driver, but that didnt help either. all the other drivers i have on my computer are built in microsoft drivers.

Quote   Quote: Originally Posted by septprince View Post
Restart your system and open the BIOS settings page. Here, turn off the following settings:

Plug and Play
Shadowing
BIOS-based virus protection feature
All caching configuration including BIOS, L2, Internal/External and writeback caching of disk controllers.
wont that slow down the pc? i dont want to solve this problem at the cost of losing performance.
My System SpecsSystem Spec
30 Jun 2009   #13
Dzomlija

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by BlackRaven View Post
the special pool error message was / is generated by the driver verifier. i found new drivers for my sound card, but the driver verifier still bluescreens the pc upon shutting down. i tried uninstalling the videocard driver, but that didnt help either. all the other drivers i have on my computer are built in microsoft drivers.


wont that slow down the pc? i dont want to solve this problem at the cost of losing performance.
Disabling the items that SeptPrince suggested will probably hurt performance, but the secret to solving a BSOD is to NEVER dismiss anything as "that can't be that cause". Sometimes the biggest problems have the smallest solutions.

Without getting of topic and into too much detail, I solved a STOP 0x124 error over a year ago by changing ONE setting in the bios back to it's default setting...
My System SpecsSystem Spec
.

30 Jun 2009   #14
BlackRaven

Windows 7 64 bit
 
 

Quote   Quote: Originally Posted by Dzomlija View Post
Disabling the items that SeptPrince suggested will probably hurt performance, but the secret to solving a BSOD is to NEVER dismiss anything as "that can't be that cause". Sometimes the biggest problems have the smallest solutions.

Without getting of topic and into too much detail, I solved a STOP 0x124 error over a year ago by changing ONE setting in the bios back to it's default setting...
i would rather throw my pc out of the window than purposely slow it down through the bios. if it solves the problem then what? am i supposed to use the pc like that? thats not really why i bought it.
My System SpecsSystem Spec
30 Jun 2009   #15
septprince

Window 7 build 7600, Xp pro(VM)
 
 

try to reset the bios and then load optimised settings..that could help..
My System SpecsSystem Spec
30 Jun 2009   #16
Dzomlija

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by BlackRaven View Post
i would rather throw my pc out of the window than purposely slow it down through the bios. if it solves the problem then what? am i supposed to use the pc like that? thats not really why i bought it.
Fair enough, but are you a Star Trek fan? Spock said in "The Undiscovered Country":

If you eliminate the impossible, whatever remains, however improbable, must be the truth.

Generally, what you need to do in your situation, is not discount any possibility, however remote. Disable the items in the BIOS as suggessted, even if it does slow your PC down. Then, do what you usually do that producues the STOP errors. If you don't get any, re-enable each item again ONE AT A TIME, rebooting after each, When the BSODs come back, then the last item you re-enabled is the culprit. If that entire excercise does not resolve the problem, then you can rest assured that the problem does not lie with the BIOS, and you can concentrate your efforts elsewhere.

Basic Troubshooting 101: Change one thing at a time and gauge the results.
My System SpecsSystem Spec
30 Jun 2009   #17
BlackRaven

Windows 7 64 bit
 
 

what else could be causing this?
My System SpecsSystem Spec
30 Jun 2009   #18
usasma
Microsoft MVP

 
 

Most (if not all) of these errors have memory access errors in common. So, the first place to start would be the inbuilt memory diagnostic.

After that, it's a matter of hunting down which driver is causing it.
Are you running Driver Verifier? If so, what settings are you using?
Here's what I recommend for Driver Verifier:
Quote:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and wait for it to crash to the Blue Screen.

Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
My System SpecsSystem Spec
30 Jun 2009   #19
BlackRaven

Windows 7 64 bit
 
 

verifier only bluescreened my pc when it was shutting down. the bluescreens always happened in the phase where the text on the screen changes to "shutting down".

the rest of the bluescreens were not triggered directly by the verifier but of couse its probably the same issue.

the problem with the driver verifier is that when i told it to only monitor the videocard driver, it bluescreened the pc. then i told it to only monitor microsoft drivers and it bluescreened the pc again with the same error message. so it looks as if it doesnt matter which driver is monitored by it.

the built in memory diagnostic tool didnt find any problems. im gonna run memtest86 overnight to make sure the ram is fine.

im also thinking of installing xp on a seperate partition and check the driver verifier in it and the o/s in general if it bluescreens too.

dwm.exe always crashes (like 4 out of 10 times) with the usual crash window upon shutting down (before the desktop fades out). according to the event logs the crashes are caused by fraps. i wonder if fraps could be causing the bluescreens as well. disabled it now and removed it from the startup list.
My System SpecsSystem Spec
01 Jul 2009   #20
BlackRaven

Windows 7 64 bit
 
 

memtest ran for 11,5 hours and showed no problems.
My System SpecsSystem Spec
Reply

 Bsod




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:29.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App