BSOD unknown causes.

Windows 7 Home Premium 64-bit.
About 1 year old computer, wich i put together myself.
It has BSOD before but i ignored it, and didnt save eny data.

If theres eny more information you need just ask, i really dont know what to add here.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1061

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFF88002FD7180
BCP4: 0000000000000003
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

wildseven said:

Windows 7 Home Premium 64-bit.
About 1 year old computer, wich i put together myself.
It has BSOD before but i ignored it, and didnt save eny data.

If theres eny more information you need just ask, i really dont know what to add here.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1061

Additional information about the problem:
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFF88002FD7180
BCP4: 0000000000000003
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Best advice that I've seen about this error (from here: https://www.sevenforums.com/crashes-d...tml#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.[/QUOTE]

Thanks for the fast reply.
I took a look inside today, and it certanly was dustier then i expected.
So it might have been the dust making the problems, atleast im hoping so :P thanks again.

wildseven said:

Thanks for the fast reply.
I took a look inside today, and it certanly was dustier then i expected.
So it might have been the dust making the problems, atleast im hoping so :P thanks again.

Good luck