BSOD on multiple windows 7 installs

Hello everybody!

I just bought an HP probook 4530s notebook that came with Suse Linux. I installed Windows 7 Ultimate x64 and after I installed the drivers it started to crash with BSOD. I double checked to see if I had the latest version for the drivers and bios and everything was all right. Unfortunately I didn't write down all of the messages, but I did see that files ending in .sys were causing them: athrx.sys (wireless lan driver), igdkmd64.sys, dxgnms1.sys, ntfs.sys and another one (can't remember the name) that was a video driver file(for intel hd graphics 3000).
I installed a fresh copy of windows home premium x64 and the appropriate drivers and still the crashes went on.

I thought that there may be something wrong with driver support for 64bit windows 7 so I now have Windows 7 Professional 32bit installed. This time the crashes are less frequent, but still present. The drivers are definitely up to date, I even checked with various driver tools. I also updated windows with the latest updates. I tested the memory with memtest86, 9 passes and the memory seems to be fine.
Here is what WinDbg has to say about MEMORY.dmp:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c51000 PsLoadedModuleList = 0x82d9a4d0
Debug session time: Sun Jun 26 00:47:32.158 2011 (UTC + 3:00)
System Uptime: 0 days 0:14:34.173
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd400c).  Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {514, 2, 1, 82cf3bdc}

Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+187 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000514, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82cf3bdc, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS:  00000514 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!RtlEnumerateEntryHashTable+76
82cf3bdc 897104          mov     dword ptr [ecx+4],esi

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  LMS.exe

TRAP_FRAME:  adef5890 -- (.trap 0xffffffffadef5890)
ErrCode = 00000002
eax=85dd28b8 ebx=00000018 ecx=00000510 edx=85c69670 esi=adef592c edi=85956a44
eip=82cf3bdc esp=adef5904 ebp=adef5910 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!RtlEnumerateEntryHashTable+0x76:
82cf3bdc 897104          mov     dword ptr [ecx+4],esi ds:0023:00000514=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82cf3bdc to 82c925cb

STACK_TEXT:  
adef5890 82cf3bdc badb0d00 85c69670 adef5994 nt!KiTrap0E+0x2cf
adef5910 88ec1b28 85c69670 adef592c 85372054 nt!RtlEnumerateEntryHashTable+0x76
adef5954 88ec2547 00000017 85372054 00000000 tcpip!TcpEnumerateConnections+0x22a
adef5984 88ec25e8 00000041 0000001f adef5a4c tcpip!TcpEnumerateConnectionType+0xb7
adef5994 88d4efe2 adef59ac 00000041 85372000 tcpip!TcpEnumerateAllConnections+0xf
adef5a4c 8ddc3ba1 85372000 20332b85 0000003c NETIO!NsiEnumerateObjectsAllParametersEx+0x187
adef5ac0 8ddc4efc 8537203c 00000000 85372054 nsiproxy!NsippEnumerateObjectsAllParameters+0xeb
adef5ae4 8ddc4fe5 856c9101 00000000 85bb6dc8 nsiproxy!NsippDispatchDeviceControl+0x78
adef5afc 82c88593 85f586b8 856c91b0 856c91b0 nsiproxy!NsippDispatch+0x33
adef5b14 82e7b98f 85bb6dc8 856c91b0 856c9220 nt!IofCallDriver+0x63
adef5b34 82e7eb61 85f586b8 85bb6dc8 00000000 nt!IopSynchronousServiceTail+0x1f8
adef5bd0 82ec53fc 85f586b8 856c91b0 00000000 nt!IopXxxControlFile+0x6aa
adef5c04 82c8f1ea 00000178 00000158 00000000 nt!NtDeviceIoControlFile+0x2a
adef5c04 773070b4 00000178 00000158 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00fdf768 00000000 00000000 00000000 00000000 0x773070b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!NsiEnumerateObjectsAllParametersEx+187
88d4efe2 8945fc          mov     dword ptr [ebp-4],eax

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NETIO!NsiEnumerateObjectsAllParametersEx+187

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78963

FAILURE_BUCKET_ID:  0xA_NETIO!NsiEnumerateObjectsAllParametersEx+187

BUCKET_ID:  0xA_NETIO!NsiEnumerateObjectsAllParametersEx+187

Followup: MachineOwner
---------

And this is the report for the last minidump:

