3 BSOD's today

Judo Flounder · Jan 21, 2009

I recently restored my Vista from a backup 1 year ago. Today I got 3 BSOD's

1) Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002A82630
BCP3: FFFFF9800C9FB100
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

2) Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002AC147A
BCP3: FFFFF98022E84C50
BCP4: 0000000000000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1
Server information: 99815fa7-6741-423c-ab51-0b2647337954

3) Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
BCCode: a
BCP1: 00000000000000D0
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002CDF5BB
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1
Server information: 47fb36db-ee35-4805-b7fa-73fcddd62f87

The third one I know said something like "IRQL_NOT_LESS_OR_EQUAL" and one of them said something like "win32k.sys The driver mistakenly marked a part of it's image pageable instead of nonpageable".

I tested my RAM and found no errors.

Does anyone know what these error codes mean?

Thanks

lordbob75 · Jan 21, 2009

Ok the third error code "IRQL_NOT_LESS_OR_EQUAL" probably means a heating problem. Next time the BSOD happens, reboot into BIOS and check CPU temp. Post it here.

I will get back to you on the other codes. Gimme a half hour or so.

~Lordbob

EDIT: Since you made that backup, have you changed ANY of your hardware?

Additional EDIT: What are the stop codes? These should appear on the BSOD itself, not the monitor thing. Can you get a shot of the screen itself?

lordbob75 · Jan 21, 2009

Bleah I fail. Ok, the third error code is more likely caused by incompatible hardware. What are your hardware specs?

~Lordbob

P.S. Still checking on the others.

Judo Flounder · Jan 21, 2009

lordbob75 said:
Ok the third error code "IRQL_NOT_LESS_OR_EQUAL" probably means a heating problem. Next time the BSOD happens, reboot into BIOS and check CPU temp. Post it here.

I will get back to you on the other codes. Gimme a half hour or so.

~Lordbob

EDIT: Since you made that backup, have you changed ANY of your hardware?

Additional EDIT: What are the stop codes? These should appear on the BSOD itself, not the monitor thing. Can you get a shot of the screen itself?

I replaced 2 sticks of RAM because they went bad but they're the same exact sticks.

As for heat issues I have overclocked my CPU from 2.6 ghz to 3.2 but I also have sufficient cooling (thermoelectric cooler). I overclocked my RAM just a teeny bit (from 24 tRC to 22 and 2.1-2.2 volts) and those have fans on them as well.

As for stop codes IIRC the one for the win32k.sys had a code of 0x000000D3.
The others had something like 0x0000000A.

Judo Flounder · Jan 21, 2009

lordbob75 said:
Bleah I fail. Ok, the third error code is more likely caused by incompatible hardware. What are your hardware specs?

~Lordbob

P.S. Still checking on the others.

Just updated them. Sorry. Should've done it in the first place lol

lordbob75 · Jan 21, 2009

Ok thanks for the codes. Ok the 0x000000D3 indicates that the system attempted to access pageable memory at a process IRQL that was too high.

If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Did it happen to list what the driver was? What was the 4th parameter of the error? That will be the address that access and caused the error. If the 3rd parameter is a 0 then it is reading, 1 means writing.

~Lordbob

Judo Flounder · Jan 21, 2009

lordbob75 said:
Ok thanks for the codes. Ok the 0x000000D3 indicates that the system attempted to access pageable memory at a process IRQL that was too high.

If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

Did it happen to list what the driver was? What was the 4th parameter of the error? That will be the address that access and caused the error. If the 3rd parameter is a 0 then it is reading, 1 means writing.

~Lordbob

Unfortunately I didn't recall seeing the driver being listed. So the codes I posted aren't sufficient enough to pinpoint the exact problem? This is going to be a nightmare trying to figure this out lol.

I forgot to mention, after I restored there were a bunch of updates I went through in Vista and one of them was an nvidia driver. Would that have something to do with the BSODs? Also, I'm not even on SP1 so would that also make a difference?

lordbob75 · Jan 21, 2009

Actually now I really look, the parameters are there, but thinking about it, it doesn't matter because it is going to be different for every computer.

Ok............ Hmmm... Try this:

1. Open Control Panel -> System and Maintenance -> System.
2. In the left “Tasks”, click on Advanced System Settings.
3. You should come to “Advanced” tab. In “Performance” section, click on Settings button.
4. Click on Advanced tab.
5. In the “Virtual Memory” section, click on Change button.
6. By default, “Automatically manage paging file size for all drives” setting is selected so that Windows Vista system can manage the paging file without user’s interruption. If you want change the paging file size, move the pagefile.sys to another drive, or disable virtual memory paging, uncheck the check box of Automatically manage paging file size for all drives.
7. Select and highlight the appropriate drive that users want to change the paging file settings under the box of “Drive [Volume Label]“.
8. To fix a permanent size for the paging file, click on Custom size button, and set the values of Initial Size (MB) and Maximum Size (MB). Both values can be of same size to make the size of pagefile.sys static. Then click on Set button.

System managed size is useful for users who do not want pagefile.sys to locate on system drive root and want to move its storage location to another drive, but still want Vista to dynamically manage and allocate the drive space for the paging usage.

To move the paging file to another drive, click on No paging file radio button, and click on Set button. Then select a different drive to set a new pagefile.sys with custom size or system managed size.

To disable paging file or virtual memory, simply set no paging files on all drives.

~Lordbob

Judo Flounder · Jan 21, 2009

lordbob75 said:
Actually now I really look, the parameters are there, but thinking about it, it doesn't matter because it is going to be different for every computer.

Ok............ Hmmm... Try this:

