Blue screen and system freeze
Started by
aydyty
, Jun 24 2011 11:21 AM
#31
Posted 30 June 2011 - 07:44 PM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
#32
Posted 01 July 2011 - 05:49 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
OK and how is the system running now?
Anymore bsod's or freezing?
Anymore bsod's or freezing?
#33
Posted 04 July 2011 - 08:28 PM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
Sorry, was away for the long wknd...system seems to have stabilized. For my educational interests, what was the voltage issue you were tyring to isolate?
#34
Posted 04 July 2011 - 09:23 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
I was trying to see the +12 volt rail as that is the important one for a system.
#35
Posted 12 July 2011 - 07:14 PM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
Hi: system became unstable again froze, got a blue screen and will not load now at all (even in safe mode). Ran HP diagnostic program at the blue start-up screen and it gives me a biome-1 error code, any sugesstions?
#36
Posted 12 July 2011 - 09:04 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
According to HP's site that error indicates a faulty memory module.
I went back starting with post 6 and I don't think you ever ran the memtest86 program to test the memory as i suggested in post 5.
I went back starting with post 6 and I don't think you ever ran the memtest86 program to test the memory as i suggested in post 5.
#37
Posted 13 July 2011 - 08:20 PM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
Was able to get into system today and ran a who crashed module, dn do memtest86 yet - not sure if this is helpful? Can run mem test tmrw:
On Wed 7/13/2011 1:06:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFFA6002D42240, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 1:06:37 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFFA6002D42240, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 12:35:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x134843)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002536843, 0xFFFFFA60019BF948, 0xFFFFFA60019BF320)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 12:25:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0x159A, 0x7FFFFFC7509)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 7/12/2011 11:20:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80062F4C10, 0xFFFFFA80062F4E48, 0xFFFFF80002729640)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 7/12/2011 11:16:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000254EFEC, 0xFFFFFA600C2D7760, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 7/12/2011 5:25:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800024A4C7B, 0xFFFFFFFFFFFFFFFF, 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
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 1:06:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFFA6002D42240, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 1:06:37 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFFA6002D42240, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 12:35:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x134843)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002536843, 0xFFFFFA60019BF948, 0xFFFFFA60019BF320)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 7/13/2011 12:25:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0x159A, 0x7FFFFFC7509)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 7/12/2011 11:20:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80062F4C10, 0xFFFFFA80062F4E48, 0xFFFFF80002729640)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 7/12/2011 11:16:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000254EFEC, 0xFFFFFA600C2D7760, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 7/12/2011 5:25:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800024A4C7B, 0xFFFFFFFFFFFFFFFF, 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
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
#38
Posted 14 July 2011 - 02:55 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
I will wait for the memtest results.
#39
Posted 15 July 2011 - 04:02 AM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
Ran memtest - on the first attempt, it froze on test 3 indicating over 3 million errors at 1:22 wall clock, as the program stopped running I restarted the machine and re-ran the memtest program. Memtest then ran successfully overnight, went through 7 passes with no errors.
#41
Posted 15 July 2011 - 07:37 PM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
Ran ckdsk. 1st attempt ended in a bsod, ran successfully second time.
#42
Posted 15 July 2011 - 07:59 PM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Has system froze or BSOD with the exception of running the tests?
#43
Posted 15 July 2011 - 10:55 PM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
Not since running the tests
#44
Posted 16 July 2011 - 05:50 AM
rshaffer61
-
- Moderator
-
- 34,114 posts
Moderator
Chkdsk would be the one that could have resolved the issue. Let me know in a day or two if the issue returns. 
#45
Posted 16 July 2011 - 07:59 AM
aydyty
- Topic Starter
-
- Member
-
- 117 posts
Member
system froze again 2x this morning as I was in my email acct, going back into the posts - I had not done the virtual mem changes from post 4 as the instructions did not line up to what I saw in those windows and we started going down a diff direction with other tests - dnk if that is worth a shot?
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:
Sign In
Create Account
