Windows 7 64bit keeps freezing and giving BSOD

Joined
Apr 8, 2002
Messages
650
been giving me problems all week after installing on a new build. I would get bsod randomly when using firefox, playing games, even just leaving the computer on doing nothing. everything is running at stock speed, no OC. I ran memtest and showed no problems.

anyone know by looking at the dumps below if this this hardware or driver/software related?


On Sun 11/1/2009 10:09:08 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFC (0xFFFFF8A0001E7100, 0x9C90000000AAD943, 0xFFFFF88007B01260, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 11/1/2009 8:11:08 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC5 (0x108, 0x2, 0x1, 0xFFFFF80002BB990D)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 11/1/2009 5:51:41 AM your computer crashed
This was likely caused by the following module: jraid.sys
Bugcheck code: 0x50 (0xFFFFF88008CAD1DC, 0x1, 0xFFFFF88000FDEC9E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\jraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver



On Sun 11/1/2009 5:09:51 AM your computer crashed
This was likely caused by the following module: jraid.sys
Bugcheck code: 0x50 (0xFFFFF8800EFDF29C, 0x1, 0xFFFFF88000DE2C9E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\jraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver



On Sun 11/1/2009 4:28:03 AM your computer crashed
This was likely caused by the following module: jraid.sys
Bugcheck code: 0x50 (0xFFFFF8800FD4EF9C, 0x1, 0xFFFFF88000C58C9E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\jraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver



On Sat 10/31/2009 10:18:16 PM your computer crashed
This was likely caused by the following module: jraid.sys
Bugcheck code: 0x50 (0xFFFFF8800EFE0ADC, 0x1, 0xFFFFF88000DDAC9E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\jraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver



On Sat 10/31/2009 7:16:16 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xFFFFFA80094000A0, 0xFFFFFA80094004B0, 0x441CD70)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 10/31/2009 5:01:04 AM your computer crashed
This was likely caused by the following module: jraid.sys
Bugcheck code: 0x50 (0xFFFFF880046767DC, 0x1, 0xFFFFF88000DE5C9E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\jraid.sys
product: JMicron JMB36X RAID Driver
company: JMicron Technology Corp.
description: JMicron JMB36X RAID Driver



On Wed 10/28/2009 6:37:45 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A7A105, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 10/28/2009 2:37:31 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C7BFC, 0xFFFFF8800724CE20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 10/27/2009 2:32:45 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 10/25/2009 7:58:09 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AE064A, 0x0, 0x2F8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
 
Couple of those are your Raid system. If Windows virtual memory is having trouble writing to your array, it could create a corruption in the kernel and thus you crash. Do you have the means to do an install with a standard single drive to see if this is the case?

It's what I'd try from the above. I did practically nothing to my install and it became more stable, not less.
 
I have been getting random lockups. Fresh install to my main rig. Only OCed to 3.4GHz right now.

Half the time I am doing some large file copies, since I'm moving old stuff around. But, I have no RAID, just a VR80 & my 640AAKS (& sometimes an eSATA backup HDD). It is becoming quite annoying.
 
Back
Top