Scrambed Screen Followed by Blue Screen

T-Rent

New Member
Ok so i was given a computer. It is a desktop with a decent MSI mobo and a 250gb seagate sata drive. I loaded win 7 on it after formatting the Hard Drive. It ran fine but after running the sys for a while the whole screen scrambled. I was unable to see anything except for the mouse pointer. Then after a few seconds i got the blue screen. It recomendmended that i restart so i did then it started fine. Im not sure what woiuld cause it. Let me know any ideas
 
When you reloaded it should have given you an error code, if not go to reliability monitor and that should tell you the error code, post back!
 
^ that, the bluescreen code can tell you a lot

Sounds like either a driver crashed somewhere or the video card is buggered. Something could have overheated as well. Could be something else, but those seem most likely.

In addition to checking the code, download HWMonitor and watch the temperatures...the CPU shouldn't go above 60C (around 30-40 under load is pretty good), and any graphics card it may have shouldn't top 70 or so, though the can usually take more than that.

http://www.cpuid.com/softwares/hwmonitor.html
 
Is THis What u need?

Source
Windows

Summary
Shut down unexpectedly

Date
‎12/‎12/‎2010 9:59 PM

Status
More data required

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Files that help describe the problem
121210-24850-01.dmp
sysdata.xml
WERInternalMetadata.xml

Extra information about the problem
BCCode: 1000008e
BCP1: C0000005
BCP2: 8290CCFA
BCP3: A48DFA74
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Bucket ID: 0x8E_nt!ExFreePoolWithTag+779
Server information: 9ac53101-0a14-4ede-bb04-5f75efaba16c
 
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x84f311c8, 0x84f31348, 0x18300039). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121310-14258-01.

i also found this?
 
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x84f311c8, 0x84f31348, 0x18300039). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 121310-14258-01.

i also found this?

0x8E errors are almost always caused by hardware and 0x19 errors can be caused by bad harddrive sectors but also by other issues.

Run memtest on your RAM for a minimum of 7 Passes. You are looking for any errors. This takes a lot of time so start it before going to sleep and when you get up check it.
 
0x8E errors are almost always caused by hardware and 0x19 errors can be caused by bad harddrive sectors but also by other issues.

Run memtest on your RAM for a minimum of 7 Passes. You are looking for any errors. This takes a lot of time so start it before going to sleep and when you get up check it.

The hard drive and RAM are fine the ram is new and it did it before and after i installed it and the hard drive has been extensively tested. Any other ideas?
 
Sounds like a driver problem or something wrong with the video card. What is the motherboard model and graphics card model?
Try disabling the video card in BIOS and using the integrated GPU and see if you still get the problems.
 
well the graphics card is the one integrated in the mobo. lately it hasnt done the problem..... idk why i havnt changed anything except new thermal compound. coulld it have been that?
 
Well if your problem is gone it seems like the problem was the CPU overheating which seems to be fixed now. However, the error codes suggest the problem could be with RAM, the hard drive, or bad or incompatible drivers.
 
Well if your problem is gone it seems like the problem was the CPU overheating which seems to be fixed now. However, the error codes suggest the problem could be with RAM, the hard drive, or bad or incompatible drivers.

well i can assure the ram and the hard drive are fine.. is there anything i can do to test the drivers... any software or anything>
 
well for anyone who was curious. i reformatted the hard drive and partitioned it then installed win 7 again fresh. havent had the problem since
 
Back
Top