Bsod

[BlackRaven]

hey guys

i recently bought a new pc and installed windows 7 rc1 64 bit on it as the primary operating system.

motherboard: gigabyte ma770-ud3p
cpu: amd phenom II x3 720
memory: ocz reaper 2x2gb ddr3 1600mhz 7-7-7-24 CR2
hard drive: samsung 750gb

there are components that have been brought over from my "old" pc:

videocard: galaxy geforce 8800gt cm (driver 186.18 whql)
hard drive: hitachi deskstar t7k250 160gb
psu: corsair vx450w

everything is running at default speeds.

ive been getting bluescreens out of nowhere for no apparent reason. theres no consistency in the sense that the error messages are always different.

• i dont have all the dump files from the previous bluescreens but the last few ones pointed to ntoskrnl.exe.

• if i turn on the driver verifier the pc bluescreens upon shutting down with the following error message: special pool detected memory corruption.

• i tried to isolate the driver thats causing the bluescreens by first only selecting the videocard driver, second by selecting only the microsoft drivers but the pc bluescreened in both cases.

• sfc /scannow shows no problems.

heres a list of programs that i have installed. please tell me if you see anything thats known to cause bluescreens on windows 7.

any ideas?

edit: forgot to mention the bluescreens always happen when im in windows and never when im playing.

 

[septprince]

can you boot in safe mode??
Hve you ran windows update after installing RC1?

 

[BlackRaven]

yes and yes.

 

[septprince]

type event log in the start search box. Then open it, see if there is any log about the error if possible post a screenshot.

 

[zigzag3143]

hey guys

i recently bought a new pc and installed windows 7 rc1 64 bit on it as the primary operating system.

motherboard: gigabyte ma770-ud3p
cpu: amd phenom II x3 720
memory: ocz reaper 2x2gb ddr3 1600mhz 7-7-7-24 CR2
hard drive: samsung 750gb

there are components that have been brought over from my "old" pc:

videocard: galaxy geforce 8800gt cm (driver 186.18 whql)
hard drive: hitachi deskstar t7k250 160gb
psu: corsair vx450w

everything is running at default speeds.

ive been getting bluescreens out of nowhere for no apparent reason. theres no consistency in the sense that the error messages are always different.

• i dont have all the dump files from the previous bluescreens but the last few ones pointed to ntoskrnl.exe.

• if i turn on the driver verifier the pc bluescreens upon shutting down with the following error message: special pool detected memory corruption.

• i tried to isolate the driver thats causing the bluescreens by first only selecting the videocard driver, second by selecting only the microsoft drivers but the pc bluescreened in both cases.

• sfc /scannow shows no problems.

heres a list of programs that i have installed. please tell me if you see anything thats known to cause bluescreens on windows 7.

any ideas?

edit: forgot to mention the bluescreens always happen when im in windows and never when im playing.

OK
the only way I can really see the apps you have installed is to pull it out and inlarge it 500% but I noticed you have 5 benchmarking apps, 4 different kinds of C++ (including 1 for 32bit and 1 for 64bit) 3 dated the same day.

Did you install win 7 on june 13? when did the probs start?

could you snip another pic and upload it. I will comment the lines that might be giving you grief

Hope this helps

Ken

 

[BlackRaven]

type event log in the start search box. Then open it, see if there is any log about the error if possible post a screenshot.

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000044 (0xfffffa800574f6f0, 0x0000000000000eae, 0x0000000000000000, 0x0000000000000000). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000003452, 0x000007fefa27b000, 0xfffff700010833a0, 0x0000000000000000). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff98026c5cfc0, 0xfffff98026c5ce3e, 0x0000000000f14040, 0x0000000000000032). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff98009fc2ff0, 0xfffff98009fc2ffc, 0x000000000067000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff98009724ff0, 0xfffff98009724ffc, 0x000000000009000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9801d85aff0, 0xfffff9801d85affc, 0x000000000089000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9800ebeeff0, 0xfffff9800ebeeffc, 0x000000000023000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9800df88ff0, 0xfffff9800df88ffc, 0x000000000031000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9800d296ff0, 0xfffff9800d296ffc, 0x0000000000a9000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9800cc44ff0, 0xfffff9800cc44ffc, 0x000000000067000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9800abb4ff0, 0xfffff9800abb4ffc, 0x00000000006f000c, 0x0000000000000024). 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9803ba26ff0, 0xfffff9803ba26ffc, 0x0000000000c9000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c1 (0xfffff9802c0dcff0, 0xfffff9802c0dcffc, 0x000000000055000c, 0x0000000000000024).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000004e (0x0000000000000099, 0x000000000011cbca, 0x0000000000000002, 0x00000000000ce3c9).

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002fa34df, 0xfffff88007c200b0, 0x0000000000000000).

 

[BlackRaven]

OK
the only way I can really see the apps you have installed is to pull it out and inlarge it 500% but I noticed you have 5 benchmarking apps, 4 different kinds of C++ (including 1 for 32bit and 1 for 64bit) 3 dated the same day.

could you snip another pic and upload it. I will comment the lines that might be giving you grief

Hope this helps

Ken

direct link: http://i543.photobucket.com/albums/gg456/BlackRavenHU/programs.jpg

edit: i have no idea when it started.

 

[Dzomlija]

Wow. That's a lot of STOP errors. From what I've been able to find, you have some serious driver problems (Are you by any chance using BETA drivers?):

STOP 0x44:
The MULTIPLE_IRP_COMPLETE_REQUESTS bug check has a value of 0x00000044. This indicates that a driver has tried to requested an IRP be completed that is already complete

STOP 0xC1:
The SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION bug check has a value of 0x000000C1. This indicates that the driver wrote to an invalid section of the special pool.

STOP 0x4E:
The PFN_LIST_CORRUPT bug check has a value of 0x0000004E. This indicates that the page frame number (PFN) list is corrupted.

 

[BlackRaven]

just had another bluescreen

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.

 

[septprince]

The following Stop 0x0000000A error message may be displayed on your system during or after you have installed the os.

Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL

Here, Address x has base at x - filename

The value of the parameters in the error message help in determining the specific issues that may have generated the error message:

Parameter1: Refers to an address that was incorrectly referenced.
Parameter2: Refers to an internal request level (IRQL) that had to access the memory.
Parameter3: Refers to the type of access-if the value is ‘1′ it refers to the ‘write’ operation, if the value is ‘0′ it refers to the ‘read’ operation.
Parameter4: Refers to the instruction address that referenced the PC memory in parameter1.
Cause of the Error

Stop 0x0000000A or Stop 0x0A error usually occurs when a driver installed on your system tries to gain access to an incorrect memory address.

The error may also occur if there is a hardware malfunction or if you have incompatible software on the system.

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.

If it doesn`t help
Try updating your Bios..

 

[Dzomlija]

just had another bluescreen

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.

 

[BlackRaven]

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.

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.

 

[Dzomlija]

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...

 

[BlackRaven]

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.

 

[septprince]

try to reset the bios and then load optimised settings..that could help..

 

[Dzomlija]

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.

 

[BlackRaven]

what else could be causing this?

 

[usasma]

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:

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.

 

[BlackRaven]

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.

 

[BlackRaven]

memtest ran for 11,5 hours and showed no problems.