1. Open Control Panel -> System and Maintenance -> System.
2. In the left “Tasks”, click on Advanced System Settings.
3. You should come to “Advanced” tab. In “Performance” section, click on Settings button.
4. Click on Advanced tab.
5. In the “Virtual Memory” section, click on Change button.
6. By default, “Automatically manage paging file size for all drives” setting is selected so that Windows Vista system can manage the paging file without user’s interruption. If you want change the paging file size, move the pagefile.sys to another drive, or disable virtual memory paging, uncheck the check box of Automatically manage paging file size for all drives.
7. Select and highlight the appropriate drive that users want to change the paging file settings under the box of “Drive [Volume Label]“.

Virtual Memory Settings
8. To fix a permanent size for the paging file, click on Custom size button, and set the values of Initial Size (MB) and Maximum Size (MB). Both values can be of same size to make the size of pagefile.sys static. Then click on Set button.

System managed size is useful for users who do not want pagefile.sys to locate on system drive root and want to move its storage location to another drive, but still want Vista to dynamically manage and allocate the drive space for the paging usage.

To move the paging file to another drive, click on No paging file radio button, and click on Set button. Then select a different drive to set a new pagefile.sys with custom size or system managed size.

To disable paging file or virtual memory, simply set no paging files on all drives.

~Lordbob

Hmm...so what do you recommend I do? Disable it altogether or change the size and move it to another drive?

lordbob75 · Jan 21, 2009

Try disabling it for now, and just to see if that works. Control test.

~Lordbob

Judo Flounder · Jan 21, 2009

lordbob75 said:
Try disabling it for now, and just to see if that works. Control test.

~Lordbob

Thanks. Will do. I'll give you an update to see if anymore BSODs occur (which I'm positive I'll get. So much for being optimistic lol).

lordbob75 · Jan 21, 2009

Well even if it doesn't work, then we know one thing is down, and leaves other options open. I hope it works though.

~Lordbob

Aryanna · Jan 22, 2009

I had problems with bsod for months with my vista. I searched all the different errors for weeks and tried sutff with the bios, nothing worked. I just kept updating vista everyday, and I realized one day that it had stopped bsoding. It hasn't since then, been like almost a yr now. I pretty sure what fixed it was an update somewhere. So just keep downloading updates and cross your fingers. Good luck!

Judo Flounder · Jan 22, 2009

lordbob75 said:
Well even if it doesn't work, then we know one thing is down, and leaves other options open. I hope it works though.

~Lordbob

UPDATE: Ok. I booted up a few minutes ago and as soon as I got past the Vista loading screen...BAM! BSOD.

It read: aswMonFlt.sys

PAGE_FAULT_IN_NONPAGED_AREA

STOP: 0x00000050

aswMonFlt.sys - Address FFFFF98015F1D9FA base at FFFFF98015F09000, Datestamp 492D84A1

Another update: I just clicked the thing in Problems and Solutions after it said "Windows has recovered from an unexpected shutdown blah blah blah" to send information and here's what it said:
Problem caused by antivirus software
"Although we have not determined the specific cause of this problem, we know the problem was caused by antivirus software."

I use Avast Professional Edition. Is this a problem?

lordbob75 · Jan 22, 2009

Ok this is a memory error cause by Avast Anit-Virus. I am assuming this is on your computer... Try uninstalling it. The other possibility is bad RAM, but since the aswMonFlt.sys is Avast, then it is probably that. So uninstall Avast and see if it helps.

~Lordbob

Judo Flounder · Jan 22, 2009

lordbob75 said:
Ok this is a memory error cause by Avast Anit-Virus. I am assuming this is on your computer... Try uninstalling it. The other possibility is bad RAM, but since the aswMonFlt.sys is Avast, then it is probably that. So uninstall Avast and see if it helps.

~Lordbob

Ok so I uninstalled Avast and installed SP1 and a bunch of other updates. After everything installed I shut down completely and started up again. No problems so far. I'll see if anything else happens within the next day or so.

lordbob75 · Jan 22, 2009

Cool. Thanks for the update.

~Lordbob

Judo Flounder · Jan 22, 2009

lordbob75 said:
Cool. Thanks for the update.

~Lordbob

Np. Would you recommend I install Avast again or would I get the same error?

lordbob75 · Jan 22, 2009

That's up to you. I have no idea, but you could try.

~Lordbob

Judo Flounder · Jan 23, 2009

lordbob75 said:
That's up to you. I have no idea, but you could try.

~Lordbob

Update: Ok a few minutes ago I booted up successfully, logged on, but after a minute or two I get a message saying "Spooler subsystem app has stopped working" or something like that and the was greeted with a BSOD. The error was 0x00000024.

Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
BCCode: 24
BCP1: 00000000001904AA
BCP2: FFFFFA600DE77728
BCP3: FFFFFA600DE77100
BCP4: FFFFF8000287640C
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

I went into Problems and Solutions and here's the error codes if it helps:
Problem Event Name: APPCRASH
Application Name: spoolsv.exe
Application Version: 6.0.6001.18000
Application Timestamp: 4791a2af
Fault Module Name: WSDMon.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791ae9e
Exception Code: c0000005
Exception Offset: 0000000000017388
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 82b9
Additional Information 2: 915df94a1eb1b5df41b89c6e18848492
Additional Information 3: f0fe
Additional Information 4: bc15109271ab49ba57622c7736d029ad

3 BSOD's today

My Computer

Lord of Bobs

My Computer

Lord of Bobs

My Computer

My Computer

My Computer

Lord of Bobs

My Computer

My Computer

Lord of Bobs

My Computer

My Computer

Lord of Bobs

My Computer

My Computer

Lord of Bobs

My Computer

New Member

My Computer

My Computer

Lord of Bobs

My Computer

My Computer

Lord of Bobs

My Computer

My Computer

Lord of Bobs

My Computer

My Computer