Random BSODs that are baffling - Occur at any time

Russ

With prime showing that error I would think hardware but your comment about running 6 hours in safe mode without problem makes me think software.

It might be easier to -reinstall win 7 clean than to RMA the computer. At least then if it re-occured you can eliminate software.

Just a thought can you run a system file check to verify the OS files

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

zigzag3143 said:

Russ

With prime showing that error I would think hardware but your comment about running 6 hours in safe mode without problem makes me think software.

It might be easier to -reinstall win 7 clean than to RMA the computer. At least then if it re-occured you can eliminate software.

Just a thought can you run a system file check to verify the OS files

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

Thanks for the reply.

I have ran SFC /SCANNOW. This is the result:

Windows Resource Protection did not find any integrity violations.

image attached.

Had a few more since my last post, MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXEPTION. Nothing different really, except I can't give you the dumps as windows/minidump is empty.

Russ

Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result

There is a test called driver verifier that would catch an offending driver. You might give that a try.

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/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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.

zigzag3143 said:

Russ

Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result

There is a test called driver verifier that would catch an offending driver. You might give that a try.

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/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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.

Hi,

I have re-ran verifier. I had about 7-8 blue screens in a row, as expected I suppose. Some of these were:

RTKVHD.sys (?) multiple of them, my comp restarts quickly so i only catch a few seconds. I believe this is Realtek drivers. One BSOD may have been '64' as well, I've had these before.

APC (Possibly API? Sorry they're quick)_INDEX_MISMATCH (?) Never had this before.

MEMORY_MANAGEMENT, a usual occurence.

SYSTEM_SERVICE_EXEPTION, usual again.

IRQL_NOT_LESS_OR_EQUAL, usual.

It crashed as soon as it hit the 'welcome' screen before it loads the desktop once, then got into windows for a few seconds on the second attempt before crashing, it did this a few times before crashing at the welcome screen again before finally being 'stable' for a minute or so that I could get to verifier and reset the settings and restart my pc.

I hope this helps.

Russ.

RussUK said:

zigzag3143 said:

Russ

Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result

There is a test called driver verifier that would catch an offending driver. You might give that a try.

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/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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.

Hi,

I have re-ran verifier. I had about 7-8 blue screens in a row, as expected I suppose. Some of these were:

RTKVHD.sys (?) multiple of them, my comp restarts quickly so i only catch a few seconds. I believe this is Realtek drivers. One BSOD may have been '64' as well, I've had these before.

APC (Possibly API? Sorry they're quick)_INDEX_MISMATCH (?) Never had this before.

MEMORY_MANAGEMENT, a usual occurence.

SYSTEM_SERVICE_EXEPTION, usual again.

IRQL_NOT_LESS_OR_EQUAL, usual.

It crashed as soon as it hit the 'welcome' screen before it loads the desktop once, then got into windows for a few seconds on the second attempt before crashing, it did this a few times before crashing at the welcome screen again before finally being 'stable' for a minute or so that I could get to verifier and reset the settings and restart my pc.

I hope this helps.

Russ.

Russ we really need the driver verifier enabled DMPS

zigzag3143 said:

RussUK said:

zigzag3143 said:

Russ

Memtest tests the ram outside of the windows environment. It probably is some driver corrupting it, but I am concerned about the prime95 result

There is a test called driver verifier that would catch an offending driver. You might give that a try.

Hi,

I have re-ran verifier. I had about 7-8 blue screens in a row, as expected I suppose. Some of these were:

RTKVHD.sys (?) multiple of them, my comp restarts quickly so i only catch a few seconds. I believe this is Realtek drivers. One BSOD may have been '64' as well, I've had these before.

APC (Possibly API? Sorry they're quick)_INDEX_MISMATCH (?) Never had this before.

MEMORY_MANAGEMENT, a usual occurence.

SYSTEM_SERVICE_EXEPTION, usual again.

IRQL_NOT_LESS_OR_EQUAL, usual.

It crashed as soon as it hit the 'welcome' screen before it loads the desktop once, then got into windows for a few seconds on the second attempt before crashing, it did this a few times before crashing at the welcome screen again before finally being 'stable' for a minute or so that I could get to verifier and reset the settings and restart my pc.

I hope this helps.

Russ.

Russ we really need the driver verifier enabled DMPS

I still don't appear to be having any. When I check my windows/minidump folder it is empty, and Blue Screen View also shows up no dumps. I don't seem to be having any dumps saving. I have uploaded the 'BSOD Dump & System File Collection' for you to see.

A perfmon report is also in the rar, incase it helps.

I've also just checked Event Viewer and I'm having tons and tons of 'Critical' messages, is this normal? An image is attached.

Hi again, I've had 4+ more bluescreens since my last reply. I don't know what else to try other than another full re-install of windows from scratch, which I would like to avoid.

Do you have anything else I could try?

RussUK said:

Hi again, I've had 4+ more bluescreens since my last reply. I don't know what else to try other than another full re-install of windows from scratch, which I would like to avoid.

Do you have anything else I could try?

I am not even sure if a re-install would help. it may be hardware

zigzag3143 said:

RussUK said:

Hi again, I've had 4+ more bluescreens since my last reply. I don't know what else to try other than another full re-install of windows from scratch, which I would like to avoid.

Do you have anything else I could try?

I am not even sure if a re-install would help. it may be hardware

Thanks for the reply.

Great, how would I find out which is the faulty hardware? I'm guessing my processor, as it is a new mobo, new ram and i very much doubt it to be my 5850. Prime 95 shows the error on a core when I run the blend test, so does OCCT, images attached. It fails too. I'm guessing processor.

Arghh, just so happens to be the most expensive change :P Oh well, I'll just go for the 1090T or 1100T black edition processors instead since they're better.

I imagine I'll ring AMD and tell them my problem with my processor, and they'll RMA it?