Code:

Loading Dump File [C:\Windows\Minidump\062611-23212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c51000 PsLoadedModuleList = 0x82d9a4d0
Debug session time: Sun Jun 26 00:47:32.158 2011 (UTC + 3:00)
System Uptime: 0 days 0:14:34.173
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {514, 2, 1, 82cf3bdc}

Probably caused by : NETIO.SYS ( NETIO!NsiEnumerateObjectsAllParametersEx+187 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000514, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82cf3bdc, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dba848
Unable to read MiSystemVaType memory at 82d99e20
 00000514 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!RtlEnumerateEntryHashTable+76
82cf3bdc 897104          mov     dword ptr [ecx+4],esi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  LMS.exe

TRAP_FRAME:  adef5890 -- (.trap 0xffffffffadef5890)
ErrCode = 00000002
eax=85dd28b8 ebx=00000018 ecx=00000510 edx=85c69670 esi=adef592c edi=85956a44
eip=82cf3bdc esp=adef5904 ebp=adef5910 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!RtlEnumerateEntryHashTable+0x76:
82cf3bdc 897104          mov     dword ptr [ecx+4],esi ds:0023:00000514=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82cf3bdc to 82c925cb

STACK_TEXT:  
adef5890 82cf3bdc badb0d00 85c69670 adef5994 nt!KiTrap0E+0x2cf
adef5910 88ec1b28 85c69670 adef592c 85372054 nt!RtlEnumerateEntryHashTable+0x76
adef5954 88ec2547 00000017 85372054 00000000 tcpip!TcpEnumerateConnections+0x22a
adef5984 88ec25e8 00000041 0000001f adef5a4c tcpip!TcpEnumerateConnectionType+0xb7
adef5994 88d4efe2 adef59ac 00000041 85372000 tcpip!TcpEnumerateAllConnections+0xf
adef5a4c 8ddc3ba1 85372000 20332b85 0000003c NETIO!NsiEnumerateObjectsAllParametersEx+0x187
adef5ac0 8ddc4efc 8537203c 00000000 85372054 nsiproxy!NsippEnumerateObjectsAllParameters+0xeb
adef5ae4 8ddc4fe5 856c9101 00000000 85bb6dc8 nsiproxy!NsippDispatchDeviceControl+0x78
adef5afc 82c88593 85f586b8 856c91b0 856c91b0 nsiproxy!NsippDispatch+0x33
adef5b14 82e7b98f 85bb6dc8 856c91b0 856c9220 nt!IofCallDriver+0x63
adef5b34 82e7eb61 85f586b8 85bb6dc8 00000000 nt!IopSynchronousServiceTail+0x1f8
adef5bd0 82ec53fc 85f586b8 856c91b0 00000000 nt!IopXxxControlFile+0x6aa
adef5c04 82c8f1ea 00000178 00000158 00000000 nt!NtDeviceIoControlFile+0x2a
adef5c04 773070b4 00000178 00000158 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00fdf768 00000000 00000000 00000000 00000000 0x773070b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!NsiEnumerateObjectsAllParametersEx+187
88d4efe2 8945fc          mov     dword ptr [ebp-4],eax

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NETIO!NsiEnumerateObjectsAllParametersEx+187

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce78963

FAILURE_BUCKET_ID:  0xA_NETIO!NsiEnumerateObjectsAllParametersEx+187

BUCKET_ID:  0xA_NETIO!NsiEnumerateObjectsAllParametersEx+187

Followup: MachineOwner
---------

I would really appreciate your help. Thank you!

I just got another BSOD, this time it was win32k.sys
I don't know if it has anything to do with it, but I noticed that it crashes a lot when watching youtube videos, like it did now.

This is the minidump report:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062611-16473-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82c0b000 PsLoadedModuleList = 0x82d544d0
Debug session time: Sun Jun 26 20:58:07.532 2011 (UTC + 3:00)
System Uptime: 0 days 0:10:27.938
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 97ebb20c, b1ab44f0, 0}

Probably caused by : hardware ( win32k!EngAlphaBlend+1d2 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 97ebb20c, The address that the exception occurred at
Arg3: b1ab44f0, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!EngAlphaBlend+1d2
97ebb20c 080f            or      byte ptr [edi],cl

TRAP_FRAME:  b1ab44f0 -- (.trap 0xffffffffb1ab44f0)
ErrCode = 00000002
eax=fe4b1000 ebx=b1ab47a8 ecx=ffbbd540 edx=fe66c000 esi=00000000 edi=00000001
eip=97ebb20c esp=b1ab4564 ebp=b1ab4764 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
win32k!EngAlphaBlend+0x1d2:
97ebb20c 080f            or      byte ptr [edi],cl          ds:0023:00000001=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!EngAlphaBlend+1d2
97ebb20c 080f            or      byte ptr [edi],cl

LAST_CONTROL_TRANSFER:  from 97ebbe02 to 97ebb20c

STACK_TEXT:  
b1ab4764 97ebbe02 fd9a3408 ffbbd540 00000000 win32k!EngAlphaBlend+0x1d2
b1ab47d0 97ebc1bb fe4b1010 ff429a90 fe66c010 win32k!SURFREFDC::vUnlock+0x1e5
b1ab4874 97ec4892 fe4b1010 ff429a90 00000000 win32k!SURFREFDC::vUnlock+0x59e
b1ab48d4 97ec47e4 fe4b1010 ff429a90 00000000 win32k!EngNineGrid+0x6e
b1ab4934 97ec46aa fe4b1010 ff429a90 00000000 win32k!EngDrawStream+0x109
b1ab49a8 97ec11c3 b1ab4aa4 00000000 ff429a80 win32k!NtGdiDrawStreamInternal+0x232
b1ab4ad4 97ec0c29 62010f06 00000000 ffbb4810 win32k!GreDrawStream+0x557
b1ab4c20 82c491ea 62010f06 00000060 03d4eb18 win32k!NtGdiDrawStream+0x8c
b1ab4c20 774570b4 62010f06 00000060 03d4eb18 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
03d4ea94 00000000 00000000 00000000 00000000 0x774570b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!EngAlphaBlend+1d2
97ebb20c 080f            or      byte ptr [edi],cl

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!EngAlphaBlend+1d2

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

Followup: MachineOwner
---------

And again another one, this time it was a stop message. I attached all the minidump files.

Hello,

Where are you getting your copies of Windows?

Try flashing the latest BIOS from here: HP ProBook 4530s Notebook PC - HP System BIOS Update - HP Business Support Center

...Summary of the dumps:

Code:

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Sat Jun 25 10:04:41.704 2011 (UTC - 4:00)
System Uptime: 0 days 1:53:08.108
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntkrnlpa.exe ( nt+41d0b )
BUGCHECK_STR:  0x7f_d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 25 17:47:32.158 2011 (UTC - 4:00)
System Uptime: 0 days 0:14:34.173
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
*** WARNING: Unable to verify timestamp for nsiproxy.sys
*** ERROR: Module load completed but symbols could not be loaded for nsiproxy.sys
Probably caused by : NETIO.SYS ( NETIO+5fe2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  LMS.exe
FAILURE_BUCKET_ID:  0xA_NETIO+5fe2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 25 15:08:43.682 2011 (UTC - 4:00)
System Uptime: 0 days 0:16:53.086
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  0x24_Ntfs+ac789
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Sat Jun 25 07:14:43.599 2011 (UTC - 4:00)
System Uptime: 0 days 0:44:51.004
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : ntkrnlpa.exe ( nt+933ab )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

Run the three Prime95 tests: https://www.sevenforums.com/tutorials...t-prime95.html

The F.07 BIOS shown on the HP page is dated April 21, with the F.05 released earlier that month. I am confused why the F.08 would be dated March 5.

Try flashing the F.07, if it will let you.

I feel a double post is more appropriate than an edit. One of the other members pointed out that the HP page we have been using probably isn't the correct support page for your exact model. I'm not sure how to get to the correct model page, but a good place to try may be here: HP Support & Drivers | United States

Give the auto-detect feature a try.

Ok, I ran prime95 and I got no errors, but the temperature of the cpu was 80 degrees Celsius. I bit high I guess...

Is it possible to be a hardware issue causing the blue screens and not just some glitch caused by the drivers? I can still return the laptop and ask for a replacement.

edit: I just flashed the bios with f.07 version, it was indeed newer than f.08. I'm eager to see if the bsod is gone.
edit #2: nope, it's not. this time a stop message. I've had enough, it's going back to the store. Thank you for your help.

That is probably the best option, good luck with the return!