Forum Home
Press F1
 
Thread ID: 118141 2011-05-21 06:32:00 BSOD issues - Win7 X64 supersi (8401) Press F1
Post ID Timestamp Content User
1203871 2011-05-21 06:32:00 I have Win 7 X64 on 2 x 320GB Striped RAID 0 and 4 x 1gb RAM.

I keep getting BSOD's see pics (sorry Microsoft's stupid error reporting window won't go full screen, so there's two pics).

Attached file: 1.jpg (www.imagef1.net.nz) (74 KB)

and

Attached file: 2.jpg (www.imagef1.net.nz) (77 KB)

Is this my RAM or my hard drives?
supersi (8401)
1203872 2011-05-21 06:34:00 Get bluescreenview (www.nirsoft.net) run it. What does it say is the cause Speedy Gonzales (78)
1203873 2011-05-21 06:38:00 Thanks Speedy,

How do I interpret the data?
supersi (8401)
1203874 2011-05-21 06:40:00 Just install / run it the dmp folder is the default folder. Just tell us what file it says is the cause Speedy Gonzales (78)
1203875 2011-05-21 06:47:00 Ok, here's a screenshot. Attached file: DUMP.jpg (www.imagef1.net.nz) (582 KB) supersi (8401)
1203876 2011-05-21 06:49:00 The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors. This default Windows error handler typically intercepts these problems if error-handling routines are not present in the code itself.


These errors may be caused by one or more of the following:

Hardware failure (memory, processor, or motherboard).
Drivers installed by third-party software.
pctek (84)
1203877 2011-05-21 06:51:00 Great. What's the best way to isolate a hardware problem? Should I start by pulling RAM one by one and see if BSOD's go away? supersi (8401)
1203878 2011-05-21 07:05:00 Is SP1 on this? This may or may not apply (support.microsoft.com) but thats for RAID 5

Mcafee isnt on this is it?
Speedy Gonzales (78)
1203879 2011-05-21 07:11:00 SP1 is on. No MacAfee, I use Avast. supersi (8401)
1203880 2011-05-21 07:21:00 This may or may not be of any help -- Click start, type in reli Open Reliability history - where its crashed there should be an red circle with an X, click it, and hopefully in the description, may be the cause (in more detail) This would be for a Software/Driver issue mainly. wainuitech (129)
1 2