Solved Random BSOD - ntoskrnl.exe (nt+7cc40) Please Help

[stonethickwood]

Hello,

I am getting BSOD every couple of days with no apparent reason sometime with doing virus scans, running windows movie maker and sometime while idle. Not sure what's going on please help - I have attached .dmp for assessment.

http://www.sevenforums.com/attachment.php?attachmentid=202148&stc=1&d=1331424155

Hopefully someone can advise me on this not really a huge problem but would like to resolve it before it becomes one.

 

[zigzag3143]

Related to your directx

Diagnosing basic problems with DirectX

 

[stonethickwood]

more problems

I tried to figure it out with the directx ... but everything seem to be fine. I am now getting an array or BSOD please see attach files.

Not sure what happening but this is getting frustrating.

Thanks in advance

 

[zigzag3143]

I tried to figure it out with the directx ... but everything seem to be fine. I am now getting an array or BSOD please see attach files.

Not sure what happening but this is getting frustrating.

Thanks in advance

These gave us more information



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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/Win7 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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and 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.

 

[stonethickwood]

Ok.... seems to be the ram.... I upgraded it a while back after reading your last reply I simply put in my stock ram and now it seems to be running fine (no BSOD) but I have taken the ram back they test it and say it's fine - is there any changes in the BIOS that I need to make before I upgrade my RAM.

Specification of PC - HP Pavilion HPE 541F
MoBo: H-RS880 uATX
Video: ATI Radeon 6770
HD - Seagate Barricuda 2tb
Ram - Stock 8gb (trying to upgrade with Corsair Vengance 16gb)
Processor - AMD Phenom II X6


But I have a few other problems hopefully you can assist me with:

1) My Computer stick in limbo on the shutting down screen
2)When I attach an usb device which already has drivers installed it is not noticed till I force a hard restart.

Please provide any Hint or Fixes

Thank in Advance

Stone

 

[zigzag3143]

Ok.... seems to be the ram.... I upgraded it a while back after reading your last reply I simply put in my stock ram and now it seems to be running fine (no BSOD) but I have taken the ram back they test it and say it's fine - is there any changes in the BIOS that I need to make before I upgrade my RAM.

Specification of PC - HP Pavilion HPE 541F
MoBo: H-RS880 uATX
Video: ATI Radeon 6770
HD - Seagate Barricuda 2tb
Ram - Stock 8gb (trying to upgrade with Corsair Vengance 16gb)
Processor - AMD Phenom II X6


But I have a few other problems hopefully you can assist me with:

1) My Computer stick in limbo on the shutting down screen
2)When I attach an usb device which already has drivers installed it is not noticed till I force a hard restart.

Please provide any Hint or Fixes

Thank in Advance

Stone

Best to start a new thread for the new issues. You will get more people looking it them that way