Nicole26
Topic Starter
Hello everyone,
I bought a new computer from Ibuypower in October and since receiving it I have had daily BSOD crashes. I have been online with their tech support but they give me the typical, update your drivers, uninstall and re-install your drivers, etc. I have run a disk check without any errors as well as a memory check without any errors. I have tried all suggestions and find myself lost. To clarify my situation I am going to list my computer build below as well as list the blue screen errors I have gotten just this weekend.
Computer Build
1 x Case NZXT Guardian 921 RB Gaming Case - Black w/ Blue Light
0 x Case Lighting None
0 x iBUYPOWER Labs - Noise Reduction None
0 x iBUYPOWER Labs - Internal Expansion None
1 x Processor AMD FX-8150 CPU (8x 3.60GHz/8MB L2 Cache)
1 x Processor Cooling Liquid CPU Cooling System [AMD] - ARC Dual Silent High Performance Fan Upgrade (Push-Pull Airflow)
1 x Memory 16 GB [4 GB X4] DDR3-1600 Memory Module - Corsair or Major Brand
1 x Video Card AMD Radeon HD 6970 - 2GB - HIS IceQ X Turbo - Core: 900MHz - Single Card
1 x Video Card Brand Major Brand Powered by AMD or NVIDIA
1 x Motherboard Gigabyte GA-970A-D3 – AMD 970
1 x Motherboard USB / SATA Interface [Free] Internal USB 3.0 PCI-E 2.0 x1 Expansion Card
1 x Power Supply 1000 Watt – Extreme Gaming Series
1 x Primary Hard Drive 120 GB Corsair Force Series 3 F120 SSD - Single Drive
1 x Data Hard Drive 2 TB HARD DRIVE – 64M Cache, 7200 RPM, 6.0Gb/s - Single Drive
1 x Optical Drive [12X Blu-Ray] LG BLU-RAY Reader, DVD±R/±RW Burner Combo Drive - Black
0 x 2nd Optical Drive None
1 x Flash Media Reader / Writer 12-In-1 Internal Flash Media Card Reader/Writer - Black
0 x Meter Display None
0 x USB Expansion None
1 x Sound Card 3D Premium Surround Sound Onboard
1 x Network Card Onboard LAN Network (Gb or 10/100)
1 x Operating System Microsoft Windows 7 Home Premium + Office Starter 2010 (Includes basic versions of Word and Excel) - 64-Bit
1 x Additional Software Microsoft Office 2010 Home and Business - Word, Excel, PowerPoint, OneNote, and Outlook included
1 x Keyboard Razer Lycosa Gaming Keyboard
1 x Mouse MadCatz Cyborg R.A.T.5 4000dpi Gaming Mouse
1 x Monitor 24" LED 1920x1080 – ASUS VS248H-P
0 x 2nd Monitor None
1 x Monitor Cable 30 ft. DVI to HDMI Cable (Resolution up to 1080P)
1 x Speaker System iBUYPOWER 2.1 Channel Stereo Super Bass Subwoofer Speaker System
1 x Power Protection Mighty Voltage Regulator - Opti-UPS SS1200-AVR
0 x Headset None
0 x Video Camera None
1 x Advanced Build Options Tuniq TX-2 High Performance Thermal Compound - The best interface between your CPU and the heatsinks
1 x Advanced Build Options Professional wiring for all cables inside the system tower - Achieve exceptional airflow in your chassis
1 x Advanced Build Options Professional wiring for all cables inside the system tower - Basic Pro Wiring
Crash Log For This Weekend (Items in red italics indicate what I was doing at time of crash)
On Sat 1/21/2012 1:02:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012012-14149-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFF80047EA2F5E, 0xD, 0x8, 0xFFFFF80047EA2F5E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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.
(At this time I was only online on my school site angel.com in the middle of an extensive forum post to one of my peers. My post was of course lost… and the system crashed. Nothing running in the background, just my web browser google chrome).
On Sat 1/21/2012 3:02:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012012-13743-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2469)
Bugcheck code: 0xA (0x203B, 0x2, 0x1, 0xFFFFF800033FB469)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 1/21/2012 3:02:17 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalMakeBeep+0x11A1)
Bugcheck code: 0xA (0x203B, 0x2, 0x1, 0xFFFFF800033FB469)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
(I was browsing the web as well when it just crashed… frustrating)
On Sun 1/22/2012 9:36:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
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
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 Sun 1/22/2012 9:36:25 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTIONh_NOT_HANDLED
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.
(I was working in Microsoft word and running Nitro Pro PDF to Word converter in the background).
On Mon 1/23/2012 12:27:11 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xD1 (0x7FE, 0x2, 0x0, 0xFFFFF880016D3642)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 1/22/2012 9:36:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
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
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.
(Was loading game: Star Wars the Old Republic when computer crashed)
Any insight? Thank you in advance for your help!
Sincerely,
Nicole
I bought a new computer from Ibuypower in October and since receiving it I have had daily BSOD crashes. I have been online with their tech support but they give me the typical, update your drivers, uninstall and re-install your drivers, etc. I have run a disk check without any errors as well as a memory check without any errors. I have tried all suggestions and find myself lost. To clarify my situation I am going to list my computer build below as well as list the blue screen errors I have gotten just this weekend.
Computer Build
1 x Case NZXT Guardian 921 RB Gaming Case - Black w/ Blue Light
0 x Case Lighting None
0 x iBUYPOWER Labs - Noise Reduction None
0 x iBUYPOWER Labs - Internal Expansion None
1 x Processor AMD FX-8150 CPU (8x 3.60GHz/8MB L2 Cache)
1 x Processor Cooling Liquid CPU Cooling System [AMD] - ARC Dual Silent High Performance Fan Upgrade (Push-Pull Airflow)
1 x Memory 16 GB [4 GB X4] DDR3-1600 Memory Module - Corsair or Major Brand
1 x Video Card AMD Radeon HD 6970 - 2GB - HIS IceQ X Turbo - Core: 900MHz - Single Card
1 x Video Card Brand Major Brand Powered by AMD or NVIDIA
1 x Motherboard Gigabyte GA-970A-D3 – AMD 970
1 x Motherboard USB / SATA Interface [Free] Internal USB 3.0 PCI-E 2.0 x1 Expansion Card
1 x Power Supply 1000 Watt – Extreme Gaming Series
1 x Primary Hard Drive 120 GB Corsair Force Series 3 F120 SSD - Single Drive
1 x Data Hard Drive 2 TB HARD DRIVE – 64M Cache, 7200 RPM, 6.0Gb/s - Single Drive
1 x Optical Drive [12X Blu-Ray] LG BLU-RAY Reader, DVD±R/±RW Burner Combo Drive - Black
0 x 2nd Optical Drive None
1 x Flash Media Reader / Writer 12-In-1 Internal Flash Media Card Reader/Writer - Black
0 x Meter Display None
0 x USB Expansion None
1 x Sound Card 3D Premium Surround Sound Onboard
1 x Network Card Onboard LAN Network (Gb or 10/100)
1 x Operating System Microsoft Windows 7 Home Premium + Office Starter 2010 (Includes basic versions of Word and Excel) - 64-Bit
1 x Additional Software Microsoft Office 2010 Home and Business - Word, Excel, PowerPoint, OneNote, and Outlook included
1 x Keyboard Razer Lycosa Gaming Keyboard
1 x Mouse MadCatz Cyborg R.A.T.5 4000dpi Gaming Mouse
1 x Monitor 24" LED 1920x1080 – ASUS VS248H-P
0 x 2nd Monitor None
1 x Monitor Cable 30 ft. DVI to HDMI Cable (Resolution up to 1080P)
1 x Speaker System iBUYPOWER 2.1 Channel Stereo Super Bass Subwoofer Speaker System
1 x Power Protection Mighty Voltage Regulator - Opti-UPS SS1200-AVR
0 x Headset None
0 x Video Camera None
1 x Advanced Build Options Tuniq TX-2 High Performance Thermal Compound - The best interface between your CPU and the heatsinks
1 x Advanced Build Options Professional wiring for all cables inside the system tower - Achieve exceptional airflow in your chassis
1 x Advanced Build Options Professional wiring for all cables inside the system tower - Basic Pro Wiring
Crash Log For This Weekend (Items in red italics indicate what I was doing at time of crash)
On Sat 1/21/2012 1:02:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012012-14149-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFF80047EA2F5E, 0xD, 0x8, 0xFFFFF80047EA2F5E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 driver attempted to access pageable memory at a process IRQL that was too high.
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.
(At this time I was only online on my school site angel.com in the middle of an extensive forum post to one of my peers. My post was of course lost… and the system crashed. Nothing running in the background, just my web browser google chrome).
On Sat 1/21/2012 3:02:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012012-13743-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2469)
Bugcheck code: 0xA (0x203B, 0x2, 0x1, 0xFFFFF800033FB469)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 1/21/2012 3:02:17 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalMakeBeep+0x11A1)
Bugcheck code: 0xA (0x203B, 0x2, 0x1, 0xFFFFF800033FB469)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
(I was browsing the web as well when it just crashed… frustrating)
On Sun 1/22/2012 9:36:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
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
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 Sun 1/22/2012 9:36:25 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTIONh_NOT_HANDLED
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.
(I was working in Microsoft word and running Nitro Pro PDF to Word converter in the background).
On Mon 1/23/2012 12:27:11 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0xD1 (0x7FE, 0x2, 0x0, 0xFFFFF880016D3642)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 1/22/2012 9:36:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
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
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.
(Was loading game: Star Wars the Old Republic when computer crashed)
Any insight? Thank you in advance for your help!
Sincerely,
Nicole