Bluescreen issues, again

2010-04-16 08:01:39

#1

Bevo: Nah; +718|6779|Austin, Texas

Sooo I just built my new computer not even a week ago, and it seems already I'm having issues with bluescreens.

Just now I started up windows 3 times and got bluescreens after entering windows for about a minute. Now none of my programs are working and they're all closing.

What the fuck is going on?

ed: Windows 7

Last edited by Bevo (2010-04-16 08:02:27)

2010-04-16 08:02:08

#2

Finray: Hup! Dos, Tres, Cuatro; +2,629|6047|Catherine Black

Memtest again.

E: Are you using the same hard-drive and windows install?
E2: Maybe you should just RMA the mobo..

Last edited by Finray (2010-05-06 08:43:31)

2010-04-16 08:03:09

#3

Bevo: Nah; +718|6779|Austin, Texas

Finray wrote:

Memtest again.

E: Are you using the same hard-drive and windows install?

No. My old HDD is still in my comp but I'm booting from a new one

Last edited by Bevo (2010-04-16 08:03:27)

2010-04-16 08:04:07

#4

Finray: Hup! Dos, Tres, Cuatro; +2,629|6047|Catherine Black

Any other parts you're sharing from the old computer?

Try disconnecting your old HDD.

2010-04-16 08:05:22

#5

Bevo: Nah; +718|6779|Austin, Texas

Finray wrote:
Any other parts you're sharing from the old computer?

Try disconnecting your old HDD.

No, just the case and old HDD.

FUCK just got another bluescreen. what the hell

2010-04-16 08:11:12

#6

Bevo: Nah; +718|6779|Austin, Texas

Great.

DC'd my old HDD, ran memtest and it rebooted itself 2 seconds in.

I fucking hate computers right now.

2010-04-16 08:19:59

#7

13urnzz: Banned; +5,830|6756

when you get a bluescreen, it will tell you all you need to know -

"fatal exception 0x000007b" with the offending process. please write it down . . .

2010-04-16 08:28:51

#8

Bevo: Nah; +718|6779|Austin, Texas

burnzz wrote:
when you get a bluescreen, it will tell you all you need to know -

"fatal exception 0x000007b" with the offending process. please write it down . . .

I'd try to get bluescreen viewer back but I'm afraid it won't stay in windows long enough to actually get info

there's a whole mess of em, they're all different, the bluescreens

2010-04-16 08:33:58

#9

Yellowman03: Once Again, We Meet at Last; +108|6493|Texas

Try taking a picture.

Also, try reinstalling windows if you can't find anything else.

2010-04-16 09:12:58

#10

max: Vela Incident; +1,652|6826|NYC / Hamburg

