Blue screen help!

[opelrsx]

2 more dump files attached.

 

[opelrsx]

still BSOD every day please see the most recent dump files.

 

[zigzag3143]

still BSOD every day please see the most recent dump files.

Virtually all of these and previous crashes were caused by a memory exception. These newest were not driver verified.

I dont remember what the results for memtest were (I am on a portable device).

If you cannot resolve these soon it may be time for a clean install.


One item of note. The CCC was running in two of the most recent. I would remove it and just install the driver.

 

[opelrsx]

Virtually all of these and previous crashes were caused by a memory exception. These newest were not driver verified.

I dont remember what the results for memtest were (I am on a portable device).

If you cannot resolve these soon it may be time for a clean install.


One item of note. The CCC was running in two of the most recent. I would remove it and just install the driver.

memtest reports no error.

Verifier is now on again. I will post back.

will remove the CCC

 

[opelrsx]

Verifier on,
CCC removed
two BSOD today so far dump file attached

 

[zigzag3143]

Verifier on,
CCC removed
two BSOD today so far dump file attached

Your BC code 101


Best advice that I've seen about this error (from here: http://www.sevenforums.com/crashes-...lock-interrupt-bsod-101-error.html#post356791 )

What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)

So, check the drivers
Then check the inside of the case (temperature, voltage, dust, etc).
Then run some hardware stress tests

Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.