_{once upon a midnight dreary, while i pron surfed, weak and weary, over many a strange and spurious site of ' hot xxx galore'. While i clicked my fav'rite bookmark, suddenly there came a warning, and my heart was filled with mourning, mourning for my dear amour, " 'Tis not possible!", i muttered, " give me back my free hardcore!"..... quoth the server, 404.}

2010-04-16 09:41:38

#11

Jaekus: I'm the matchstick that you'll never lose; +957|5437|Sydney

I'm no genius by any stretch but system hardware specs can't hurt here either...

2010-04-16 10:16:43

#12

Bevo: Nah; +718|6779|Austin, Texas

650 W Antec
Gigabyte 790 GX
ATI HD 5850
4gig Gskill DDR3
AMD 965 quad core
WD SATA3 HDD
Win 7 64 bit

Testing the memory now, if those both pass I'll try replacing with old PSU, then I guess reinstall windows, past that I'm lost

2010-04-16 10:45:29

#13

Bevo: Nah; +718|6779|Austin, Texas

Both sticks passed individually and the memtest rebooted itself both times when trying to test both at one. Tried switching them.

Here's the log of the bluescreens.

Code:

==================================================
Dump File         : 041610-13821-01.dmp
Crash Time        : 4/16/2010 12:51:09 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff683`ff7d3a80
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`028d21e2
Caused By Driver  : ndis.sys
Caused By Address : ndis.sys+906f4
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\041610-13821-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 041610-14570-01.dmp
Crash Time        : 4/16/2010 9:59:32 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00000411
Parameter 2       : fffff680`00014638
Parameter 3       : cc100000`becca886
Parameter 4       : fffff680`000ebab3
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\041610-14570-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 041610-14336-01.dmp
Crash Time        : 4/16/2010 9:55:28 AM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00000403
Parameter 2       : fffff680`00004598
Parameter 3       : f5300000`966c0025
Parameter 4       : fffff6fc`004b3600
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+432e
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\041610-14336-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 041610-13884-01.dmp
Crash Time        : 4/16/2010 9:53:25 AM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`000c614a
Parameter 3       : 00000000`00000002
Parameter 4       : 00000000`000c4c29
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\041610-13884-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 041510-15568-01.dmp
Crash Time        : 4/15/2010 10:09:48 AM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff880`04020cf7
Parameter 3       : fffff880`05c6c6a8
Parameter 4       : fffff880`05c6bf10
Caused By Driver  : dxgmms1.sys
Caused By Address : dxgmms1.sys+1ded3
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\041510-15568-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 041510-15802-01.dmp
Crash Time        : 4/15/2010 9:41:55 AM
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 00000000`001904fb
Parameter 2       : fffff880`0373f718
Parameter 3       : fffff880`0373ef80
Parameter 4       : fffff880`010edc55
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+acc55
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\minidump\041510-15802-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7600
==================================================

Last edited by Bevo (2010-04-16 10:55:16)

2010-04-16 10:55:57

#14

Kimmmmmmmmmmmm: ©; +1,811|6255

good luck bevo

2010-04-16 10:56:57

#15

Bevo: Nah; +718|6779|Austin, Texas

cheers kim

2010-04-16 11:35:28

#16

Finray: Hup! Dos, Tres, Cuatro; +2,629|6047|Catherine Black

Bevo, all those drivers are Windows drivers. Leads me to believe your installation is corrupt. Try reinstalling.

2010-04-16 11:41:53

#17

Bevo: Nah; +718|6779|Austin, Texas

I booted it up about 20 minutes ago and have had no issues. I don't know what the fuck to say.

2010-04-16 11:54:17

#18

Beduin: Compensation of Reactive Power in the grid; +510|6008|شمال

lel?

الشعب يريد اسقاط النظام
...show me the schematic

2010-04-16 12:23:12

#19

SonderKommando: Eat, Lift, Grow, Repeat....; +564|6918|The darkside of Denver

Well guaranteed thats a hardware issue. Double check your temps, how do you have your memory configured? Did you test each slot/DIMM configuration to isolate a memory issue? I see that you ran them induvidually, in the same slot?? Try running a few passes with each dimm in slot A1, then A1 to B1 to B22, and see what the results are. maybe somthing is wrong with teh memory controller on the board if it cant run the memory in dual channel, or it could be a bad bank/slot. What are your cpu temps bevo? did you make sure that your HSF is adequately seated?

2010-04-16 12:26:14

#20

Bevo: Nah; +718|6779|Austin, Texas

Memory... configured. I ono?

Yeah I ran them both in slot 1. CPU temp is normal (35c idle) and HSF is fine.

No issues in the past hour or so

2010-04-16 13:03:05

#21

SonderKommando: Eat, Lift, Grow, Repeat....; +564|6918|The darkside of Denver

Bevo wrote:
Memory... configured. I ono?

Yeah I ran them both in slot 1. CPU temp is normal (35c idle) and HSF is fine.

No issues in the past hour or so

your board has two yellow and two red slots, four total. Assuming on your board DIMMS in slots A1/2 or B1/2 is for Dual channel. Do you have both sticks in A bank or B bank?

2010-04-16 15:19:08

#22

Bevo: Nah; +718|6779|Austin, Texas

Both in A. Ran A-OK for about 2 hours before I left for class. Been sitting idle for the past hour and no issues.

Maybe it was a fluke? Iono.

2010-04-16 15:31:32

#23

King_County_Downy: shitfaced; +2,791|6856|Seattle

If you're getting random BSOD's it could be PSU or an optical drive even. Random BSOD's are a bitch. I'd start looking there if your memtest passed.

Sober enough to know what I'm doing, drunk enough to really enjoy doing it

2010-04-16 18:20:17

#24

SonderKommando: Eat, Lift, Grow, Repeat....; +564|6918|The darkside of Denver

my whole thing is this
IRQL_NOT_LESS_OR_EQUAL
IRQ is the interupt request from hardware to the CPU.. so some hardware is not communicating with the mobo to teh CPU. You could go barebones and slowly add hardware to teh machine till you start getting a bsod.

2010-04-16 19:55:36

#25

alexb: <3; +590|6198|Kentucky, USA

Run a SMART test on the hard drive, it could be bad - fltmgr.sys is related the file system manager.

BF2S Forums Bluescreen issues, again

Finray wrote:

Finray wrote:

burnzz wrote:

Code:

Bevo wrote:

Board footer